BTCPay Server

What is BTCPay Server?

BTCPay Server is an open-source, self-hosted Bitcoin payment processor that lets merchants accept Bitcoin payments directly, without relying on a traditional third-party payment gateway to custody funds. BTCPay Server’s primary service is providing a payment platform (checkout, invoices, and payment notifications) that you run on your own infrastructure, so you maintain control over private keys and settlement.

Unlike hosted processors, BTCPay Server is software rather than a financial institution. It is not positioned as a bank and does not present itself as a regulated money transmitter or EMI; instead, it is a tool merchants can deploy to accept Bitcoin peer-to-peer. Because the software can be installed and run by anyone, BTCPay Server is globally relevant in practice, but real-world availability depends on whether you can host it in your region and comply with local tax and payments rules for your business.

A key implication of the self-hosted model is that BTCPay Server doesn’t “approve” merchants or provide country-by-country account availability the way a payment processor like Stripe would. Geographic limitations are mostly technical (your hosting environment, your access to Bitcoin infrastructure) and operational (your ability to manage your own node/wallet and comply with local laws). For businesses that prefer owning the payment stack and avoiding processor lock-in, BTCPay Server is commonly evaluated as a Bitcoin-native alternative to custodial crypto checkout solutions.

Key Features & Services

BTCPay Server focuses on the core building blocks required to accept Bitcoin payments in an e-commerce or invoicing flow. Because it’s self-hosted software, capabilities can also depend on configuration and your chosen integration method.

Self-hosted Bitcoin payment processing

BTCPay Server is designed to be run by the merchant (or their technical team) on their own server. This matters for businesses that want to avoid a third-party payment platform holding funds, setting payout schedules, or imposing account freezes. In a BTCPay Server setup, the merchant receives Bitcoin payments directly to wallets they control.

This architecture is particularly relevant for merchants who want to reduce dependency on a single provider and prefer a system that can keep working even if a hosted processor changes terms or discontinues service. It also shifts responsibility for uptime, security updates, and infrastructure monitoring to the operator.

Checkout, invoices, and payment notifications

BTCPay Server provides a checkout experience intended for online payments, typically including invoice creation and payment status tracking. For many merchants, a key requirement is confirming whether a customer has paid, and receiving callbacks/notifications that a payment is detected and confirmed.

In practical terms, this supports common merchant workflows:

• Creating a payment request for a specific amount
• Presenting a Bitcoin payment option to the customer
• Tracking whether the invoice is paid and when it’s confirmed
• Using payment status updates to fulfill an order or mark an invoice as settled

The exact confirmation policy (for example, whether you accept “paid but unconfirmed” transactions for digital goods) is a merchant decision that can be influenced by risk tolerance and average transaction size.

Integrations for e-commerce and custom apps

BTCPay Server is commonly used as a payment gateway component for e-commerce stores and custom checkout flows. Merchants typically evaluate it when they want Bitcoin acceptance inside an existing website, store platform, or bespoke ordering system.

Because it’s software-first, BTCPay Server is often compared on how well it can fit into:

• A hosted e-commerce storefront that needs a Bitcoin payment method
• A donation page that requires transparent payment tracking
• A SaaS billing flow that needs invoice-like payments

Integration effort varies. Some setups are relatively straightforward (plug-in style), while custom applications may require developer time to connect APIs, handle webhooks, and reconcile orders.

Direct control of funds and settlement

A defining feature of BTCPay Server is merchant custody: you control the destination of funds and the settlement timing because payments go to wallets you manage. For businesses that prioritize minimizing counterparty risk, this can be a significant difference versus custodial processors that receive funds first and then pay out.

This also changes accounting and treasury workflows. Instead of receiving fiat payouts, you may be holding Bitcoin on your own balance sheet unless you choose to convert elsewhere. That can be a benefit for Bitcoin-native companies and a downside for businesses that require fiat settlement for payroll, suppliers, or taxes.

Privacy and reduced processor dependency

BTCPay Server is positioned around reducing reliance on third-party intermediaries. In general, a self-hosted payment gateway can reduce the amount of transaction and customer metadata shared with external processors, since your server handles the checkout and invoice logic.

That said, privacy outcomes depend on the merchant’s hosting provider, logging configuration, analytics stack, and how their Bitcoin infrastructure is set up. Merchants should also consider operational best practices (secure hosting, backups, access controls) to avoid introducing risk through misconfiguration.

Pricing & Fees

