Coinbase Commerce Alternatives in 2026 and How to Migrate

If you need a Coinbase Commerce alternative, you are probably outside the United States or Singapore. According to Coinbase's help center, Coinbase Commerce was unified with Coinbase Business, the transition had to be completed by March 31, 2026, and after that date the Commerce portal is no longer accessible. Coinbase Business is open only to businesses with a legal entity in the US or Singapore, so everyone else has to move to another provider.

Your realistic options are a hosted crypto payment gateway (NOWPayments, CoinGate, Plisio, OxaPay, CoinPayments, Cryptomus, Zypher and others), a self-hosted processor such as BTCPay Server, or Coinbase Business if your company qualifies. The right pick depends on which coins your customers actually pay with, whether you want to hold the keys yourself, and how much integration work you can afford.

This guide covers what to secure first, how to compare replacements, a fee table with sources, and a migration plan that keeps orders flowing while you switch.

What happened to Coinbase Commerce

Coinbase moved its merchant tooling into Coinbase Business, a custodial business account. Eligible merchants in the US and Singapore were invited to transition. Merchants elsewhere were told to find another provider before the March 31, 2026 deadline if they wanted to keep accepting crypto.

For developers the change was not cosmetic. The old Commerce charge flow was replaced, and third-party integrations had to be rebuilt or removed. Some services publicly retired their Coinbase Commerce endpoints, so if a plugin or library you rely on still talks to the old API, assume it no longer works.

Details beyond this, such as exact withdrawal procedures for leftover balances, come mostly from Coinbase's notices to merchants and from third-party migration guides. If you still have funds or records tied to Commerce, check Coinbase's own help pages for the current procedure rather than relying on a blog post, including this one.

Before anything else, secure funds and records

Switching gateways is the easy part. Losing access to old balances or transaction history is what hurts. Work through this list first:

1. Check for remaining balances. If your Commerce wallet was self-custodial, the recovery phrase you saved at setup is what controls those funds. Third-party guides describe importing it into a compatible wallet. Never type a recovery phrase into a site you reached from an email link.

2. Export your history. Download every transaction report you can still reach. You will need it for bookkeeping, refunds and tax filings.

3. Find every place Commerce is wired in. Checkout buttons, hosted payment links in emails, invoices in your billing system, Shopify or WooCommerce extensions, and webhook endpoints on your server.

4. Write down your real payment mix. Which coins and networks did customers actually use in the last few months? This decides which alternatives fit.

5. Note your open orders. Any order created against a Commerce charge that never completed needs a manual follow-up with the customer.

What to look for in a Coinbase Commerce alternative

Commerce users tend to share a profile: a small or mid-size online business, mostly international customers, and a simple need to take crypto and get paid. Measure each candidate against these points.

Coins and networks

Many merchants discover after switching that a large share of customers want to pay in USDT, and specifically on TRON (TRC20) or BSC (BEP20), because those transfers are cheap. Make sure your replacement supports the stablecoins and networks your audience uses, not just BTC and ETH.

Custody

• Custodial gateways receive the payment, credit your balance and let you withdraw. Less to manage, but you trust the provider with funds between payment and withdrawal.

• Self-hosted or non-custodial setups (BTCPay Server is the best-known example) send funds straight to your wallet. You keep control, but you run the server, the node or the wallet connections yourself.

Fees

Look beyond the headline percentage. Ask who pays network fees, whether there is a withdrawal or payout fee, whether conversion to a stablecoin costs extra, and whether the rate drops as volume grows.

Onboarding requirements

Requirements vary widely. Some providers ask for company documents (KYB) before you can go live, some ask only when volume crosses a threshold, and some let you open a store without documents. Pick what matches your business and your local rules. Don't treat this as a way around obligations that apply to you.

Integration

Check for a plugin for your platform, a clean REST API, signed webhooks and good docs. If you used Commerce's hosted checkout, you will want a hosted payment page that does the same job: QR code, countdown and clear status messages.

Settlement

Decide whether you want to keep the coins you receive, convert everything to one stablecoin automatically, or cash out to a bank account. Not every provider offers bank settlement, and those that do usually require full business verification.

Coinbase Commerce alternatives compared

Fees below are the merchant processing fees as of October 2026, taken from each provider's own pricing page. Network fees and payout fees are usually extra. Always open the source before deciding, because these pages change.

NOWPayments

Worth comparing first if you want a hosted model similar to Commerce. The pricing page lists a 1% service fee with loyalty discounts, with network fees on top. Check its coin list and plugin support against your platform and payment mix.

CoinGate

CoinGate is EU-regulated and verifies the businesses it works with, so it suits companies that want a regulated counterparty and are ready to provide documents. Payouts carry their own fee, listed separately from processing.

Plisio and OxaPay

Both have published rates that vary by integration type. If you plan to embed the payment flow in your own UI (white label), check that rate specifically, as it is higher than the standard one on both pricing pages.

BTCPay Server

The choice for merchants who want no intermediary at all. It is free and open source, but you are responsible for hosting, updates and backups, and for connecting the wallets and nodes it needs. Check which coins and networks your setup can handle before you commit.

