BTPay

• Name: BTPay
• URL: https://btpay.org/
• Category: self-hosted merchant stack / Bitcoin-and-stablecoin checkout appliance
• Tags: bitcoin-ecosystem ethereum-ecosystem solana-ecosystem
• Summary: BTPay is a compact BTCPay-style checkout appliance with stablecoin monitoring bolted on. Useful for invoices, storefronts, webhooks, and privacy defaults; not a merchant-stack anchor.
• What it does:
  • Lets merchants accept onchain Bitcoin through xpubs, output descriptors, or imported static address lists with BIP32-derived fresh addresses
  • Supports integrations with a self-hosted BTCPay Server and LNbits for Lightning-denominated payment flows and tracking
  • Monitors stablecoin payments for major dollar tokens across Ethereum-family chains plus Tron and Solana
  • Exposes invoices, invoice search/export, payment links, receipts, storefronts, donation pages, carts, and post-payment inventory handling
  • Ships a REST API with Bearer-token auth plus HMAC-signed webhooks and retry behavior for merchant integrations
  • Uses Electrum plus mempool-style monitoring, optional SOCKS5/Tor routing, and configurable mempool endpoints to preserve privacy and payment-verification control
  • Runs with JSON-file persistence rather than a database and documents deployment on Linux, FreeBSD, and common PaaS targets
• Key claims:
  • The official site and README describe BTPay as a “Self-hosted Bitcoin payment processor” with “No third parties. No monthly fees. Full control of your keys,” which is the cleanest signal that this is sovereign merchant plumbing rather than a hosted processor
  • The same materials call it a “lightweight, privacy-focused alternative to BTCPay Server,” which is the right frame: narrower, simpler, and smaller than BTCPay Server rather than a peer reference stack
  • The README says BTPay supports onchain Bitcoin, BTCPay Server, LNbits, stablecoins, and wire transfer inside one invoicing and storefront shell, which makes it broader than a Bitcoin-only donation page tool without making it a category anchor
  • The API docs expose invoice lifecycle, payment links, exchange-rate endpoints, and signed webhooks with explicit retry policy, showing a real merchant integration surface rather than a UI-only app
  • The configuration docs emphasize SOCKS5/Tor routing, custom mempool instances, public/private Electrum selection, and no telemetry, reinforcing the privacy-first operator posture
  • The deployment docs explicitly require a single Gunicorn worker because of the in-memory data store, which helps explain why BTPay reads as a compact merchant appliance rather than horizontally scaled payment SaaS
• Whitepaper: No canonical standalone BTPay whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the official site, repository README, and first-party API / configuration / deployment docs; see ../whitepapers/btpay-primary-sources-2026-05-03.md.
• Sources:
  • https://btpay.org/
  • https://github.com/btpay-org/btpay
  • https://raw.githubusercontent.com/btpay-org/btpay/master/README.md
  • https://raw.githubusercontent.com/btpay-org/btpay/master/docs/API.md
  • https://raw.githubusercontent.com/btpay-org/btpay/master/docs/CONFIGURATION.md
  • https://raw.githubusercontent.com/btpay-org/btpay/master/docs/DEPLOYMENT.md

Internal linkages

• Best upward reads: btcpay-server and bitcart.

Control surface

• Practical authority sits in xpub or descriptor import, invoice and storefront defaults, webhook policy, stablecoin coverage, and the privacy or deployment choices the operator keeps enabled.

• Read BTPay as a compact self-hosted checkout appliance, not as a merchant-stack baseline.

• Last reviewed: 2026-06-15 UTC