BTCPay Server

BTCPay Server is a free and open-source, self-hosted Bitcoin payment processor that lets a merchant accept Bitcoin payments directly, without fees, custodians, or KYC intermediaries. It is licensed under the MIT license and maintained by the BTCPay Server Foundation alongside a global community of volunteer contributors. For a sovereign Bitcoiner who wants to sell goods or accept donations on their own terms, it is the canonical self-hosted alternative to custodial payment gateways — and it is not theory for us: D-Central runs BTCPay in production, powering the Bitcoin checkout in our own shop and the on-chain and Lightning options on our Fund the Sovereign Stack page.

How it works

BTCPay runs on the merchant's own infrastructure and connects to a Bitcoin full node, so payments settle peer-to-peer straight to the merchant's wallet — the operator holds their own keys and the platform never takes custody. Address generation happens from an extended public key, meaning the server can issue fresh invoices all day without a single private key ever touching the machine. It generates invoices, point-of-sale screens, payment buttons, and crowdfunding pages, exposes a full API for automation, and integrates with common e-commerce platforms, including the WooCommerce stack this very site runs on. Because it is self-hosted, there is no third party that can freeze funds, close an account, or impose chargebacks — the failure modes of custodial processors simply have no place to live.

Lightning integration

BTCPay accepts both on-chain payments and Lightning Network payments from the same invoice. For Lightning it integrates with the major node implementations — LND, Core Lightning, and Eclair — letting a merchant route instant, low-fee payments through whichever node software they already operate. Small purchases that would be awkward on-chain become trivial over Lightning, while large ones settle on-chain with full finality; the customer just pays the invoice and BTCPay sorts out which rail was used.

Why it matters for sovereignty

Running it in practice

Deployment is more approachable than "run your own payment processor" sounds. The standard path is a Docker-based install that bundles Bitcoin node, optional Lightning node, database, and web front end; modest homelab or VPS hardware runs it comfortably, with the Bitcoin node's chain storage as the main resource line — and a pruned node configuration keeps even that within reach of small disks. Day-two operations are the honest workload: applying updates, backing up the store configuration and wallet descriptors, and — if you run Lightning — watching channel liquidity so invoices keep getting paid. Many operators start by accepting on-chain only, which needs no liquidity management at all, then add Lightning once the store proves out. The reward structure suits patient builders: a checkout that costs nothing per transaction, censors nothing, and improves every release without a vendor deciding your category of business is no longer welcome. It is the difference between renting your till and owning it.

BTCPay is funded by grant programs and donations rather than transaction fees, which keeps its incentives aligned with self-custody instead of rent extraction. It embodies the verify, don't trust ethos applied to commerce: your node validates the payments, your keys receive the funds, your server issues the invoices. For a miner or homesteader already running a node, adding BTCPay decentralizes one more layer of their operation — the revenue side — the same way running your own firmware or your own pool connection decentralizes the production side. It is honest to note the cost: you are now the sysadmin, responsible for backups, updates, and uptime. Most operators find that a fair trade for owning their checkout outright. To connect it to your own Lightning node, see our entries on LND (Lightning Network Daemon) and Core Lightning (CLN).

Find payment stacks in the sovereign self-hosting catalog.