Definition: BTCPay Server is free, open-source payment-processing software that lets a merchant or organization run its own Bitcoin checkout and receive payments to a wallet it controls. It can create invoices and integrate payments into online stores, point-of-sale flows, donation pages, and other applications. BTCPay is software, not a Bitcoin network, a bank, or a company that holds customer balances; the person operating each instance is responsible for its hosting, configuration, and security.1
| Project type | Self-hosted, open-source Bitcoin payment processor |
|---|---|
| Created | The project says it began in August 2017.4 |
| Official website | BTCPay Server |
| Documentation | Official docs |
| Source code | GitHub |
| Directory | Bitcoin Directory · Bitcoin Technology & Infrastructure |
How BTCPay Server works
BTCPay gives an operator tools to create a store, connect a wallet, issue invoices, and monitor payments. For an existing on-chain wallet, invoice addresses can be derived from its extended public key (xpub); the software does not need the wallet’s master private key to generate receiving addresses. The project describes this as a way to preserve direct wallet control while avoiding address reuse. A buyer pays the invoice to the address provided, and BTCPay tracks the payment and can report its status to a connected store or application. The details a customer sees depend on the merchant’s configuration and integration.1
Software stack and infrastructure
A typical installation connects several components. BTCPay Server provides the merchant interface and payment workflow; Bitcoin Core supplies a Bitcoin node; NBXplorer monitors blockchain activity and payment addresses; and PostgreSQL stores application data. An operator who wants Lightning payments can connect a Lightning implementation such as Core Lightning or LND. These components are separate software with their own configuration, upgrades, storage needs, and failure modes. Running them together can give an operator more control, but it also means someone must maintain the server and keep the node and payment software synchronized.2
Custody and key management
For on-chain payments to an existing wallet, BTCPay can use public wallet data to create receiving addresses without having the private key that spends those funds. That distinction reduces what a compromised web server could do with the on-chain wallet, but it does not make a server compromise harmless: an attacker may still disrupt service, view operational data, or alter payment presentation. Optional server-generated hot wallets and Lightning integrations can involve keys or credentials on the server, which have different risks. Users should understand which wallet type and payment method their installation uses, secure recovery material, and test backups before relying on them.1
Costs and trade-offs
The software itself is free and open source, and the project says it does not charge a subscription or processor transaction fee. “Free software” does not mean operating a payment service has no costs: self-hosting may require hardware, electricity, a domain, administration, and internet service; cloud hosting has provider charges; Bitcoin transactions can incur network fees; and Lightning payments may involve routing fees. A merchant who chooses a third-party BTCPay host avoids maintaining the server but introduces reliance on that host. The right arrangement depends on the operator’s technical ability, uptime needs, privacy goals, and tolerance for managing infrastructure.13
What it does not provide
BTCPay is not itself a bank, exchange, fiat settlement provider, or customer-support desk for every merchant using the software. The project says each merchant controls its own store and wallet, so a buyer with a refund or order issue must contact that merchant. BTCPay can integrate with optional plugins and other services, but those additions have their own terms, dependencies, and availability. Payment confirmations, refunds, tax treatment, and consumer obligations also depend on the specific transaction, setup, and applicable rules; using BTCPay does not decide those questions for a business.1
History
- August 2017: BTCPay Server began as a community open-source project, according to the project’s later foundation announcement.4
- September 14, 2019: The project announced the BTCPay Server Foundation and its first grant from Square Crypto to support development and contributors.4
Last updated: November 12, 2026.
Related Terms
Related Articles
- What Happens to Bitcoin Miner Rewards When New BTC Issuance Ends?
- Bitcoin as Collateral: Bank Loans, Mortgages, and DeFi
- Why Bitcoin Sometimes Moves With Stocks — and Why the Correlation Changes
- The Impact of U.S. Spot Bitcoin ETP Launches in 2024: What Changed and What Did Not
See Also
Sources
- BTCPay Server Contributors, “General FAQ,” BTCPay Server Documentation, accessed November 12, 2026, https://docs.btcpayserver.org/FAQ/General/.
- BTCPay Server Contributors, “Architecture,” BTCPay Server Documentation, accessed November 12, 2026, https://docs.btcpayserver.org/Development/.
- BTCPay Server Contributors, “Deployment FAQ,” BTCPay Server Documentation, accessed November 12, 2026, https://docs.btcpayserver.org/FAQ/Deployment/.
- BTCPay Server Foundation, “Announcing the BTCPay Server Foundation and Our First Grant from Square Crypto,” BTCPay Server Blog, September 14, 2019, https://blog.btcpayserver.org/btcpay-foundation-announcement/.