Bitcart

Self-hosted cryptocurrency payments, honestly reviewed. No hype about “Web3 disruption” — just what you actually get when you run it yourself.

TL;DR

• What it is: MIT-licensed, self-hosted cryptocurrency payment processor — accepts Bitcoin, Ethereum, Monero, stablecoins (USDT, USDC), and 50+ other coins with zero transaction fees and no intermediary touching your funds [website][3].
• Who it’s for: Online merchants, freelancers, and nonprofits who want to accept crypto payments without paying 1–3% per transaction to Stripe, BitPay, or Coinbase Commerce. Also developers who need a full REST API and Python SDK to build custom payment flows [3][website].
• Cost savings: BitPay charges 1% per transaction; Stripe charges 2.9% + $0.30; Coinbase Commerce has no listed fee but is fully custodial. Bitcart self-hosted runs on a $5–10/mo VPS with unlimited transactions and zero processor fees [4][website].
• Key strength: Genuinely non-custodial. Funds go directly to your wallet — Bitcart never holds or touches your money. Private keys never leave your server [website].
• Key weakness: 915 GitHub stars puts this firmly in “small project” territory. Community support is the primary channel; paid support options are limited to one developer [2]. Compared to BTCPay Server — the dominant alternative — Bitcart has a fraction of the community, documentation, and ecosystem.

---

What is Bitcart

Bitcart is a self-hosted cryptocurrency payment processor. You deploy it on your own server, connect your existing wallets (public key only — no private key required), and start accepting payments across 50+ cryptocurrencies including Bitcoin, Litecoin, Monero, Ethereum, Tron, and ERC-20/BEP-20/TRC-20 tokens like USDT and USDC [website][3].

The project describes itself as “a free and open-source self-hosted payment processor” — which is accurate and refreshingly unambiguous [README]. The homepage leans into the “0% fees, no third-party” pitch, which is the core value proposition and genuinely delivered by the architecture [website].

What makes Bitcart structurally different from SaaS crypto payment providers is the non-custodial design. When a customer pays, the funds go directly to your wallet. Bitcart orchestrates the invoice, confirms the transaction, and fires webhook notifications — but it never intermediates the money. You provide a public key or a watch-only address; Bitcart monitors the blockchain, not your private keys [website].

The architecture is modular — separate repositories for the core daemons, admin panel, storefront, Docker packaging, Python SDK, and a custom scripting language (BitCCL) for checkout automation [README]. You can deploy only the components you need. The admin panel and storefront are optional; the Merchants API works independently [website][3].

The project has 915 GitHub stars and appears to be maintained primarily by one core developer (MrNaif2018, identified across the README and support docs) with a handful of contributors [README][2]. This is not a YC-backed company with a growth team — it’s an open-source project with a real working product and honest community-first support model [2].

---

Why people choose it over BitPay, Coinbase Commerce, and Stripe

The case for Bitcart isn’t complicated: it eliminates transaction fees and custody entirely. The alternatives don’t.

Versus BitPay. BitPay charges 1% per transaction and is a custodial intermediary — they hold settlement funds and handle compliance. For a merchant processing $10,000/month in crypto, that’s $100/month to a middleman, every month, forever. Bitcart processes the same volume for the cost of your VPS hosting — approximately $5–10/month — and you receive funds directly [4][website].

Versus Coinbase Commerce. Coinbase Commerce is free to set up but tied to the Coinbase ecosystem, which means account freezes, identity verification requirements, and geographic restrictions are all in play. Coinbase is also a regulated custodian, meaning your funds pass through their infrastructure. Bitcart is self-hosted and requires no account with any third party [website][3].

Versus Stripe (crypto). Stripe’s crypto payment offering is limited to specific geographies and supported assets, charges their standard 2.9% + $0.30, and routes funds through Stripe’s infrastructure. For merchants accepting international crypto payments where traditional payment rails are expensive or unavailable, Bitcart is in a different category entirely [website].

Versus BTCPay Server. This is the comparison that matters most for technical evaluation. BTCPay Server is the dominant open-source self-hosted payment processor, with significantly more GitHub stars, a larger contributor community, extensive documentation, and broader third-party integrations (WooCommerce, Shopify, etc.). Bitcart’s practical advantage over BTCPay is its multi-currency support architecture (especially smart contract platforms like Ethereum and Tron) and its Python-first SDK, which some developers prefer for backend integration. Data on direct user comparisons is not available from the provided sources, but the GitHub activity gap is significant.

The privacy angle. The self-hosted design means no analytics tracking and customer payment data stays on your server [3]. For merchants in privacy-sensitive industries, or those serving customers in jurisdictions with payment surveillance concerns, this matters.

---

Features

Core payment processing:

• Accept payments in 50+ cryptocurrencies including BTC, LTC, BCH, XMR, ETH, TRX, BNB, MATIC, and stablecoins (USDT, USDC, and others via ERC-20/BEP-20/TRC-20) [website]
• Lightning Network support — enable with a single command [website]
• Non-custodial: funds go directly to your wallet, private key never required [website]
• Invoice management with payment status tracking [3]
• QR code generation for mobile payments [3]
• Fiat price display with automatic crypto conversion [3]
• Real-time payment confirmations and webhook notifications [3]

