Practical overview
When it fits
Consider Bitcart when you want to operate a self-hosted cryptocurrency payment processor and are prepared to consult its documentation for deployment and integration details.
Who it is for
- Merchants seeking to process cryptocurrency payments using a self-hosted service.
- Developers exploring integrations or checkout-flow automation within the Bitcart ecosystem.
Documented uses
- Set up a merchant payment processor for cryptocurrency payments.
- Use related ecosystem components for administration, a ready-made store, coin connections or checkout-flow scripting.
Requirements & limits
The project is described as free and open-source under the MIT license. It is intended for self-hosted deployment; Docker packaging is identified as the base for deployment methods.
- Bitcart is a self-hosted processor, not simply a hosted checkout service.
- The core repository and supporting components are separate repositories, including the admin panel, store, Docker packaging, SDK and checkout scripting language.
- The repository links to documentation, but the available description does not specify exact setup steps or API behavior.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Use Bitcart to accept direct cryptocurrency payments
Configure Bitcart as a merchant invoice and payment-processing system that directs payments to your wallet.
Before you start
- A self-hosted Bitcart instance.
- A wallet master public key (xpub) to configure as a watch-only key.
Steps
Configure the wallet using its watch-only master public key; the documentation says private keys are not required on the server.
Use Bitcart to create an invoice for a customer.
Present the invoice to the customer; Bitcart generates a fresh address associated with the configured wallet for each invoice.
After payment, use the instance’s payment monitoring and order-fulfillment automation.
Expected outcome
Customers can pay invoices directly to addresses belonging to the merchant’s wallet, while Bitcart watches for payments and can automate fulfillment.
Guide limitations
- Bitcart uses the Electrum wallet protocol and SPV to verify payments.
- The merchant remains responsible for the wallet; the server does not store private keys.
- A server outage or loss of server settings and invoice data can affect operations, although the documentation says offline invoice payments are detected when the instance returns.
- The documentation describes capabilities but does not provide the configuration or checkout steps here.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 9 October 2026
- Original website title
- bitcart/bitcart · Official homepage title · retained in its source language

