Are there non-custodial BitPay alternatives? 5 options compared for 2026

How BitPay works: custodial, even when it settles in crypto

BitPay is one of the oldest names in crypto payments. It says it was founded in 2011, and it describes itself as "a licensed crypto payments company in multiple jurisdictions," with KYC, AML and transaction monitoring. Merchants use it for online checkout, email billing, an in-store POS and payouts. It's a mature product.

It's also custodial, and its own developer documentation shows exactly where. A BitPay invoice gives the buyer a 15-minute window to pay. Orders "are only credited to the BitPay Account for settlement after the invoice reaches the status complete." Then: "Settlement payments for BitPay merchants happen automatically, every business day. BitPay collects and deposits all payments processed from the previous business day directly to your bank or cryptocurrency wallet."

That last sentence is where many merchants get confused. Choosing crypto settlement doesn't make BitPay non-custodial. For each coin, BitPay's settlement page says it "will forward" your payments "to your address on file on a daily basis," and each coin has a minimum: 200 USDC, 200 USDT, 0.01 BTC, 0.2 ETH. Between the sale and the forward, the money sits in BitPay's ledger. Stablecoins also arrive in one place: crypto settlements come "either as the native asset of their blockchain (like BTC) or a token on the Ethereum network (like USDC)."

Here are the settlement options from BitPay's Banking & Settlements page (last updated 22 September 2025):

None of this is a criticism. Custody is how BitPay can do things a non-custodial processor can't: pay dollars or euros into your bank, refund underpayments automatically and run identity checks on buyers. The question is whether you need those things, or would rather have the money in your own wallet the moment the customer pays.

That second model is what we built. Payzum is a non-custodial, stablecoin-first crypto payment processor: payments settle directly to wallets the merchant controls. It's one of five non-custodial options below, and we'll say plainly where another one fits better.

What BitPay's custodial model costs a growing merchant

Merchants rarely leave BitPay because something broke. They leave when one of these starts to hurt.

Fees that bite small tickets. BitPay's pricing page, published on 13 October 2026, lists 2% + 25¢ per transaction below $500,000 a month, 1.5% + 25¢ from $500,000 to $999,999, and 1% + 25¢ above that, with "higher fees applicable for high-risk industries." The fixed 25¢ is what hurts small tickets. On an $8 coffee, 2% + 25¢ is 41¢, or 5.1%. On a $60 order, it's $1.45. A store doing 2,000 orders of $60 a month ($120,000) pays BitPay $2,900. Payzum charges 0.5% per sale, which is $600 on the same month, plus on-chain network fees. To be fair, BitPay's price includes conversion and fiat settlement, which Payzum doesn't do. If you don't need those, you're paying for them anyway.

Money that waits. A sale is credited after the invoice reaches complete, goes out with the next business day's batch, and by ACH appears "after two business days." A Monday sale typically reaches a US bank on Thursday. Every settlement has a minimum, and a US dollar wire to a bank outside the US needs $10,000.

Volume caps while you grow. BitPay's compliance guide says new merchants apply for Tier 2: "$10,000 USD Daily / $500,000 USD Yearly." Tier 3 ($100,000 a day, $5 million a year) and Tier 4 (unlimited) require more vetting. A wholesaler with two $6,000 invoices on the same day hits the daily cap.

Extra steps for your buyers. BitPay requires BitPay ID, a one-time compliance check, for "customers making a purchase in excess of $3,000 USD," for recipients of payouts or refunds, and for VPN users. For a B2B supplier, that means many new customers have to verify their identity with BitPay before they can pay the invoice.

Refunds and mistakes run through BitPay. To refund a customer, "your BitPay ledger must hold funds in excess of the refund amount," and the customer receives an email from BitPay asking for a wallet address. Partial payments aren't credited to you at all: BitPay refunds them to the buyer automatically. A customer whose wallet sends $1 short starts over.

One company between you and your money. If a provider that holds your balance freezes the account, changes its terms or shuts down, the balance is stuck until that's resolved. We looked at how that plays out in what happens when a crypto payment provider shuts down.

Why it works this way, and what "non-custodial" actually means

There's a simple test for any processor. Ask where the customer's transaction goes. If it goes to an address the provider controls, the provider holds your money, even if only for a day. If it goes to an address that belongs to your wallet, nobody does.

Comparison sites sometimes describe BitPay's crypto settlement as non-custodial. BitPay's own documentation describes a daily forward from its ledger, which is custody. Don't confuse its merchant service with the BitPay Wallet app either: the wallet is self-custodial ("you control your crypto, keys, and data"), but it's a separate consumer product.