Admin and storefront:

• Admin panel for product management and checkout configuration [website]
• Ready-to-use storefront (bitcart-store) — fill in products, start selling [website]
• No-code payment pages for merchants without engineering resources [3]
• Plugin system — ETH Payments Plugin released as an extension, available in Admin Panel → Plugins [website]

Developer tools:

• Full REST API for integration with any platform [3][website]
• Python SDK (bitcart-sdk) for connecting to coin daemons and building custom applications [website]
• BitCCL — a custom scripting language for checkout flow automation [README]
• Modular architecture — deploy only what you need [website]
• Compatible with atomic swap bots, blockchain explorers, and custom wallet applications [website]

Deployment:

• Docker + docker-compose as the primary deployment path [3][4]
• Bitcart Configurator for no-CLI setup [4]
• LunaNode web deployment for users who don’t want to manage their own VPS [4]
• Third-party hosts available (free) for users not ready to self-host [4]
• Hardware deployment supported [4]

---

Pricing: SaaS vs self-hosted math

Bitcart is free software (MIT license). The only cost is your server.

Minimum requirements per the official docs: 1GB RAM, ~10GB disk, Docker-compatible OS [4]. A VPS meeting these specs runs $4–7/month on Hetzner, Contabo, or DigitalOcean.

SaaS alternatives for context:

• BitPay: 1% per transaction. On $5,000/month in crypto revenue: $50/month. On $20,000/month: $200/month.
• Stripe (traditional): 2.9% + $0.30 per transaction. On $5,000/month (100 transactions at $50 avg): $175/month.
• Coinbase Commerce: No listed transaction fee, but custodial and ecosystem-locked.

Self-hosted Bitcart math:

• Software: $0
• VPS (Hetzner CX11): ~$4–6/month
• Your time to set up: 1–4 hours depending on technical level
• Ongoing maintenance: low — Docker restarts, occasional version updates

For a merchant processing $10,000/month at BitPay’s 1%: $100/month saved, $1,200/year. For a Stripe merchant at 2.9%: $290/month saved, $3,480/year. These are real numbers, not marketing projections — the fee structure is the fee structure.

The catch: these savings assume you have the technical capability to deploy and maintain a Docker instance, or are willing to pay someone once to do it.

---

Deployment reality check

The official path is Docker Compose via the Bitcart Configurator or CLI [4]. The minimum server requirements are genuinely minimal: 1GB RAM and ~10GB disk [4]. An Ubuntu VPS on any major provider works.

What the setup actually involves:

• A Linux VPS (Ubuntu recommended per docs)
• Domain name for SSL — Bitcart uses Let’s Encrypt via its nginx proxy component [1]
• Run the configurator or set environment variables and execute setup.sh
• First registered user becomes the server admin [4]

What can go sideways:

The troubleshooting docs [1] reveal the common failure modes: SSL certificates not yet issued when you first access the admin panel (causes a Nuxt 500 error), misconfigured BITCART_ADMIN_URL or BITCART_STORE_URL environment variables breaking the one-domain mode, and container-level issues that require docker logs inspection [4]. None of these are unusual for Docker-based self-hosted deployments, but they do require basic command-line comfort to diagnose.

The docs themselves show their age in some places — references to the repository as bitcartcc/bitcart appear in the Klutch.sh guide [3] while the current GitHub organization is bitcart/bitcart. Small discrepancy, but worth noting as a signal of documentation drift.

Community support reality: The support model is community-first — Telegram group, GitHub issues, documentation [2]. Paid support is available from the lead developer (MrNaif2018) for custom integrations and features [2]. There’s no support team, no ticketing system, no SLA. For a merchant whose payment flow goes down on a Friday night, this is a real consideration.

Realistic setup time: 30–60 minutes for someone comfortable with Docker and SSH. 2–4 hours for a non-technical founder following the deployment guide step by step. The Bitcart Configurator and LunaNode deployment option exist specifically to lower this bar [4].

---

Pros and Cons

Pros

• Genuinely non-custodial. Funds go directly to your wallet. No intermediary holds your crypto at any point [website]. This is architecturally enforced, not just a marketing claim — Bitcart only ever needs your public key or a watch-only address.
• Zero transaction fees. Not “lower fees” — zero processor fees. Your only cost is server hosting [4][website].
• MIT license. Full freedom to self-host, fork, embed in your product, or customize without commercial agreement [README].
• 50+ currency support. Including smart contract platforms (Ethereum, Tron, BSC) and stablecoins — broader than many self-hosted alternatives [website].
• Lightning Network built in. Enable with one command [website].
• Modular architecture. Deploy only the components you need — API-only, or with admin panel and storefront [website][README].
• REST API + Python SDK for custom integrations [3][website].
• Minimal server requirements. 1GB RAM, ~10GB disk — runs on the cheapest VPS tier [4].

Cons

