Bitcart

• Name: Bitcart
• URL: https://bitcart.ai/
• Category: self-hosted crypto merchant stack
• Tags: bitcoin-ecosystem
• Summary: Bitcart is a self-hosted merchant stack: watch-only wallet monitoring, invoice generation, Lightning, an API, and optional admin/store surfaces. Useful merchant plumbing, but still a smaller BTCPay-adjacent tool rather than a reference stack.
• What it does:
  • Lets merchants accept cryptocurrency payments directly into their own wallets without Bitcart taking custody of funds or requiring private keys on the server
  • Uses watch-only xpub or address monitoring plus fresh invoice addresses and Electrum SPV verification to track incoming payments and confirmation state
  • Exposes a modular stack with core daemons, a Merchants API, an optional admin panel, a ready-made store, and multiple deployment paths including Docker
  • Supports Lightning Network payment flows alongside Bitcoin and a wider set of altcoin and token integrations
  • Provides a Python SDK and event-driven daemon interface so developers can build custom wallets, bots, explorers, and checkout automations on top of the stack
  • Includes BitCCL, a dedicated scripting layer for checkout-flow automation, which signals a broader operating surface than a basic hosted checkout product
• Key claims:
  • The official site says Bitcart is a self-hosted, open-source cryptocurrency all-in-one solution with no fees or third-party involvement, and that funds go directly to the merchant wallet while private keys are never required
  • The docs introduction lists direct peer-to-peer payments, no processing fees, no middleman, no KYC, self-hosting, Lightning support, opt-in altcoin integrations, API and SDK support, an admin panel, and a ready store as first-class features
  • The docs explain that Bitcart generates a fresh address from the merchant wallet for each invoice, verifies payments via the Electrum wallet protocol and SPV, and can automate fulfillment work after successful payment
  • The security section says merchants only need to configure a watch-only master public key, so Bitcart can observe and reconcile invoices without being able to move funds
  • The “Bitcart vs others” docs stress modularity, low-resource deployment, host-it-yourself economics, and the ability to use only the components needed, which supports cataloging Bitcart as infrastructure rather than only a merchant-facing app
  • The central repo maps a multi-repo ecosystem spanning core daemons and Merchants API, admin panel, ready store, Docker packaging, SDK, docs, site, and the BitCCL scripting language for checkout automation
  • The SDK README shows multi-coin support with Lightning on Bitcoin, Litecoin, and Groestlcoin plus async/sync event handling, reinforcing that Bitcart is also a reusable developer platform
• Whitepaper: No canonical Bitcart whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, docs corpus, core repo, and SDK repo; see ../whitepapers/bitcart-primary-sources-2026-05-01.md.
• Sources:
  • https://bitcart.ai/
  • https://docs.bitcart.ai/
  • https://docs.bitcart.ai/bitcart-basics/bitcart-vs-others
  • https://github.com/bitcart/bitcart
  • https://github.com/bitcart/bitcart-docs
  • https://github.com/bitcart/bitcart-sdk

Internal linkages

• Best upward reads: btcpay-server and opennode.

Control surface

• Practical authority sits in watch-only wallet configuration, invoice issuance, Lightning wiring, the modules an operator chooses to expose, and which coins or tokens the stack is asked to normalize.

• The useful part is the self-hosted merchant appliance. The wider crypto menu does not turn Bitcart into a payment rail or a category anchor.

• Last reviewed: 2026-06-04 UTC