BTCPay Server vs NoHoldPay

The BTCPay trust model without the server

NoHoldPay asks for the same inputs a BTCPay store does. An xpub covers the Bitcoin-family chains, and the server never sees a private key. On Ethereum, TRON, and Solana every payment gets its own forwarder contract with your treasury address compiled into it, so the funds have exactly one place they can go. XRP, Stellar, and TON payments carry a reference that lands them in an account you already control. Monero runs from a view key, which lets us observe incoming payments and do nothing else. The chain list on this page renders from the live platform, and it includes networks that BTCPay's own FAQ routes to community plugins it may remove when maintenance lapses.

The pricing is one number. 0.5% per confirmed payment with no fixed fee, deducted from a credit you prepay, and the customer's transfer is never touched. A $50 signup credit covers roughly your first $10,000 of processed volume, so you can compare against 0% with real payments before the number costs you anything. What the fee buys is the entire operations column of BTCPay's own deployment docs: the servers, the node connections, the watcher that credits each payment, and every upgrade.

Two things come with the managed side that a self-hosted stack does not offer. On eligible EVM stablecoin routes your customer pays USDC with no ETH in their wallet, because a relay covers the network fee, and on Solana sponsored signing does the same for SPL USDC and USDT. BTCPay's USDt plugin has no fee abstraction, so its payers need the gas token in hand. And since sovereignty is the whole point for this audience, the downloadable Recovery Kit and its offline CLI re-derive every forwarder address you were ever assigned, with NoHoldPay gone entirely. The exit BTCPay gives you by architecture, we give you as a file you keep.

The line items of running your own gateway

None of these costs are hidden, which is to the project's credit. Their deployment docs price a VPS between $10 and $70 a month depending on provider, and the low end is a genuinely easy one-click LunaNode deploy. The recurring work starts after the deploy. Docker upgrades are yours to schedule and test. The node your instance watches is yours to keep synced. Lightning adds channel opens, which their docs describe as an expensive setup during high-fee environments, followed by liquidity management for as long as you accept payments. Releases can also retire things you depend on: v2.4.0, shipped June 2026, discontinued the LNBank and Lightning Charge backends, and every store running either one inherited a migration that month.

The documented way around all of this is a third-party BTCPay host, and here their docs are admirably blunt. A hot wallet on someone else's instance 'gives the host complete access to your funds', so the only clean configuration on a shared host is a watch-only xpub setup. Lightning is always hot, so it never qualifies. And since the December 2025 release, host operators can charge recurring access fees through Server Monetization, which means the free-hosted route can stop being free. NoHoldPay removes that fork entirely. Keys never exist on our side in any configuration, so there is no setting in which the operator could reach your funds.

Switching from BTCPay Server

If you run a BTCPay store today, you already own the main input. A watch-only store is built on an xpub, and the same xpub works here unchanged, so Bitcoin-family settlement continues to the wallet you use now. Create an account with an email, paste the wallet material, and swap the integration. WooCommerce stores install our plugin next to the BTCPay one and flip gateways when ready. API integrations replace one create-invoice call and one webhook consumer. The $50 credit covers roughly your first $10,000 of volume while both gateways run side by side. Be clear-eyed about the trade, though: BTCPay puts no third party in the payment path, and NoHoldPay is one. Our answer is that funds never wait anywhere we control, and the Recovery Kit keeps every address derivable with us gone.

Where BTCPay Server is the better fit

Weigh your own capacity first, because for a real slice of this audience BTCPay is simply the right answer. If your business is Bitcoin-first, and especially if Lightning matters, BTCPay has a mature first-class implementation and NoHoldPay has none shipped. If literal 0% matters more than your ops time, they win on price by definition. The code is MIT licensed and auditable, subscriptions have been native since December 2025, and no third party touches the payment path at any point. A merchant with the skills to maintain a server, or the budget to pay someone who does, keeps more sovereignty there than any managed gateway can offer, ours included.

Common questions

Is BTCPay Server actually non-custodial?

Yes, without qualification. Your own instance derives payment addresses from your wallet, either watch-only from an xpub or from a hot wallet on your server, and no platform exists that could hold funds. The caveat comes from their own docs: a hot wallet on a third-party host gives that host access to your funds, so shared hosts are only clean with watch-only setups.

Does NoHoldPay have Bitcoin Lightning?

No. NoHoldPay ships no Lightning support, while BTCPay's Lightning is mature, with CLN, LND, and Eclair backends. If Lightning is a requirement, BTCPay wins this comparison outright. The trade is operational: running Lightning means funding channel opens and managing liquidity on an always-hot node, work their own docs assign to the merchant.

Why pay a fee at all when BTCPay charges 0%?

The fee prices the operations, nothing else. With BTCPay the software is free while the server, upgrades, node maintenance, and Lightning liquidity are yours, at $10 to $70 a month in hosting per their docs plus your time. NoHoldPay's flat rate covers all of that while payments still settle to addresses derived from your own wallet material.

Can I move a BTCPay store to NoHoldPay without changing wallets?

Usually, yes. A watch-only BTCPay store is built on an xpub, and that same xpub works in NoHoldPay unchanged, so Bitcoin-family settlement continues to the same wallet. Add account addresses or a Monero view key for chains BTCPay does not cover in core. Both gateways can run in parallel while you compare real payments.

What does BTCPay Server offer that NoHoldPay does not?

A real list. Mature Lightning, 0% fees, MIT-licensed code you can audit and modify, self-hosted subscriptions since December 2025, a plugin marketplace, and integrations well beyond our WooCommerce and OpenCart pair, including Shopify, Ghost, Wix, and Odoo. Above all, a payment path with no third party in it anywhere. If those outweigh the ops burden, choose BTCPay.