BTCPay Server is open-source software, and the project is widely understood to be free to use in the sense that there is no mandatory per-transaction fee charged by the BTCPay Server software itself. However, running BTCPay Server is not “costless” because you typically incur infrastructure and operational expenses (hosting, maintenance, and potentially Bitcoin node resources).

BTCPay Server does not publish a traditional processor pricing schedule (e.g., “2.9% + $0.30”) because it is not a hosted payment processor that charges interchange-like fees. What you pay will depend on how you deploy it.

Cost component	What BTCPay Server discloses	What you should expect in practice
Software license cost	No mandatory license fee (open-source)	$0 for the software itself
BTCPay Server “processor” fee	No BTCPay Server per-transaction fee	You still pay Bitcoin network miner fees indirectly (usually paid by the sender, but it depends on wallet behavior and fee policy)
Hosting/infrastructure	Not a fixed BTCPay Server price	Monthly server/VPS costs vary by provider and performance needs
Maintenance & security	Not priced by BTCPay Server	Internal time or contractor cost for updates, monitoring, backups
FX conversion to fiat	Not provided by BTCPay Server as a built-in paid service	If you need fiat settlement, you may use an exchange or third-party service with its own fees and spreads

What isn’t publicly standardized: BTCPay Server does not provide a single “all-in” fee schedule because there is no centralized account plan. If you need managed hosting or a service provider to run it for you, that provider may charge setup fees and monthly management costs (these are external to BTCPay Server).

Pros and Cons

Pros

• Self-hosted architecture means you can avoid relying on a third-party payment processor to custody funds, which may reduce counterparty risk for some merchants.
• The software model avoids the typical percentage-based processor fee structure, which can be attractive for higher-ticket items where card fees are material.
• Merchants can design settlement workflows around their own wallets and treasury policies, rather than waiting for scheduled payouts from a processor.
• Open-source software can be audited and adapted, which can matter for teams that want transparency or custom functionality.
• The platform is oriented toward Bitcoin-native checkout flows (invoices and payment status), which suits businesses that want a dedicated Bitcoin payment gateway.

Cons

• Running your own payment infrastructure adds operational responsibility, including server security, updates, backups, and uptime monitoring.
• BTCPay Server is not a bank or regulated payment institution, so businesses needing fiat settlement, chargeback handling, or card acceptance will need separate providers.
• If you require automatic conversion to fiat for accounting simplicity, you will likely need an external exchange or service, adding integration and fee complexity.
• Technical setup and integration effort can be higher than enabling a hosted crypto checkout button, especially for custom stacks.
• Bitcoin price volatility can introduce treasury and accounting challenges if you hold BTC rather than converting quickly.

Who Is BTCPay Server Best For?

BTCPay Server is best suited for merchants and organizations that specifically want to accept Bitcoin and are comfortable operating (or outsourcing) a self-hosted payment gateway. It’s a practical fit when ownership and control of the payment flow matters more than convenience.

Common best-fit profiles include:

• Small to mid-sized online merchants that want an alternative to card processing for certain customer segments, especially where typical card fees make margins tight.
• Bitcoin-native businesses that prefer to receive funds directly in BTC and manage their own custody, rather than using a custodial processor.
• Nonprofits and donation-funded projects that want transparent, direct-to-wallet contributions and invoice-style payment tracking.
• Developers and technical teams building custom commerce or billing systems that can integrate a Bitcoin payment platform via APIs and webhooks.
• International sellers who face payment acceptance limitations with mainstream processors in certain regions, and can legally accept Bitcoin under local rules.

Who may not be a good fit:

• Merchants needing card payments, chargebacks, and consumer financing as part of the same checkout; BTCPay Server is focused on Bitcoin payments rather than card rails.
• Businesses that require guaranteed fiat payouts into a bank account without managing exchange relationships.
• Teams without technical capacity to manage hosting, security, and incident response, unless they use a trusted managed service provider.

BTCPay Server Alternatives

• BitPay — A hosted crypto payment processor that can be easier for merchants who want a managed service and optional fiat settlement, at the cost of relying on a third party.
• CoinGate — Often considered by merchants who want a more traditional, provider-managed crypto checkout with built-in settlement options rather than self-hosting.
• OpenNode — A Bitcoin-focused payments provider that may suit businesses prioritizing quick setup and hosted infrastructure over operating their own server.
• Stripe — A card-first payment processor that is a better fit if your priority is broad card acceptance, fraud tooling, and conventional checkout flows rather than Bitcoin-native payments.
• Coinbase Commerce — A common alternative for merchants wanting a hosted crypto checkout experience with simpler deployment, though it changes the custody and dependency model compared to BTCPay Server.