How to accept bitcoin payments on the site?

Question

API

Good afternoon.
There is a need to accept bitcoin payments on the site according to the type "I chose the product> clicked on the button> paid> the site received a response and issued the product"
The option with bitcoind disappears, because there is not so much (200GB) space on the server.
I got acquainted with the blockchain.info API, but did not fully understand the essence of what would happen if 20 wallets were not involved.
If someone has come across this, please explain how this can be organized, or describe how to work correctly with the blockchain.info API.
Thanks in advance.

Answer 1

so, 2 main rules:
1. private keys of addresses issued to users SHOULD NOT be stored on a web server, moreover, since you do not issue coins, store them personally on your (service owner's) hardware wallet
2. bitcoind with the -prune key 512 after loading the blockchain will take up about 6 gigabytes on the disk and through api it will fully work with wallet.dat and the addresses in it in the mode of viewing and checking the receipt of deposits, run also on the server next to the web, at the moment this daemon can even work on a raspberry (it is better to use the file system over the network on a fast file server, because the raspberry has only a VERY slow usb), though it is better to do the initial boot on a fast machine.
You just need to generate on your local machine and import to the web server large batches of addresses for receiving payments (in my mind it is not necessary to do this all the time, but one payment is strongly recommended - a new address) and that's it, your wallet is no longer required. To protect against ddos ​​emptying receive addresses, slip old addresses to clients without incoming transfers.
There are other libraries that take up less resources (they connect directly to the network and do not perform any checks other than the presence of confirmation from the miners, this is more than enough), but formally they are 'not official' (although it is a philosophical question what is official in a decentralized cryptocurrency, but if implements something that breaks compatibility, first of all in bitcoind).
This is the most correct and easiest way to organize payment acceptance.
ps wait for the release of the lightning network, it will soon become the de facto standard for accepting payments
pps for this api) that double-checks everything possible, ideally developed by developers other than those who made the web server.

Answer 2

If it doesn’t matter, then I would advise you to connect the reception of cue balls through a frikassa

Answer 3

And I would advise generating unique addresses for each transaction on the server and parsing information about transactions from blockchain.info. For one project, it turned out to be more convenient for me this way, for another, I raised a node and wrote my json rpc bitcoin bible and use it. Many factors depend on which method is right for you.
Still, I will oppose all kinds of fricassettes and other payment aggregators, why should they pay a commission for nothing?

Answer 4

https://developer.bitaps.com/

Answer 5

As far as I understand you can use Electrum light wallet
How to accept Bitcoin on a website using Electrum
docs.electrum.org/en/latest/merchant.html

Answer 6

https://commerce.coinbase.com/