In practice, you'll find five models:

• Custodial balance. The provider receives the payment, credits your account and pays you out in fiat or crypto. BitPay, Coinbase Business, CoinGate and Stripe's stablecoin payments work this way.
• Forwarding. The payment goes to the provider's deposit address and is then sent on to you. It looks non-custodial, but the provider touches every payment. NOWPayments' forwarding mode works this way, and since 28 May 2026 its new accounts start with custody switched on (see our NOWPayments alternatives guide).
• Non-custodial, hosted. The provider runs the invoices, checkout, network monitoring and webhooks. The payment settles to your wallet. Payzum and Blockonomics work this way.
• Self-hosted. You run the processor software and receive straight to your wallet. That's BTCPay Server.
• Protocol or do-it-yourself. You build on an open standard such as Solana Pay, or just share a wallet address.

Your customers already work the third way. Chainalysis' 2026 Global Crypto Adoption Index, published on 23 September 2026, found that domestic wallet-to-wallet transfers rose 302.9% to $228.7 billion between July 2025 and June 2026, and 96% of that value was in stablecoins. People pay each other from wallet to wallet. A non-custodial processor lets a business receive the same way. For more on the model, see what a non-custodial crypto payment processor is.

The 5 best non-custodial BitPay alternatives

We checked each option's public documentation on 16 October 2026. They're grouped by how much you want to run yourself, from nothing to everything. Where a provider publishes its fees, we list them with the date.

1. Payzum: best for stablecoins on many networks, online and at the counter

Payzum never holds, pools or controls merchant funds. The customer pays from their wallet and the payment settles in yours: the settlement is the payment. It runs on Bitcoin, Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, BNB Chain and Avalanche. Typical confirmations take about 0.4 seconds on Solana and about 2 seconds on Base or Polygon, so the money is yours before the receipt prints. If you also accept volatile coins, optional auto-convert to USDC or USDT is available on most supported networks, and the result still lands in your wallet (how auto-convert works).

Online, you get no-code payment links and buttons, a hosted checkout (redirect, modal or inline), invoices with an expiry time and overpayment detection, recurring subscriptions and donations. At a counter, the POS shows a new QR code for every sale, any phone works as a terminal, cashiers sign in with a PIN, and you get analytics per cashier and terminal. There are no chargebacks. Payouts live in the same dashboard: CSV mass payouts in BTC, LTC and DOGE, and stablecoin payouts on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche.

BitPay merchants on WooCommerce or Magento 2 will find an official plugin for both among Payzum's 29 open-source integrations, alongside PrestaShop, WHMCS, Blesta and more. There are official SDKs for Node.js, PHP, Python and Rust, and signed webhooks. Security includes 2FA, encrypted secrets and a full audit log. Pricing is 0.5% per processed sale, plus on-chain network fees.

Limits to know: Payzum is crypto-only and never pays fiat into a bank. It doesn't support TRON, and it focuses on major coins and stablecoins, not 100+ assets: XRP and Bitcoin Cash, for example, aren't on its network list. Refunds are on-chain payments you send yourself. Sign-up includes KYC, and your wallet's security is your responsibility. Best for: merchants whose customers pay mostly in USDC, USDT, BTC or ETH and who want the money in their own wallet, online and in person.

2. BTCPay Server: best if you run a server and mostly take Bitcoin

BTCPay Server is free, open-source software that you host yourself. Its FAQ calls it "a non-custodial invoicing system" that receives Bitcoin on-chain and over the Lightning Network, plus altcoins, and says: "There are no subscriptions, no transaction fees." It only needs your wallet's public key, never your private keys, and it uses a new address for every invoice.

It's also the only option here that was designed with BitPay merchants in mind. The FAQ says its original API "is compatible for the most part with BitPay's API to allow merchants to smoothly transition." Webhooks are the exception: BTCPay's newer Greenfield webhooks aren't BitPay-compatible, and BitPay-style notifications come through the notification URL you set on each invoice.

Best for: Bitcoin-first merchants with someone who can run and update a server. If you mainly need stablecoins across several chains without hosting anything, it's the heavier route.

3. Blockonomics: best for a small Bitcoin shop on WordPress

Blockonomics is a hosted service that sends payments straight to your wallet. Its pricing article (last modified 18 July 2026) says: "Blockonomics is completely non-custodial — we can never touch your revenue." The first 10 payments are free, then the fee is 1% of crypto received. It isn't taken from the payment: Blockonomics bills it monthly from a prepaid credit balance that you top up in BTC.

