Comparison
BTCPay Server vs OpenNode
Self-hosted, zero-fee, you-run-the-server vs hosted, percentage-fee, they-run-the-server. The most common Lightning processor decision.
Affiliate disclosure. Some links on this page are partner links. LN Cash may earn a commission if you sign up. This does not change which tools we recommend — see our methodology and the full disclosure.
If you’ve decided to accept Lightning payments and you’re not running a one-person Lightning Address tip jar, this is the decision you’re going to make. Self-hosted (BTCPay Server) or hosted (OpenNode).
Short answer: if you can run a Linux server or pay a consultant to do it, BTCPay Server is almost always the right long-term choice. If you can’t or won’t, OpenNode is a perfectly reasonable starting point — just keep your integration thin so you can migrate later.
At a glance
| BTCPay Server | OpenNode | |
|---|---|---|
| Hosting | Self-hosted (or managed BTCPay host) | Hosted by OpenNode |
| Custody | Non-custodial — you keep keys | Custodial — OpenNode holds funds until withdrawal |
| Fees | 0% platform fee; free on Raspberry Pi, ~$8/month on managed host | Lightning↔Lightning between OpenNode accounts: free. On-chain withdrawals: 1% |
| KYC | None | Required |
| Fiat settlement | Manual (you handle conversion) | Built in for supported regions |
| Setup time | Hours to days | Minutes |
| Lightning implementations | LND or Core Lightning (CLN) | Hosted; abstracted from you |
| Ecommerce plugins | 30+ integrations: WooCommerce, Shopify V2, Magento, PrestaShop, Cal.com, Zaprite, Ghost, ECWID, GiveWP | Shopify, WooCommerce, Magento, Drupal Commerce |
| Best for | Long-term cost, sovereignty, technical operators | Speed to first payment, non-technical merchants |
How they differ in practice
Setup. OpenNode is “sign up, get API keys, integrate” — a process measured in minutes. BTCPay is “spin up a $5 VPS, run the Docker install script, configure your Lightning node, fund a channel, point your DNS, install plugins” — a process measured in hours or a weekend.
Custody. OpenNode holds your sats from the moment a customer pays until you withdraw. BTCPay never touches them — payments settle directly to the Lightning node you run. Different trust models, both legitimate.
Fees. OpenNode charges 1% on on-chain withdrawals; Lightning-to-Lightning transfers between OpenNode accounts are free. BTCPay’s software is free; your costs are server hosting (free on a Raspberry Pi, ~$8/month on Voltage or LunaNode) and the time you spend on operations. For a merchant whose payouts mostly stay on Lightning, OpenNode’s effective fee is small. For a merchant who needs frequent on-chain settlements at scale, BTCPay’s savings compound quickly.
Compliance burden. OpenNode requires KYC and operates in a regulated way; their compliance is your shield in jurisdictions that care. BTCPay puts compliance on you — you are running the payment infrastructure and any obligations attach to you.
Resilience. OpenNode is one company; if they’re down, you’re down. BTCPay is software you run; if it’s down, it’s because of something you can usually fix. The trade-off is operational maturity: you also have to be the one who fixes it.
When to pick BTCPay Server
- You expect non-trivial volume and don’t want a percentage haircut on every payment.
- Self-custody matters — you don’t want a custodial intermediary holding sats.
- You (or someone on retainer) are comfortable with Linux, Docker, and basic networking.
- You want ecommerce plugins that are first-class to the Bitcoin community (the WooCommerce plugin is very polished).
- You want the option to use additional features: refunds via Lightning, payment-channel-level analytics, multi-currency display.
A reasonable cheat: use a managed BTCPay host like Voltage or LunaNode (~$8/month). You get most of the cost benefit and self-custody guarantees of BTCPay, without running the server yourself.
When to pick OpenNode
- You want to ship Lightning payments this week, not next month.
- You’re in a country where fiat settlement is supported and you want to remove Bitcoin price volatility from your accounting.
- You’re a non-technical merchant, or you don’t have engineering time to spare on payment infrastructure.
- Your volume is low enough that the percentage fee doesn’t bite.
- You explicitly want a third party in the loop — useful in markets where regulators prefer regulated intermediaries.
The honest middle path
A pattern we recommend frequently: start with OpenNode, plan to migrate to BTCPay.
Build your integration with a thin abstraction layer so swapping providers is a config change rather than a rewrite. Use OpenNode to validate that customers actually want to pay in Lightning. Once you have meaningful volume, deploy BTCPay (or hire someone to), migrate, and pocket the percentage fees.
This is also a reasonable answer if you’re a developer asking “which one should I integrate first?” — OpenNode is faster to learn, and the API patterns transfer well.
What we did not test
This page is an editorial draft. Hands-on test results — actual signup screenshots, deployment walkthrough, fee verification at current rates — are scheduled for the next review. Verify pricing and country support with each provider before making a final decision.
Next step
- Wallet question? See the best Lightning wallets.
- Specific country considerations? Check the country guides.
- Getting set up? Read how to accept Lightning payments.
FAQ
Which one is cheaper? +
BTCPay Server long-term, by a lot — there are no platform fees, only your server hosting cost (free on a Raspberry Pi, ~$8/month on a managed host like Voltage or LunaNode). OpenNode charges 1% on on-chain withdrawals; Lightning-to-Lightning transfers between OpenNode accounts are free. For a merchant doing meaningful on-chain volume, BTCPay wins on cost. For a merchant whose receiving and payouts mostly stay on Lightning between OpenNode accounts, the fee difference is smaller than it looks.
Is BTCPay Server really free? +
The software is free and open source. You pay for: a Linux server to run it on, time to set it up and maintain it, and (optionally) inbound Lightning liquidity from a service like Lightning Network+ or Voltage. The total operational cost is small, but it is not zero — it's just not paid to BTCPay.
Does OpenNode work outside the US? +
Yes, in many countries — but availability and fiat-settlement options vary. Verify country support on OpenNode's pricing page before you commit to building around it.
Can I switch from OpenNode to BTCPay later? +
Yes. The customer-facing payment experience (invoice → QR → confirm) is almost identical. You'd swap out your backend integration. Plan for it from day one by keeping the integration logic isolated.