BTCPay Server is a free, open-source platform that lets organizations process Bitcoin payments on their own infrastructure. Instead of routing transactions through a conventional payment processor, a business operates the invoicing and checkout layer itself or selects a trusted host. Payments can go directly to its own wallet.
This makes BTCPay Server useful for online stores, digital products, international businesses, donation projects and physical retailers. It supports Bitcoin on-chain and Lightning, automates invoices and returns payment status to the store or application.
What is BTCPay Server?
BTCPay Server is an open-source Bitcoin payment processor. It creates time-limited invoices, monitors the blockchain or Lightning backend and updates an order's status. The merchant controls infrastructure, data and wallet configuration. According to the official project description, BTCPay Server charges no processing fee; infrastructure, network and operational costs still apply.
One instance can manage multiple stores, each with its own configuration, wallet and integrations. This is useful for agencies, groups and platforms, but it requires clear separation of users, permissions and backups.
How a payment works
- Order: The store sends the amount, currency and order reference to BTCPay Server.
- Invoice: BTCPay creates an invoice with a Bitcoin address or Lightning invoice and a time-limited exchange rate.
- Payment: The customer pays directly from a wallet.
- Detection: BTCPay monitors payment and confirmations and updates invoice state.
- Callback: The store receives status through the API or a webhook and can release the order.
A robust integration also handles expired, underpaid, overpaid and late invoices. These exceptions must remain understandable and recoverable.
Bitcoin on-chain and Lightning
On-chain payments are suitable for larger amounts or flows that do not require confirmation within seconds. Lightning enables fast, low-value payments. BTCPay Server can expose both options in one checkout.
Lightning adds operational work: an own node needs channels, inbound liquidity, backups and monitoring. The official Lightning documentation describes own nodes and supported alternatives. A Lightning wallet is generally a hot wallet, so limits and risk models must be explicit.
More than a checkout
BTCPay Server includes applications for practical business processes:
- Point of Sale: product catalog, cart and tips for physical sales.
- Payment Requests: payment requests with configurable amounts and validity.
- Donations and crowdfunding: campaigns and public progress.
- Payment Button: an embeddable payment function for websites.
- Wallet management: transactions and refunds within the selected wallet architecture.
The official app documentation explains these modules.
Store integrations, API and webhooks
Integrations are available for common commerce platforms, while custom products connect through the Greenfield REST API. It covers stores, invoices, payment methods, wallet operations and more. Webhooks notify applications about state changes. The BTCPay documentation recommends Greenfield for new custom integrations.
A reliable integration stores keys server-side, validates webhook signatures, processes events idempotently and reconciles orders regularly. Duplicate or delayed events must never cause duplicate fulfillment.
Self-hosting or a third-party host?
Self-hosting offers maximum control over metadata, updates, wallet connections and availability. The official Docker deployment is a sensible starting point for many production installations. Server hardening, TLS, updates, monitoring and backups remain the operator's responsibility.
A third-party host reduces administration but can see account and payment metadata and may restrict features. The official hosting documentation recommends evaluating trust, Lightning access and export options.
Security and operations
- store and test wallet recovery data offline;
- separate API keys per application with minimum permissions;
- protect administration with strong accounts and multi-factor authentication;
- back up databases, configuration and relevant Lightning data;
- test updates in staging first;
- monitor availability, disk space, node sync and payment events;
- document refund and incident procedures.
“Non-custodial” does not mean “maintenance-free.” Whether private keys remain exclusively with the merchant depends on the chosen wallet and Lightning configuration.
BTCPay Server or LNbits?
BTCPay Server focuses on complete merchant workflows: checkout, invoice status, store integrations and point of sale. LNbits is more oriented toward a modular Lightning wallet, API and extension layer. Both can coexist in the right architecture.
Who is BTCPay Server for?
It fits organizations that want to accept Bitcoin and Lightning independently, control payment data and integrate payments with stores, ERP systems or internal applications. A hosted service may be enough for low volume. Business-critical processes benefit from a professionally designed, monitored and documented installation.
BTCPay Server projects with BIT62
BIT62 supports operating-model selection, Docker deployment, node connectivity and store or API integration. This includes checkout UX, webhooks, monitoring, backups, updates and clear operational documentation.