Its WordPress plugin page lists Bitcoin, Bitcoin Cash and USDT as an ERC-20 token on Ethereum, and shows 2,000+ active installations. It also offers integrations for other platforms, including WHMCS.

Best for: small online shops whose customers pay mostly in Bitcoin. If your buyers want USDC, or USDT on cheaper networks than Ethereum, look elsewhere.

4. Solana Pay: best for developers building on Solana

Solana Pay isn't a company you sign up with. Its documentation describes it as "a standard protocol and set of reference implementations that enable developers to incorporate decentralized payments into their apps and services." Payments go from the buyer's wallet to yours with no intermediary, and the docs quote confirmation in under a second at an average cost of $0.0005.

The catch is that it's a building block. Invoices, order matching, webhooks, refunds and reporting are yours to build, and it only covers Solana.

Best for: a development team that already lives on Solana and wants full control. If you want the same speed without building the checkout, Payzum settles on Solana too.

5. A plain wallet address: best for a handful of invoices a month

The simplest non-custodial setup is to send customers your wallet address. There's no processor fee, only the network fee the customer pays.

Everything else is manual. Nothing locks the price, nothing expires, and if you reuse one address you can't easily tell which customer paid which invoice. There are no webhooks, no overpayment check and no counter checkout. Best for: a freelancer or consultant billing a few clients a month. Past that, the reconciliation work costs more than a processor.

When staying with BitPay is the right call

BitPay does something none of the five options above do: it turns crypto payments into dollars, euros, pounds or pesos in your bank account, and handles refunds and buyer checks for you. If your finance team needs fiat every morning, or you'd rather not hold a wallet at all, staying is reasonable. BitPay also settles in Mexican pesos, which few crypto processors do.

BitPay vs non-custodial alternatives, side by side

Fees are as each provider published them on the dates above. For custodial options that settle in fiat, see the best crypto payment processors in 2026.

How does Payzum compare with BitPay?

If you're deciding between BitPay and Payzum specifically, these are the differences you'll notice day to day. BitPay facts come from its pricing page and developer documentation, checked on 16 October 2026.

The short version: if you need fiat in a bank and want someone else to handle refunds, BitPay does that job. If you want the money in your own wallet the moment it confirms, for a quarter of BitPay's entry percentage, Payzum does that job, with a counter and payouts in the same account.

How to move from BitPay to Payzum, step by step

If you use BitPay's WooCommerce or Magento plugin, the move is mostly installing Payzum's plugin and pasting your keys. If you built on BitPay's API, follow this order so no paid order gets lost.

1. Decide what happens to fiat. Payzum won't deposit dollars. If you need some fiat, plan how you'll convert stablecoins on your own schedule (see non-custodial stablecoin off-ramps), or keep BitPay for that part of the business.
2. Check what your customers paid with. Export a few months of BitPay invoices and group them by coin. If most came in USDC, USDT, BTC or ETH, nothing changes for your buyers. If a real share came in XRP, BCH or other coins Payzum doesn't list, factor that in.
3. Set up Payzum. Create the account, complete KYC and turn on 2FA. Connect wallets you control, choose coins and networks, and decide whether to auto-convert. Test on the sandbox first (staging.payzum.com).
4. Replace the invoice call. Swap BitPay's signed POST /invoices for POST /v1/payment with an x-api-key header. There's no key pair to manage. Send price_amount and price_currency, set pay_currency to "all" so the buyer picks the coin, and redirect to the returned invoice_url. Add an Idempotency-Key header, and keep your own uniqueness check on order_id, because the API doesn't enforce it server-side.
5. Rewrite the webhook verifier. Verify x-nowpayments-sig as HMAC-SHA-512 over the key-sorted JSON body with your IPN secret. Reject events whose event_at is more than 10 minutes old, and deduplicate on event_id. The official SDKs do this for you, and our guide to signed webhooks covers the details.
6. Map the statuses and write a refund policy. Payzum sends five statuses (table below). Fulfil on finished, after checking the amount, and nowhere else. Because underpayments and overpayments now land in your wallet, decide in advance how you handle each one.
7. Wind down BitPay, then cut over. Keep enough in your BitPay ledger to cover refunds on past BitPay orders, since those refunds come from it. Run one small real payment on Payzum, switch new checkouts, then replace old payment links, buttons and email bills.

Here's the core change in a typical API integration:

