Switching · checked 2026-09-02
Best BTCPay Server alternatives in 2026
Merchants replacing BTCPay Server land on one of three options. NOWPayments suits keeps the non-custodial model, hands the server back to somebody else, and publishes the widest asset list here. Plisio fits non-custodial at a published 0.5%, with maintained plugins for five ecommerce platforms. Coinsnap covers hosted Bitcoin and Lightning with euro payout to a bank account, for merchants who wanted the assets and not the server. Rates below reflect published rates checked in August 2026.
Quick verdict
NOWPaymentsKeeps the non-custodial model, hands the server back to somebody else, and publishes the widest asset list here.
PlisioNon-custodial at a published 0.5%, with maintained plugins for five ecommerce platforms.
CoinsnapHosted Bitcoin and Lightning with euro payout to a bank account, for merchants who wanted the assets and not the server.
Why do merchants look for a BTCPay Server alternative?
There is no fiat settlement of any kind, so a merchant needing bank currency has to arrange conversion through a second relationship. Checked 2026-09-02 against the provider's own page.
Support is a community chat room and a public issue tracker, with no published response commitment behind either. Checked 2026-09-02 against the provider's own page.
BTCPay Server at a glance
| Processing from | 0% |
|---|---|
| Assets | Not published |
| Merchant verification | None stated |
| Custody | Non custodial |
| Checked | 2026-09-02 against its own pricing page |
None of this is a recommendation to leave. It scores 7.7 against every other indexed provider on one set of weights, and whether that ordering matches your priorities is what the methodology page exists to let you test. The full card has the detail.
How do these alternatives compare?
Method| Gateway | Score | From | Assets | Verification | Settles fiat | Discloses |
|---|---|---|---|---|---|---|
| BTCPay Server | 7.7 | 0% | None stated | No | 74% | |
| NOWPayments | 8.0 | 1% | 350 | Not disclosed | 68% | |
| Plisio | 6.9 | 0.5% | 12 | Not disclosed | 68% | |
| Coinsnap | 4.8 | — | 1 | Not disclosed | Yes | 53% |
3 best alternatives to BTCPay Server
NOWPayments
Who it fits. Keeps the non-custodial model, hands the server back to somebody else, and publishes the widest asset list here.
| Processing from | 1% |
|---|---|
| Conversion | Not published |
| Payouts | Not published |
| Assets | 350+ across Bitcoin, Ethereum, BNB Chain, Tron, Solana, Polygon, Litecoin |
| Verification | Not disclosed |
The full NOWPayments card has its strengths, its gaps and the fields it declines to publish.
Plisio
Who it fits. Non-custodial at a published 0.5%, with maintained plugins for five ecommerce platforms.
| Processing from | 0.5% |
|---|---|
| Conversion | Not published |
| Payouts | Not published |
| Assets | 12+ across Bitcoin, Ethereum, Litecoin, Monero, Dash, Zcash, Tron |
| Verification | Not disclosed |
The full Plisio card has its strengths, its gaps and the fields it declines to publish.
Coinsnap
Who it fits. Hosted Bitcoin and Lightning with euro payout to a bank account, for merchants who wanted the assets and not the server.
| Processing from | — |
|---|---|
| Conversion | Not published |
| Payouts | Not published |
| Assets | 1+ across Bitcoin, Lightning |
| Verification | Not disclosed |
The full Coinsnap card has its strengths, its gaps and the fields it declines to publish.
On this page
What you are actually giving up#
A fee of exactly zero, which no hosted replacement can match, and the certainty that nobody in the payment path can be compelled to freeze anything. Both are structural rather than contractual, and neither survives a move to a service.
The twenty-three plugin integrations go with it. Two of the three alternatives here publish fewer, and the widest-coverage one publishes none at all, which for a shop is a step backwards disguised as an upgrade.
The operational load is the usual reason people leave#
Somebody rents the server, applies the updates, watches the Lightning channels and gets paged when an invoice stops confirming. That person is on your payroll, and businesses discover the cost of that when the person leaves.
It is not a fault in the software. It is the bill that replaces the percentage, and a business without an engineer was always going to find it larger than one percent of revenue.
No euros, and no way to add them#
Payments arrive as bitcoin in a wallet you hold. There is no conversion step, no bank leg and no schedule, because a system that never touches your funds cannot deliver any of those.
Only one of the three replacements fixes this cleanly. If bank currency on a timetable is the requirement, that narrows this page to a single option before anything else is weighed.
Where each replacement lands#
NOWPayments keeps the property that mattered most — settlement to a wallet you control — and charges a flat 1% for removing the server from your life. Its asset list is the longest in this index by a distance.
Plisio keeps the same custody model at 0.5% and adds maintained plugins for five platforms, which is the closest thing here to a like-for-like swap with the operations handed over.
Coinsnap is the odd one and often the right one#
It is the only replacement that keeps the Bitcoin-and-Lightning shape exactly and adds a euro payout to a bank account. For a shop that ran this software to take bitcoin over a counter, that is precisely the missing half.
It publishes no rate at all, which is the price of the convenience. Establish what it costs before switching, because a zero you understood is being traded for a number you do not.
The plugin shelf will shrink#
Twenty-three named integrations is more than any commercial provider in this index offers, and the replacements publish seven, six and none respectively. If your platform is outside the mainstream, check before committing.
Ghost, Pretix, Invoice Ninja and the rest exist because somebody ran them personally. A company builds the plugins its sales pipeline justifies, and yours may not be among them.
Key custody moves or it does not#
Two of the three alternatives are non-custodial, so the key-management problem you already solved stays solved and the migration is mostly configuration. That is unusual and worth exploiting.
The third holds funds until you withdraw, which returns key management to a provider and returns provider risk to you. Neither direction is wrong; both should be a decision rather than a side effect.
What onboarding will look like now#
You have never been verified by anybody, because there was nobody to verify you. Every replacement here is a company, and two of the three publish nothing about what they will ask for.
Plan for a file rather than a form. Ask what applies in your jurisdiction, in your vertical, at your expected volume, and ask before you migrate a live checkout.
What to check on the way out#
That your existing wallet keeps working. On the two non-custodial replacements the same extended public key can usually carry over, which means the addresses your accounting already knows do not change.
That your invoice history is exported before the instance goes down. It is your database and nobody else has a copy, which is the flip side of having run everything yourself.
The case for staying#
If a competent person already runs the instance and it has not broken, leaving costs money for the first time in the life of this integration. One percent of a growing revenue line is a real number and it compounds.
The honest test is whether the operational load falls on somebody who has other work. If the answer is no, this page is a comparison you do not need to finish.
How to migrate from BTCPay Server
- Export the invoice database first. Nobody else holds a copy of your payment history, so pull the full invoice export from the instance before scheduling any shutdown. Accounting will need it long after the server is gone.
- Carry the same wallet across where you can. Both non-custodial replacements accept an extended public key. Supplying the one already in use keeps the addresses your bookkeeping recognises and removes an entire reconciliation exercise from the switch.
- Rebuild the plugin path deliberately. Check that your storefront platform appears on the replacement's own integration list rather than through a third-party plugin. A community connector with no maintainer is a checkout outage waiting for the next platform release.
- Run both in parallel for a fortnight. Keep the existing instance taking payments while the replacement handles a share of traffic. Two weeks covers a full billing cycle and surfaces webhook and confirmation differences before the old system is switched off.
- Decide who owns the fiat leg. If the replacement converts to bank currency, somebody has to own the reconciliation between the crypto amount received and the euros credited. Name that person before the first settlement rather than after the first month-end.
Questions merchants ask
Why do merchants leave BTCPay Server?
There is no fiat settlement of any kind, so a merchant needing bank currency has to arrange conversion through a second relationship. Support is a community chat room and a public issue tracker, with no published response commitment behind either. Both points were checked against the provider's own pages on 2026-09-02.
What is the closest alternative to BTCPay Server?
NOWPayments is the closest substitute for most merchants: Keeps the non-custodial model, hands the server back to somebody else, and publishes the widest asset list here. It scores 8.0 against 7.7 on the same published weights.
Is switching crypto payment gateway difficult?
Small technically, larger operationally: reconciliation and refunds change, and neither appears in an integration guide.
Will I lose payment history when I switch?
Not if you export before closing, which is the step everyone does last. No retention period is published.