Bitcart delivers a self-hosted, zero-fee Monero checkout with direct wallet payouts. This 2026 review covers its XMR integration, deployment steps, privacy trade-offs, and comparisons for merchants.
Bitcart is a self-hosted, open-source, non-custodial cryptocurrency payment processor that routes payments directly from customer to merchant wallet. It supports more than 50 coins across 10 blockchains with zero processing fees and requires no KYC or middleman.
Merchants configure the system with watch-only credentials such as xpubs or viewkeys; private keys never enter the software. For Monero specifically, integration relies on integrated addresses and viewkey configuration, a setup introduced in release 0.6.14.0 on 26 November 2022. Balance fetching and payouts for XMR remain limited to watch-only data.
The project maintains active development on GitHub, where the main repository shows 998 stars and 185 forks with commits recorded through 30 October 2026. Bitcart handled Monero checkouts at MoneroKon 2025, demonstrating production use for event payments without custodial custody of funds.
Optional components include an admin panel, point-of-sale interface, API, and plugin system, yet the core payment flow stays non-custodial and privacy-oriented through fresh addresses generated per invoice.
Bitcart keeps merchant funds entirely under user control by accepting only a Monero view key paired with the primary address during store setup. The software uses these watch-only credentials to scan the blockchain and detect payments without ever receiving or storing the private spend key.
For each invoice the processor derives a fresh integrated address. The buyer sends funds directly to that one-time address, and the merchant’s wallet receives the output once the transaction confirms. No intermediate hot wallet or shared account holds the coins at any point.
Monero support entered the codebase through view-key and address configuration. At launch, this implementation disabled both automatic payouts and on-the-fly balance queries for XMR, requiring merchants to handle settlement manually outside the dashboard.
Custodial processors, by contrast, collect and custody merchant funds on their own servers, exposing users to platform insolvency risk and mandatory KYC. Bitcart’s watch-only approach eliminates that custodial layer while still providing real-time payment detection and invoice matching.
Bitcart requires a minimum of 1 GB RAM and roughly 10 GB of disk space for a full installation that includes the necessary daemons. This configuration has remained stable since earlier references in the documentation.
The current version referenced is release 0.10.3.0, dated March 2026, which includes updates to the frontend and proxy components.
Plugin support began with version 0.9.0.0. One notable addition is the paid ETH payments plugin, which improves user experience for ETH, TRX, BNB, MATIC, and related tokens. This plugin operates on a non-custodial basis and uses volume-based billing with thresholds like $2,000 unbilled monthly volume qualifying for yearly plans.
The system is built with modular components such as the store interface, API, and SDK, allowing users to extend functionality selectively.
Bitcart differentiates itself through its documented zero-fee model and modular architecture. The following table summarizes its verified capabilities against the criteria requested.
| Criterion | Bitcart |
|---|---|
| Fee structure | 0% transaction and processing fees (official site, 2026) |
| Self-hosting model | Self-hosted, open-source, non-custodial; private keys never stored |
| Monero address handling | Integrated addresses and viewkey/address configuration; fresh address per invoice; payouts and balance fetching initially disabled |
| Plugin extensibility | Plugins introduced in v0.9.0.0 (March 2025); ETH payments plugin available with volume-based billing |
| Lightning support | Lightning Network and SegWit support for Bitcoin-family coins |
Monero support arrived in release 0.6.14.0 (November 2022). The project lists 50+ cryptocurrencies across 10 blockchains and 248+ tokens. GitHub activity continued through October 2026 with 998 stars and 185 forks. These details position Bitcart as a lightweight, extensible option for merchants seeking direct peer-to-peer settlement without middlemen or KYC requirements.
Bitcart’s non-custodial design keeps private keys off the server, yet several operational points can still link a merchant to Monero activity. Running the instance over clearnet exposes the node’s IP address to anyone scanning for the checkout endpoint. A single public IP can be correlated with domain registration or hosting records, weakening the separation that fresh integrated addresses are meant to provide.
Initial XMR acquisition remains the most common KYC vector. Funds obtained through regulated exchanges carry withdrawal records that may later be matched against on-chain deposits received by the Bitcart wallet. Even when Bitcart itself stores no customer data, the on-ramp trail can re-identify the merchant.
Checkout flows can leak IP information if the customer’s browser contacts the Bitcart server directly or if the merchant accesses the admin panel without protection. Monero’s viewkey configuration allows balance queries without exposing spend keys, but it does not mask the server’s network presence.
Practical steps include hosting behind Tor or a VPN, restricting admin access to authenticated tunnels, and obtaining starting balances through non-KYC channels such as peer-to-peer trades or mining. Merchants should also verify that any plugins or reverse-proxy setups do not inadvertently log request metadata. These measures reduce but do not eliminate linkage risks inherent to self-hosted services.
Bitcart runs on a minimal setup of 1 GB RAM and roughly 10 GB disk space for a full install that includes daemons, according to the deployment FAQ.
Monero support relies on integrated addresses and viewkey configuration, but payouts and balance fetching remain disabled in the current implementation.
The processor handles 50+ cryptocurrencies across 10 blockchains plus 248+ tokens on networks such as ERC-20, BEP-20 and TRC-20.
Core features carry zero fees, yet the ETH payments plugin uses monthly or yearly subscriptions with volume-based billing once monthly unbilled volume exceeds $2,000.
Recent releases include version 0.10.3.0 on March 5, 2026, and plugin support added in 0.9.0.0 roughly one year earlier.
Yes, the modular design supplies an API, SDK and plugin system that merchants can connect to current storefronts without rebuilding from scratch.