# Before: BitPay
POST https://bitpay.com/invoices
X-Accept-Version: 2.0.0
X-Identity: <hex public key>
X-Signature: <ECDSA signature of URL + body>
{ "token": "<merchant facade token>",
  "price": 49.00, "currency": "USD", "orderId": "1042",
  "notificationURL": "https://shop.example/bitpay/ipn",
  "redirectURL": "https://shop.example/thanks",
  "transactionSpeed": "medium" }
# -> send the buyer to data.url
# Webhook: x-signature = base64(HMAC-SHA256(body, API token))

# After: Payzum
POST https://merchant.payzum.com/v1/payment   # sandbox: https://staging.payzum.com
x-api-key: <Payzum API key>
Idempotency-Key: order-1042
{ "price_amount": 49.00, "price_currency": "usd", "pay_currency": "all",
  "order_id": "1042",
  "ipn_callback_url": "https://shop.example/payzum/ipn",
  "success_url": "https://shop.example/thanks",
  "cancel_url": "https://shop.example/cart" }
# -> send the buyer to invoice_url
# Webhook: x-nowpayments-sig = HMAC-SHA-512(key-sorted JSON, IPN secret)

And here's how BitPay's invoice states, as its documentation lists them, map to Payzum:

Non-custodial BitPay alternatives in practice: seven merchants

The right choice depends on the business. Here's how the options map to real situations, including the ones where the honest answer isn't Payzum.

• An online electronics store in Ohio on WooCommerce. It does about 2,000 orders of $60 a month, and most crypto buyers pay in USDC. At BitPay's 2% + 25¢, that's $2,900 a month. It doesn't need fiat every day, so it installs Payzum's WooCommerce plugin, connects its own wallet and pays $600 in Payzum fees plus network fees. Order status comes from the signed IPN, not the return page.
• A parts wholesaler in Rotterdam with $5,000 to $20,000 invoices. On BitPay, every buyer above $3,000 has to complete BitPay ID, and a single large invoice can exceed the $10,000 daily cap of a new account. With Payzum invoices, which expire and detect overpayment, buyers pay USDC from their own wallets straight into the wholesaler's. It converts to euros on its own schedule.
• A café in Miami. On a $6 coffee, 2% + 25¢ is 37¢, more than 6%. With the Payzum POS, each sale shows a new QR on any phone, every barista has a PIN, and the 0.5% fee is 3¢ plus network fees. The money lands in the café's wallet in seconds, with no chargebacks.
• A US software company whose CFO wants dollars every morning. It takes few crypto payments, but its books are in dollars and nobody wants to manage a wallet. It stays on BitPay. That's the job BitPay does well.
• A Bitcoin-only shop with a sysadmin and a custom BitPay integration. It never took stablecoins. BTCPay Server's mostly BitPay-compatible API means less code to rewrite, and there are no transaction fees. It rewrites its webhook handler and hosts the server itself.
• A small WordPress shop selling to Bitcoin buyers. It wants nothing to host and low volume. Blockonomics' plugin sends payments to its wallet, and the 1% fee arrives as a monthly bill.
• An affiliate network paying 400 creators a month. On BitPay, each recipient has to accept an invitation and complete BitPay ID. On Payzum, the network takes payments in its own wallet and sends mass payouts in USDC on Base or Polygon from the same dashboard.

Common objections to leaving BitPay

"BitPay is licensed. Isn't a regulated custodian safer?"

Licensing rules govern how a custodian holds your money. Non-custodial processing removes the holding: there's no balance with us to freeze, lose or wind down. Both are legitimate choices, with different risks. With BitPay, the risk sits with a regulated company. With a non-custodial processor, it sits with your wallet, so you need good key management, a backup and a test withdrawal before you rely on it.

"BitPay refunds underpayments for us automatically."

It can, because it holds the money. With Payzum, a short payment arrives as partially_paid and the funds are already yours, so you choose: ask the customer for the difference or send it back. Write the rule down once and apply it every time. Most merchants find a short policy covers it.

"We need fiat in the bank."

Then BitPay, or another custodial provider that settles in fiat, is the better fit for that part of your business. Payzum is crypto-only. Some merchants split the difference: they take stablecoins in their own wallet and convert only what they need, when they need it.

"Switching means rewriting our integration."

If you use a cart plugin, it's a plugin swap. If you built on the API, it's one invoice call and one webhook handler, and you can drop BitPay's key-pair signing. Plan a careful test pass on the sandbox, not a project.