• Small community. 915 GitHub stars is modest. Compare to BTCPay Server, which has orders of magnitude more community, documentation, and third-party integrations. If you hit an edge case, the self-help surface area is limited.
• One-developer support. Paid support exists but is provided by a single person [2]. This is a concentration risk for production deployments.
• Documentation shows gaps. The troubleshooting guide is functional but thin [1]. Repository references in third-party docs are inconsistent [3]. Active development appears to continue, but documentation maintenance appears slower.
• No hosted/managed option. There’s no “Bitcart Cloud” where you pay monthly and skip the self-hosting. Third-party hosts exist [4], but they’re community-run and unvetted by the project. If you want managed crypto payments with the Bitcart API surface, you’re self-hosting.
• Limited e-commerce integrations. WooCommerce and Shopify integration are listed as “plugin ready” [3] but the maturity of these integrations is unclear from available sources. BTCPay Server has more extensively maintained e-commerce plugins.
• No audit logs, SSO, or enterprise governance features. This is a merchant payment processor, not an enterprise platform. Fine for solo merchants, a gap for teams with compliance requirements.
• Relatively low GitHub activity signals. 915 stars and the “last commit: n/a” from the metadata suggest slower-than-expected public activity for a production payment tool. Verify the GitHub repository directly before committing to this for a production deployment.

---

Who should use this / who shouldn’t

Use Bitcart if:

• You’re a merchant or freelancer accepting crypto payments and the 1–3% processor fee is your primary pain point.
• You want genuine non-custody — funds going directly to your wallet, no intermediary.
• You’re technically comfortable with Docker deployment, or willing to pay someone once to set it up.
• You need Ethereum, Tron, or stablecoin support alongside Bitcoin — Bitcart’s multi-chain breadth is a real differentiator.
• You’re a developer building a custom payment application and want a REST API + Python SDK without a vendor relationship.

Skip it (use BTCPay Server) if:

• You primarily accept Bitcoin and Lightning, and want the largest community, most documentation, and broadest e-commerce plugin support.
• You’re running a WooCommerce store and need a payment plugin with a track record and active maintenance.
• You want the confidence of a large contributor base behind your production payment infrastructure.

Skip it (stay on Coinbase Commerce or BitPay) if:

• You process low volume and the fee is not a meaningful cost — the simplicity of a hosted solution may be worth $20–50/month.
• You have no technical resources and no budget to hire someone for a one-time deployment.
• Your business requires KYC/AML compliance tooling from your payment processor — Bitcart provides none of this.

Skip it (use Stripe) if:

• Your customers don’t actually want to pay in crypto, and you’re considering this as a “future-proofing” move. Crypto payment adoption by end customers remains low in most markets — solve the real payment problem first.

---

Alternatives worth considering

• BTCPay Server — the dominant self-hosted crypto payment processor. Larger community, more documentation, better e-commerce integrations, Bitcoin-first but with altcoin support. If you’re uncertain, start here.
• BitPay — managed SaaS, 1% fee, handles compliance. Right choice if you want no-ops and can absorb the fee.
• Coinbase Commerce — managed SaaS, no listed fee, custodial, US-market-focused. Simple setup but ecosystem-locked.
• OpenNode — Lightning-native payment processor, managed SaaS, 1% fee. Worth considering for Lightning-first merchants.
• LNbits — Lightning-focused, extremely lightweight, self-hosted. Right for Lightning-only use cases.
• Stripe — not crypto-native, but handles fiat globally with minimal friction. If your customers would actually rather pay in USD, Stripe is the honest answer.

---

Bottom line

Bitcart does what it says: zero-fee, non-custodial, self-hosted crypto payment processing across 50+ currencies, MIT-licensed, running on a $5/month VPS. The value proposition is real, the architecture is sound, and the non-custodial design is enforced in code, not just policy. The trade-offs are equally real: small community, single primary maintainer, documentation that shows its age, and a shadow cast by BTCPay Server’s larger ecosystem. For a merchant whose primary goal is eliminating payment processor fees on crypto transactions — and who has basic Docker literacy or a technical friend — Bitcart is worth a serious look. For merchants who want the safest possible bet in self-hosted crypto infrastructure, BTCPay Server remains the lower-risk default, and Bitcart becomes the right choice specifically when you need multi-chain and stablecoin breadth that BTCPay doesn’t cover as cleanly.

If the deployment step is the barrier, that’s a one-time problem. It’s exactly what upready.dev handles for founders who want the infrastructure running without touching a terminal.

---

Sources

1. Bitcart Docs — Troubleshooting an issue. https://docs.bitcart.ai/support-and-community/troubleshooting-an-issue
2. Bitcart Docs — Support. https://docs.bitcart.ai/support-and-community/support
3. Klutch.sh Docs — Deploying Bitcart. https://docs.klutch.sh/guides/open-source-software/bitcart/
4. Bitcart Docs — Deployment FAQ. https://docs.bitcart.ai/support-and-community/faq/deployment-faq

Primary sources:

• GitHub repository: https://github.com/bitcart/bitcart (915 stars, MIT license)
• Official website: https://bitcart.ai
• Official documentation: https://docs.bitcart.ai