Best Non-Custodial Crypto Payment Gateways
Choose BTCPay Server if you want Bitcoin paid straight into your own wallet and someone can run the checkout software. Consider Blockonomics if you'd rather have a service watch your wallet for payments and tell your store. Either way, find out who holds the keys and who keeps checkout running. Non-custodial describes who controls incoming funds. It doesn't make checkout secure, give you unrestricted access or deliver bank money. The better choice is the one you can keep running and reconcile when an order goes wrong.
The best non custodial crypto payment gateway for your shop gives you control of incoming payments without leaving a job that nobody owns. Start with BTCPay if you can run the software, and look at Blockonomics if a hosted monitoring service fits better. Either way, follow a payment from the customer to the person who can spend it.
We read the original software, hosting, payment, platform and policy documents listed below on 15 October 2026 and worked through a hypothetical budget example. We didn't create accounts, install software, connect wallets or send payments. The shortlist rests on one test: who controls an ordinary incoming payment. The cards follow our overall formula: cost 25%, fiat 15%, licences 15%, coins, integrations, features and support 10% each, and onboarding 5%. Those weights compare listed inputs, not your operator, security, eligibility or total bill, and our methodology explains their limits.
Which non-custodial gateway should you consider first?
Start with BTCPay if you want control of the software and Blockonomics if you want a service watching your wallet. BTCPay can create Bitcoin invoices from public wallet information while the keys that spend the money stay off the server.[1] Blockonomics describes generating receiving addresses, detecting payments and notifying your store, with ordinary receipts going into your wallet.[15] If someone already looks after your shop and its payment records, running more of the system can make sense. If you're struggling to keep orders reconciled, a service has to lift that burden in a way you can name.
The money headlines on the cards cover two setups: BTCPay run by you or your developer with an external Bitcoin wallet, or Blockonomics's ordinary Bitcoin service after the first ten account transactions. Whether either fits depends on your company, owners, activity and customers. Neither headline is the whole bill: hosting, the time of whoever runs the software, network and conversion fees and returns all cost extra, and a cost we couldn't price isn't free. BTCPay's zero is only the project's own charge, and Blockonomics's percentage is a service bill of its own, not a cut of each payment.
- 12
BTCPay ServerFor a Bitcoin shop with someone to run the software
57/1000%- External-wallet receipt can keep spending keys off the server
- You control the payment software you run
- Described workflows for orders, returns and prepaid renewals
- Someone has to do the operating work, and a host-held hot wallet, shared Lightning or a conversion partner changes how much control you keep.
- 25Blockonomics
For a shop that qualifies and wants a service to watch its wallet for payments
32/1001%- Ordinary payments go to your own wallet, according to Blockonomics
- Store notifications and platform guides are available
- The ongoing service bill is kept apart from customer payments
- The first ten account transactions are a one-off allowance, not a monthly band. Service credit, whether checkout keeps working, returns and bank access each need their own attention.
Our BTCPay review covers what running the software involves.
What does non-custodial mean for a merchant?
It means asking who can spend an incoming payment and whether another company has to release it to you. That's the practical test we use for ordinary receipts, not a legal custody opinion for every jurisdiction or product a brand sells.
A public wallet connection lets checkout recognise your payments without holding the keys that spend them. A hot wallet keeps those keys on a connected system. BTCPay describes both external signing and server-stored hot keys, and the two leave you with different levels of control.[4]
Follow the customer's payment. If a processor first credits a managed balance and then forwards it to your wallet, you're buying a different product from direct collection, whatever the final address. The BTCPay versus BitPay comparison covers that other kind of purchase. A consumer wallet from the same brand says nothing about how its merchant checkout receives money.
Money you've already received and the instructions for future payments are two different risks. BTCPay's hosting guide warns that a host can hold hot-wallet keys or replace receiving information, diverting future payments, and a compromised server you run yourself can change those instructions too.[2] External keys protect what you've already received, but the shop can still show the next customer the wrong destination.
How do the wallet and hosting setups compare?
The same software can leave you with very different control, so compare the specific setup. BTCPay's administrator controls the available methods and features, and users and operators have different responsibilities.[5] Before you hand over the operating work, agree who can change payment settings and who investigates a disputed payment.
| Setup | Spending or receipt control | Who keeps checkout working? | Catch for the owner |
|---|---|---|---|
| BTCPay you run, with an external Bitcoin signer | Your external keys control spending | You or the developer who runs the software | Someone still has to watch the receiving instructions and keep independent records |
| BTCPay you run, with a hot wallet or your own Lightning node | Spending authority sits on your own system or node | Your operator and whoever owns the wallet | Internet exposure, permissions, backups and Lightning capacity all need attention |
| BTCPay on a shared host, external wallet | You control what's already been received | The host runs the software and you maintain your shop's connection | The host controls features and can affect future payment instructions |
| Hot wallet held by the host, or shared internal Lightning | The host can sign, or receives the money first | The host, with you reconciling the shop's records | Left out of this guide's test of direct merchant-controlled receipt |
| Blockonomics ordinary wallet flow | Payments go to your wallet, and the service watches for them and notifies your store | Blockonomics for its service, you for the wallet, website and orders | You depend on the account staying intact, optional browser-wallet keys and future receiving instructions |
Blockonomics's wallet guide includes an optional browser wallet, as well as public-wallet-data and Ethereum destination options. We haven't evaluated the extension or its keys, so treat that as its own decision.[18] Nothing in the service description supports a claim that the setup is immune from theft.
The comparison table covers the same two setups as the cards. Its software-zero and service-fee rows aren't whole-operation offers or bank proceeds. The asset and platform counts are dated or partial lists, not methods you've enabled, and the software's no-document, no-reserve labels don't extend to hosts or partners. Where we found no evidence on banks, reserves, licences or native features, it stays unknown.
BTCPay Server | Blockonomics | |
|---|---|---|
| Score | 57/100 · #12 | 32/100 · #25 |
| Payment fee | 0% | 1% |
| Cost on $10k/month | $0.00 | $100 |
| Pays out to bank | Not stated | Not stated |
| Stablecoin networks | USDT: Liquid, TRC20 (plugin) | USDT: ERC20 |
| Coins | 14 | Not stated |
| Custody | Non-custodial | Non-custodial |
| Merchant KYC | None | None |
| Rolling reserve | none | Not stated |
| Licence | Not stated | Not stated |
| Plugins | WooCommerce, Shopify, PrestaShop, Magento, BigCommerce, Odoo | WooCommerce, WHMCS, PrestaShop |
| Legal entity country | Not stated | Not stated |
| Founded | Not stated | Not stated |
Which fits these five business situations?
Choose by how your customers pay and what work you can support. If the flow doesn't suit the wallets they use, or nobody can sort out a mismatch between a payment and an order, holding the keys still leaves you with a checkout that doesn't work. Our processor selection guide helps turn these cases into requirements you can hand a developer.
| Your situation | Starting preference | Why it could fit | Catch to resolve |
|---|---|---|---|
| Bitcoin shop with someone who can run software | BTCPay with an external signer | You run checkout and receive into your own wallet | Pay for the operating work and cover absences |
| Small-ticket shop considering Lightning | BTCPay with enough capacity on a node you own | BTCPay describes Lightning for the same software | Receiving capacity, routing services and support all need attention, and receipt on a shared host works differently |
| Store on a particular platform or using a particular token | Check the exact integration at either one | Published guides give you a starting point | The wallet, network and package you enable, and how orders and returns really behave, all have to fit |
| Membership or credit business | BTCPay's renewal setup | Reminders or prepaid credit can suit the service | Access in your application, used-up credit and customer communication stay your job |
| Business that has to pay bills in bank money | Neither, until you've found a way to convert | Direct crypto receipt can be the first step | Conversion approval, all the charges and money arriving in your bank are further steps |
For Lightning, BTCPay treats a merchant's own node and a host's shared internal wallet as different setups, and incoming capacity and routing policies matter.[3] We haven't found a Blockonomics Lightning option, so BTCPay's capability doesn't carry over to it.
What will you pay beyond the advertised fee?
Budget the whole operation and treat the published charge as one line in it. The figures here cover only BTCPay you run with external Bitcoin receipt, or Blockonomics's ongoing ordinary Bitcoin service after its account allowance, and they're before the other costs above.
BTCPay charges nothing for the project software, but its deployment FAQ says you need hosting and continuous operation.[6] Blockonomics publishes an ongoing 1% after the first ten account transactions, across plugins and API, and sends its own bill. A monthly bill under $10 carries forward, and unpaid bills can eventually interrupt new checkout.[16] Moving the calculator's sales slider doesn't reset the account allowance.
The calculator shows only Blockonomics's ongoing service fee, in USD, for an account that has already used its allowance. It doesn't model how the crypto bill is denominated or valued, its timing, service credit or the initial allowance, and it leaves out the other costs above. “Lowest”, the difference and the annual figures cover only these inputs, and the annual numbers assume twelve identical months. None of them is a deduction from a customer's payment, a bank receipt or a complete saving.
- BlockonomicsLowest estimate
$100$100 1.00%
Published rate estimates only. Provider minimums, network, conversion, bank and account charges may be extra.
The buyer's own network fee and your later transfer cost are different expenses. BTCPay's Stores FAQ describes an optional network-cost surcharge at checkout, and it doesn't replace the miner fee the buyer pays.[10] Tell your customers before they pay. The calculator guide explains why a subtotal can't cover costs it leaves out.
Does prepaid service credit give you another revenue balance?
No. Blockonomics's prepaid fee credit pays its service bills, while customer payments follow the merchant-wallet flow its docs describe, so keep them as different records when you reconcile. Its Terms say credit can't be redeemed for cash or crypto and expires after five years, and that the transaction fee is kept when a merchant refunds a sale.[17] We read those Terms on 15 October 2026 and couldn't find an effective date.
A bill that carries forward is still owed, and an automatic deduction from fee credit isn't collection from your customer's wallet. The pricing guide also says unrelated receipts into a linked wallet may be counted for billing, so if that wallet also receives money for another purpose, the service statement and your sales export may cover different activity. Reconcile the included transactions with your order records.
Which assets, wallets and store platforms matter?
Pick the exact asset and network your customers will pay with, not the longest asset list. Blockonomics's docs give BTC and BCH public-wallet-data examples and a USDT destination on Ethereum, and leave open which other assets are enabled, whether TRON or USDC work and how each platform handles tokens. BTCPay's Altcoin FAQ separates its Bitcoin focus from community-maintained opt-ins and outside exchange services.[9]
Start from what the customer is doing: paying for a physical order, getting a download or renewing access. Then have your maintainer check that the wallet, network, software package and payment-state changes work for that task, including what the customer sees when they leave checkout.
BTCPay's WooCommerce guide describes the V2 bridge, the server, store and wallet you need in place first, and the unmaintained legacy connection.[14] Its Shopify setup uses a custom manual payment method followed by a payment button on the Thank-you page, and it depends on your host enabling it and on the refund version and email conditions.[13] The order can exist in Shopify before the payment has arrived.
Blockonomics's WooCommerce guide makes order updates depend on callbacks reaching the shop.[24] Its WHMCS guide describes how BTC and USDT payments are handled, including short-payment decisions, and its PrestaShop BTC guide describes manual returns for exceptions. None of that adds up to native generic invoicing, recurring debit or a complete refund service.
- 01
Specify the payment
Name the exact asset, network, customer wallet and receiving setup, and make sure the account and host are enabled for that flow.
- 02
Check what the store does
Agree what a confirmed order, shortfall, expiry, repeated update and return should do in your shop.
- 03
Assign maintenance
Name who looks after the package, the store connection, updates, problems and records after handover.
- 04
Roll it out gradually
Verify it in a way the provider permits, and keep another payment option running while you check how your store behaves.
When is a payment ready for delivery?
Deliver once a payment has the confirmations your payment policy requires and matches the right order and amount. Detection, confirmation and fulfilment are three different events. Blockonomics's receiving guide separates unconfirmed detection from the server-side confirmed notification, and the price-lock window from how long a Bitcoin address stays valid.[20] An address can stay usable after its price quote has lapsed.
Its callback guide requires you to verify each notification, which carries the received amount, address, transaction and confirmation state. An HTTP 200 response only acknowledges that the message arrived, not that the money did.[21] BTCPay's order policy likewise treats Processing and Settled as different. Set your own payment policy with whoever runs checkout, because we don't prescribe a confirmation threshold or underpayment tolerance.
| Stage | What it tells you | Responsible next step |
|---|---|---|
| Order and quote created | A request with an amount, a payment method and time limits | The shop shows accurate payment instructions |
| Payment detected or pending | A payment that's been attempted or isn't confirmed yet | Whoever maintains the shop checks the order, amount and address |
| Confirmed and matched | The payment meets your payment policy | The shop approves delivery and stops duplicate fulfilment |
| Delivered and reconciled | Goods or access were supplied against the payment | Staff keep the order and transaction trail |
| Return claimed, approved, signed and sent | Progress through an outgoing-payment process of its own | Whoever controls the wallet sees the return through to completion |
If a customer pays short, overpays, pays late or uses the wrong network, pause automatic delivery while someone works out what arrived and what the shop can offer, and tell the buyer what happens next. Someone needs to be able to approve an adjustment or a return. An email, a redirect or a manually marked Paid label doesn't replace those checks.
Blockonomics publishes button-checkout order records with ordered and paid amounts, which help with reconciliation. Its simulation facility can help a maintainer check notifications, though we ran no simulation or live payment for this article, and simulated delays aren't promises about live receipts.[22]
Who handles full and partial returns?
Your shop makes the return decision and has to follow the outgoing payment through. BTCPay's refund documentation treats the buyer's destination claim, approval, signing, broadcast and confirmation as different steps.[7] Creating a claim link doesn't repay the buyer.
Before you promise a return, settle where it goes, who signs it, where the funds come from, how the amount is worked out and who pays the fees. The person answering your customer should be able to see whether it's only approved, sent or complete. A service fee kept on a refunded sale and the network cost of a new transfer are different items. The BTCPay payout guide likewise treats approval and sending as different from completed outgoing records, and it isn't a bank-withdrawal desk.
Blockonomics's PrestaShop manual-return example isn't a native full or partial refund product for every merchant, so ask about the workflow and the charges. Payment software also doesn't decide what the customer is owed or what consumer rights apply.
A renewal business faces the same gap between a request and paid-for access. BTCPay describes reminders or automatic renewals that use prepaid customer credits, with your application deciding who gets access.[8] Scheduled payouts, service-fee credit and renewal reminders don't let you debit an outside wallet or give you a mandate to take to another gateway.
What other software and hosting choices deserve a look?
Other software or rented servers can change the work without adding a ranked payment service. Bitcart describes a watch-only Bitcoin receipt model and warns that if hosting is interrupted, your payment records depend on the data you've kept.[27]
Its paid ETH and token extension is a different setup, with local pool keys, a fee-wallet signer, forwarding conditions and licence billing to check on their own.[28] Local pooling doesn't by itself mean a remote provider holds funds, and the core's watch-only description doesn't cover every extension or hosted deployment. Name who operates it and who can sign.
LunaNode's guide describes an unmanaged virtual server: you get the infrastructure, and running the software stays your job.[29] Renting a server isn't an application-support agreement, and nothing in the launcher says who repairs your order connection after an update or covers for an absent maintainer.
BTC Pay Latin America's Terms, updated 4 September 2026, describe temporary custody and daily forwarding for its standard service, alongside a claim of direct receipt for people who use their own node.[30] That doesn't describe the whole brand uniformly, and we haven't fully checked the company behind it, its permissions or whether you'd qualify.
Can either setup cover bills that need bank money?
Neither has a complete built-in way to reach your bank in this shortlist. An invoice in your own currency asks the customer for a crypto amount, and wallet receipt, outside conversion, partner-account credit and bank arrival are all different milestones.
BTCPay's Bringin guide shows what a partner stage looks like. It describes an account, forwarding and a euro partner balance, while its wording about on-chain use and what's coming soon is inconsistent.[31] We haven't confirmed the current contract, product approval, holds, limits, charges or bank arrival. Bringin products are partner options, not native BTCPay settlement, and they aren't extra shortlist members.
If your suppliers need bank transfers, look at the whole path to your bank before you budget from crypto receipts. The BitPay review and CoinGate review are worth reading if a managed gateway belongs in your comparison. Reading them doesn't mean you'd be approved, or that either provider belongs on the direct-receipt list.
Does no-document access mean your business is approved?
No. Permission to use software, access to a service and eligibility for your business are three different questions. On 15 October 2026, BTCPay's MIT licence allowed using and modifying the software, subject to its notice conditions and warranty limits, and it wasn't a financial authorisation.[32]
The Blockonomics Terms we read the same day name OneByZero Tech Pte Ltd., and we haven't independently verified its registration or service-specific permission. Its restrictions include gambling, adult services and crowdfunding, with prior approval for charities. Country, control, nationality, residence and customer-use conditions go beyond a short country list. Those are what the contract says, not a live summary of the law anywhere.[17]
Direct receipt doesn't give you insurance, anonymity, no-reserve terms or immunity from interruption, and whether your own company, owners, activity and customers qualify is a question for an adviser. Where we found no licence evidence, the answer is unknown, not that a permission is absent. This is general information, not legal advice.
Who keeps checkout working, and how do you leave?
Choose only when someone owns maintenance, incidents and any customer work still open when you leave. BTCPay's community support page says it doesn't guarantee or vouch for the help others offer.[12] Blockonomics's API gives a developer integration tools, but it doesn't take over your store, wallet or customer support.[19]
Guides and updates are documentation, not proof that the software works with your shop, a security test or a promised response time. Agree who can pause your checkout, investigate missed notifications, restore the records you need and cover your maintainer's absence, because no automatic export or recovery is promised.
- BTCPay: an external Bitcoin signer can keep control of spending with you.
- BTCPay: software you run can handle the orders, claims and prepaid renewals it describes.
- Blockonomics: ordinary payments go to your wallet, and its service bill is kept apart from your sales.
- Both: the published documents let you check a specific payment flow.
- BTCPay: someone has to run the software, keep it going and support it.
- BTCPay: a host-held hot wallet or shared Lightning changes who controls the money.
- Blockonomics: you depend on the account, notifications and billing staying up.
- Both: total costs, compatibility with your store and money reaching your bank are all still open until you check them.
Plan the handover before you switch: give open orders, late payments, returns, customer credits, service bills and record keeping to named people, including work that has to continue after you stop using the old checkout. Payment addresses and authorisations don't transfer automatically. The BTCPay alternatives guide helps you work out which purchase would fix the operating problem, and our OxaPay versus Plisio comparison explains why onward wallet routing needs a close look.
Show the evidence log (4 checks)+
| Checked | What we checked | Finding | Source |
|---|---|---|---|
| 2026-07-18 | Blockonomics overview and pricing revisions | The page shows this modification date. We read the wallet receipt and ongoing service billing details on 15 October. | Blockonomics pricing |
| 2026-08-21 | Blockonomics wallet guide revision | External receiving data and the optional browser wallet are different choices. Read on 15 October. | Blockonomics wallet guide |
| 2026-09-04 | BTC Pay Latin America Terms revision | Its standard service uses temporary custody, which differs from its own-node claim. Read on 15 October, and we don't recommend it as a general host. | BTC Pay Latin America Terms |
| 2026-10-15 | Current selected document readings | We read the published control, store and return workflows. None of it was tested. | BTCPay user guide |
Non-custodial crypto payment gateway FAQ
Which non-custodial crypto payment gateway is best for a small shop?
Is hosted BTCPay always non-custodial?
Does Blockonomics deduct its fee from customer payments?
Can a non-custodial gateway freeze my money?
Can I accept USDT on any network?
Is Lightning included with both candidates?
Can either automatically collect subscription payments?
Does non-custodial mean no verification or business restrictions?
Who handles a customer refund?
Will direct wallet receipt pay my bank-funded expenses?
Updated 15 October 2026: first version of this guide.
Sources
32
Numbers in square brackets in the text link to these sources.
- BTCPay General FAQ: software and direct receipt · Checked 2026-10-15
- BTCPay third-party hosting and future payment instructions · Checked 2026-10-15
- BTCPay Lightning: own versus shared wallets and capacity · Checked 2026-10-15
- BTCPay wallet: external signing and server hot keys · Checked 2026-10-15
- BTCPay user guide: operator duties and payment policy · Checked 2026-10-15
- BTCPay deployment: hosting and continuous operation · Checked 2026-10-15
- BTCPay refund claims and completed returns · Checked 2026-10-15
- BTCPay subscriptions: reminders and prepaid entitlements · Checked 2026-10-15
- BTCPay altcoins: community maintenance and exchange services · Checked 2026-10-15
- BTCPay Stores FAQ: surcharge and payment settings · Checked 2026-10-15
- BTCPay payouts: approval, fee choice and completion · Checked 2026-10-15
- BTCPay community support and help from others · Checked 2026-10-15
- BTCPay Shopify V2: payment and refund prerequisites · Checked 2026-10-15
- BTCPay WooCommerce V2: bridge, prerequisites and order states · Checked 2026-10-15
- Blockonomics overview, modified 18 July 2026 · Checked 2026-10-15
- Blockonomics pricing and billing, modified 18 July 2026 · Checked 2026-10-15
- Blockonomics selected Terms and credit conditions; effective date unknown · Checked 2026-10-15
- Blockonomics wallet and platform guide, modified 21 August 2026 · Checked 2026-10-15
- Blockonomics API overview: integration responsibilities · Checked 2026-10-15
- Blockonomics receipt: quote window, detection and confirmation · Checked 2026-10-15
- Blockonomics notifications: verification, amount and payment state · Checked 2026-10-15
- Blockonomics simulated facility; no payment test performed · Checked 2026-10-15
- Blockonomics button checkout: order and paid-amount records · Checked 2026-10-15
- Blockonomics WooCommerce BTC guide, modified 28 April 2025 · Checked 2026-10-15
- Blockonomics WHMCS guide, modified 29 April 2025 · Checked 2026-10-15
- Blockonomics PrestaShop BTC guide, modified 25 June 2026 · Checked 2026-10-15
- Bitcart core: watch-only Bitcoin receipt and records · Checked 2026-10-15
- Bitcart paid token extension: local keys and forwarding conditions · Checked 2026-10-15
- LunaNode BTCPay guide: unmanaged infrastructure · Checked 2026-10-15
- BTC Pay Latin America Terms, updated 4 September 2026 · Checked 2026-10-15
- BTCPay Bringin integration: partner service and unclear on-chain wording · Checked 2026-10-15
- BTCPay MIT software permission and warranty limits · Checked 2026-10-15
