Self-Hosted Python Based Bitcoin Payment Processors / Gateways
A Guide on Self-hosted Python Based Bitcoin Payment Processors#
From what I have seen the go to payment processor is:
- BTC Pay Server 3.7k stars on github
Python based processors I found:
All these providers are:
- Do not rely on a third party
Don’t want to Run your Own?#
These devices were recommended if you don’t want to run your own:
Read up for yourself Bitcart CC Docs
- Process payments as a merchant
- A full invoicing system
- Consists of: Bitcart API, Bitcart admin and bitcart store front
- Can also just do ad hoc stuff with the Bitcart CC SDK
- Has a bitcart-cli
- Supports various crypto shitcoins and Bitcoin (I am bitcoin only)
- Wallet you use must support
xpub(Full BIP32). Bitcoin-core does not support
xpuband hence you cannot use that wallet with BitcartCC
- Notifications for payments received on various platforms, integration with ecommerce
- Hard to add a donate button
- Lots of good documentation
- Lead developer is always available and on telegram
- Works! (I tested on bitcoin testnet)
- The invoice is a fresh address from your wallet that wasn’t used before
- Uses the Electrum wallet protocol and it’s SPV (Simple Payment Verification)
- Highly modular - just use the parts you need
- The BitcartCC Store frontdemo: https://store.bitcartcc.com/
- The BitcartCC Store Admin: https://admin.bitcartcc.com/login
- The BitcartCC api docs: https://api.bitcartcc.com/
How it keeps funds secure#
- For each invoice, BitcartCC generates a new address, belonging to the xpub entered, and this address is presented to the user.
- As this address is your wallet’s address, you receive the funds directly.
- BitcartCC just watches the payments, it can’t modify anything along the way, as when configuring the wallet - you enter a watch-only master public key.
I deployed it on a Debian 9 (stretch) VM with:
- 1 vCPU
- 2 GB RAM
- 40 GB Disk
I followed the manual installation docs
BitcartCC recommends the docker deployment as it is easier and more consistent. You can give it a whirl.
There is also a bitcartCC configurator for those that don’t know what deployment method to use.
- The project is fairly active and has a full-time dev working on it
- Architected in a modular way
- Does not require private keys or seed
- Still growing
- Gaining more stability
- Bitcoin Only
- It is recommended you run a full node that satsale can connect to - a security concern for me mitigated by the use of SSH tunneling. This is for not requiring a third party reasons.
- Docs are sparse - it is pretty much the readme on github
xpub- you can use any wallet that supports
- No notification - must check bitcoin wallet
- No concept of an invoice - linking products to a bitcoin address
- It works (Tested with bitcoin testnet)
- The satsale donation example: https://satsale.org/
- The satsale store demo: https://store.btcpyment.com/
- The satsale api docs: https://satsale.org/docs.html#tag/SatSale-api
- Deployment is manual
- Will take longer and require a lot more understanding: setting up your own node, networking, ensuring security and knowledge of python
- Do it yourself - manual deploymeny.
- The project is gaining momentum
- Good solution for a donation only site
- Easy to link to on your website
- Sticks to bitcoin-core reference
- For the bitcoin maxi’s
- No community channels to talk and get info
Bonus Section: What is wrong with using a single static bitcoin address#
- It links a bitcoin address to a real world identity (your website or portal receiving donations)
- You harm the privacy of people donating to you
The internet is forever. Once an address is posted it will forever be linked to you. There are surveillance companies and security analysts always watching. An example is OXT
An attacker can then know what you are spending the donations on.
Also people who have had their addresses exposed - donating to you will also have that information add to their profile.