Zypher

Zypher is a hosted crypto payment gateway and wallet. It covers the stablecoin networks many former Commerce users need: USDT on TRC20, ERC20, BEP20, TON and Solana; USDC on Ethereum, Base, Arbitrum, BSC and Solana; plus BTC, ETH, LTC, SOL, TRX, BNB, DOGE, XMR, DAI and Toncoin. The commission starts at 1% and falls to 0.25% as your 30-day paid volume grows, with no setup or monthly fees. Opening a store and getting API keys takes about a minute and needs no documents, and incoming payments are screened for AML risk. The full coin list is on the supported cryptocurrencies page.

How to migrate your integration

The concepts carry over almost one to one. A Commerce "charge" becomes an "invoice" or "payment" in most gateways. What changes is the API shape, the authentication and the webhook format.

1. Map the old objects to the new ones

2. Price in fiat, let the customer choose the coin

If you priced in USD on Commerce, keep doing so. Most gateways let you create an invoice priced in USD and let the customer pick the coin and network on the payment page. On Zypher, a fiat-priced invoice gives the customer 60 minutes to choose a coin, then 30 minutes to pay once it is selected.

3. Rebuild webhook handling, and verify signatures

Do not reuse your old Commerce handler as-is. Each provider signs webhooks differently. On Zypher, webhooks arrive as a POST with a JSON body of {event, data, timestamp}, and the X-Webhook-Signature header is a hex HMAC-SHA256 of the raw body using your API secret. A minimal Node check:

import crypto from "node:crypto";

function isValid(rawBody, signature, apiSecret) {
  const expected = crypto.createHmac("sha256", apiSecret).update(rawBody).digest("hex");
  return signature?.length === expected.length &&
    crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}

Compute the HMAC over the raw bytes you received, not over a re-serialized object, or valid requests will fail. The full request and webhook format is in the API docs.

4. Run both flows in parallel for a short time

Keep the old payment option visible only for open orders that already reference it, and route all new orders to the new gateway. Once the last old order is settled or cancelled, remove the old code and webhook route.

5. Test with a real, small payment

Many gateways, Zypher included, have no sandbox. Create a live invoice for a few dollars in a cheap network such as USDT on TRC20 or BEP20, pay it from your own wallet, and confirm that your webhook marks the order as paid. Then try an expired invoice and an underpaid one so you see how your store reacts.

6. Update everything customers see

Replace payment links in email templates, saved invoices, help-center articles and your terms page. Tell repeat customers which coins and networks you now accept.

Common mistakes when switching

• Only enabling BTC and ETH. If your customers paid Commerce in USDC, offer USDC, and add USDT, which many international buyers prefer.

• Ignoring networks. "USDT" is not one thing. A customer who sends USDT on BSC to a TRON address has a problem. Offer the networks explicitly and let the payment page show the right address.

• Marking orders paid on redirect. The success redirect only means the customer clicked through. Ship only after a verified webhook or an API status check.

• Forgetting partial payments. Customers sometimes send slightly less because their exchange deducted a fee. Decide in advance how you handle underpayments. Zypher, for example, treats 98% or more of the amount as paid and lets the customer top up the remainder below that.

• Leaving old webhooks open. Remove the old endpoint once migration is done so stale or forged requests can't touch your orders.

Legal and tax note

Moving gateways can change who your counterparty is and where funds are held. This is general information, not legal or tax advice. Check the rules that apply to your business in your country before you choose a provider.

Where to go from here

If you sell on WooCommerce, WHMCS, OpenCart, PrestaShop or forum software, see the ready-made crypto payment plugins. For custom stacks, the crypto payment gateway overview explains the invoice flow end to end. When you are ready, create a Zypher store and run your first test invoice.

FAQ

Is Coinbase Commerce still available in 2026?

According to Coinbase's help center, the standalone Commerce portal stopped being accessible after March 31, 2026, when Commerce was unified with Coinbase Business. Coinbase Business is available to businesses with a legal entity in the United States or Singapore. Merchants elsewhere need a different provider.

What is the closest Coinbase Commerce alternative?

For most former Commerce users, a hosted gateway with a payment page, signed webhooks and stablecoin support is the closest match. If you want to keep full custody, BTCPay Server is the self-hosted option. Compare fees and supported networks against your real payment mix before choosing.

Can I keep my Coinbase Commerce integration code?

Usually not without changes. Each gateway has its own API, authentication and webhook signature scheme, so the client calls and the webhook handler need to be rewritten. Your order logic, such as what happens when an order is paid, can usually stay.

Do I need to verify my business to switch?

It depends on the provider. Some require company documents before you go live, others don't for basic use. Zypher, for instance, needs no documents to open a store and get API keys, and screens incoming payments for AML risk.

How do I test a new crypto gateway without a sandbox?

Create a real invoice for a small amount on a low-fee network and pay it from your own wallet. Check that the webhook arrives, the signature verifies and the order updates. Repeat with an expired and an underpaid invoice to cover the edge cases.