What are the best Coinbase Commerce alternatives for merchants in 2026?

What happened to Coinbase Commerce, and why merchants are still looking

Coinbase Commerce was one of the easiest ways to accept crypto online. You signed up with an email, got a self-custodial wallet with a 12-word recovery phrase, and dropped a checkout button or plugin into your site. Merchants in almost any country used it.

That ended this year. Coinbase's help center article "Transitioning from Coinbase Commerce to Coinbase Business" set the deadline: after 31 March 2026, "the Commerce portal will become permanently inaccessible and you will no longer be able to create charges or access the Commerce dashboard." Merchants were told to export their history, withdraw their funds and move to Coinbase Business, if they could.

Many couldn't. The same article says Coinbase Business "is currently only available to businesses with a legal entity in the United States or Singapore." Coinbase's fourth-quarter 2025 shareholder letter, filed with the SEC on 12 February 2026, describes the launch the same way: general availability "starting with the U.S. and Singapore." On 15 October 2026, more than six months after the shutdown, the Coinbase Business FAQ still reads: "currently available in the US and Singapore, with plans to expand to more markets."

Coinbase was candid about the reason. Commerce "was built for an earlier phase of crypto – one where buyers spent volatile assets and merchants self-custodied their funds." Coinbase Business is "stablecoin-first, custodial, compliant." And Coinbase added: "We recognize that some merchants valued the self-custodial, any-asset nature of Commerce," and that Coinbase Business "may not be the right fit for everyone."

The data supports the stablecoin half of that reasoning. Chainalysis' 2026 Global Crypto Adoption Index, published on 23 September 2026, found that between July 2025 and June 2026, total value flowing into crypto services fell 4.3%, from $9.30 trillion to $8.90 trillion, while stablecoin inflows to those services rose 5.3%. Stablecoins reached 22.5% of global on-chain balances by June 2026. Buyers did move to digital dollars. Whether the merchant also had to give up custody is a separate question.

Here is what changed, using Coinbase's own comparison from that article:

So the right replacement depends on which of the first four rows mattered to you. Payzum is a non-custodial, stablecoin-first crypto payment processor: payments settle directly to wallets the merchant controls. It's one of the eight options below, and we'll say plainly where another one fits better.

What the shutdown cost merchants who weren't ready

Most merchants did migrate. The ones still searching for Coinbase Commerce alternatives in October usually hit one of these problems.

Money left in a wallet nobody can see. Coinbase warned that after 31 March "the Commerce withdrawal tool will be permanently disabled" and that, for many merchants, "especially those with Bitcoin, funds may become practically inaccessible." The cause is technical: Commerce generated a new address for every payment, so a busy store's balance sits across hundreds or thousands of addresses. Standard wallets stop looking after a run of empty ones. The BIP-44 standard that most wallets follow sets that "gap limit" at 20.

A checkout that quietly stopped working. Plugins and billing modules that called the Commerce API stopped creating charges. Some platforms removed the gateway entirely, as Blesta did in version 6 (we covered it in our WHMCS and Blesta guide). Stores that didn't notice lost every crypto sale until a customer complained.

A rushed move to custody. Merchants who chose Commerce because they held their own keys had a few weeks to pick a replacement. Many took the first custodial gateway that worked. Their money now sits in someone else's balance, which is the opposite of why they signed up.

History split across systems. Coinbase says Commerce and Coinbase Business "are separate systems" and that transaction history doesn't transfer. If you didn't export it before the deadline, your accountant now reconstructs it from block explorers.

A temporary fix that became permanent. A payment-link workaround or a manual "send USDC to this address" email gets you through the first week. Six months later, it's still how you get paid, with no signed webhook, no expiry and no overpayment check.

Still have funds in an old Commerce wallet?

Commerce wallets were self-custodial, so the funds belong to whoever holds the recovery phrase. That's you. Coinbase "cannot recover your funds" without it, and it never had the phrase. If you have it, these steps help:

1. Find the phrase. Coinbase offered a Google Drive backup when you created the account. Check it, then your password manager and any paper copy.
2. Import it into reputable wallet software that lets you scan further than 20 empty addresses. Raise the gap limit, or scan in batches, until the balance stops growing. Bitcoin and other UTXO coins need this most.
3. Sweep everything to one new wallet you control, then stop using the old phrase.
4. Never type the phrase into a website or give it to a "recovery service." Anyone who asks for it can empty the wallet. No legitimate payment provider needs it. We don't.

Why "just move to Coinbase Business" doesn't fit every merchant

Coinbase Business is a solid product for the companies it serves: a custodial USDC account with payment links, invoices, checkouts, payouts, bank cash-out and QuickBooks or Xero sync. The mismatch is structural, not a matter of quality.

• Eligibility. A legal entity in the US or Singapore and a business bank account. A shop in Lisbon, Toronto or Bogotá can't apply.
• Custody. Funds are "auto-credited to your Coinbase Business account." Coinbase holds them on your behalf, which is what makes bank cash-out possible, but it's the model self-custody merchants left behind.
• Assets. USDC only for now. Coinbase's Checkouts API FAQ goes further: it "supports USDC on Base," with more networks "added in the future." A customer holding USDT, ETH or BTC can't pay that checkout as-is.
• A new integration anyway. Coinbase's own migration guide from the Commerce Charge API lists new authentication (JWT Bearer tokens instead of the X-CC-Api-Key header), a new base URL, new field names, new ID formats, new status values and new webhook subscriptions.

That last point changes the decision. If you have to rewrite your integration even to stay with Coinbase, you might as well choose the model that fits your business. There are four:

• Custodial balance. The customer pays an address the provider controls, and the provider credits your account, often with cash-out to a bank. Coinbase Business, BitPay, CoinGate, Stripe and Shopify Payments work this way.
• Forwarding or optional custody. The provider receives the payment and forwards it to your wallet, or keeps it in a balance, depending on your settings. That's NOWPayments.
• Non-custodial, hosted. The provider runs invoices, checkout, network monitoring and webhooks, and the payment settles to a wallet you control. Nothing to self-host and no balance to freeze. That's Payzum.
• Self-hosted. You run the software, and payments go to your wallet. No provider at all, but you own the server. That's BTCPay Server.

For a deeper look at the third model, see what a non-custodial crypto payment processor is.

The 8 best Coinbase Commerce alternatives, one by one

We checked each provider's public documentation on 15 October 2026. The list is grouped by what you valued in Commerce, not ranked. We left fees out on purpose: they depend on volume and change often, so confirm them with each provider.

If you valued self-custody:

1. Payzum: best for stablecoins in your own wallet, online and in person

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, so the three networks your Commerce customers used still work. Typical confirmations take about 0.4 seconds on Solana and about 2 seconds on Base or Polygon. 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, cashiers sign in with a PIN, any phone works as a terminal, and there are no chargebacks. CSV mass payouts (BTC, LTC, DOGE) and stablecoin payouts on EVM networks live in the same dashboard.

For a Commerce merchant, the setup is familiar: a hosted invoice page, signed webhooks and plugins. There are 29 official open-source integrations, from WooCommerce, Magento 2 and PrestaShop to WHMCS and Blesta, plus official SDKs for Node.js, PHP, Python and Rust. Security includes 2FA, encrypted secrets and a full audit log.

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 hundreds of assets. Sign-up includes KYC, so it isn't the email-only onboarding Commerce had. Your wallet's security is yours. Best for: merchants who chose Commerce for self-custody and whose customers now pay mostly in USDC or USDT.

2. BTCPay Server: best free option if you can run a server

BTCPay Server is open source under the MIT license and self-hosted. Its FAQ describes it as "a non-custodial invoicing system" that receives Bitcoin on-chain and over the Lightning Network, plus altcoins, and states: "There are no subscriptions, no transaction fees." Like Commerce, it uses a new address for each invoice, and it only needs your wallet's public key to receive payments.

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

If you valued "any asset":

3. NOWPayments: best for the widest coin list

NOWPayments lists 350+ cryptocurrencies, the closest match to Commerce's "hundreds of assets." Check the custody setting before you rely on it: since 28 May 2026, NOWPayments says its Custody feature is enabled by default for new accounts, so payments settle to a NOWPayments balance. You can switch to forwarding by adding a payout wallet, and payments then pass through a NOWPayments deposit address on the way to you.

Best for: merchants whose customers pay in many smaller coins. We compared it in detail in our NOWPayments alternatives guide.

If custody is fine and you want dollars or euros:

4. Coinbase Business: best if you're a US or Singapore company happy with custody

The official successor. Coinbase describes it as a platform with "custody, fiat offramps, payouts, accounting integrations, and payments," including payment links, invoicing and a Checkouts API with a sandbox. It's built around USDC, and the Commerce transition article says pricing stays consistent for merchants moving from Commerce.

Best for: US and Singapore companies that want a USDC balance, bank cash-out and accounting sync from a brand their finance team already knows. You'll still rebuild your integration.

5. Shopify Payments USDC: best if you sell on Shopify

If your store runs on Shopify, USDC is now a built-in payment method. Coinbase's shareholder letter describes "USDC on Base integrated into Shopify Payments." Shopify's Help Center page on USDC, dated 6 October 2026, lists USDC on Base, Ethereum, Optimism, Polygon and Arbitrum, for stores in Mexico, the United States (excluding Alaska, New York and Texas), 29 European countries, and Hong Kong. Funds arrive in your payout currency, or in some regions as a USDC balance you can claim to your own wallet. Customers can't open disputes on USDC orders, and subscriptions can't be paid in USDC.

Best for: Shopify merchants in those regions who want stablecoin checkout with no extra app.

6. BitPay: best for fiat in the bank without touching crypto

BitPay says you can "settle in fiat direct to your bank account, crypto, or a mix of both." Its business page lists 100+ coins on 6 networks, including USDC and USDT, turnkey integrations for Shopify, WooCommerce and Magento, and an in-store POS.

Best for: merchants whose customers pay in crypto but whose books need fiat.

7. CoinGate: best for EU businesses that want a MiCA-authorised provider

CoinGate states that its operator, UAB Decentralized, is authorised as a crypto-asset service provider under MiCA by the Bank of Lithuania. Merchants can "settle directly into EUR, USD, or stablecoins," and it lists e-commerce plugins.

Best for: European companies, ineligible for Coinbase Business, that want euros in a bank from a provider holding a MiCA authorisation. See what MiCA means for merchants.

8. Stripe stablecoin payments: best if you already run on Stripe

Stripe's documentation says stablecoin payments "are available to businesses in all US states, except New York." It accepts USDC on Tempo, Ethereum, Solana, Polygon and Base, plus USDP and USDG (US only), and "completed payments settle in your Stripe balance in your local currency." There are no disputes, recurring payments are supported, and each customer transaction is capped at $10,000.

Best for: US businesses already on Stripe that want stablecoin sales in the same balance as their card sales. You receive dollars, not stablecoins.

Coinbase Commerce alternatives compared side by side

"Not compared here" means we didn't verify that point in the provider's public documentation on 15 October 2026, so we left it out rather than guess. For a wider market view, see the best crypto payment processors in 2026.

How does Payzum compare with Coinbase Commerce and Coinbase Business?

If you're choosing between staying in the Coinbase family and moving, these are the differences that matter in daily operations. Coinbase facts come from its help center and developer docs, checked on 15 October 2026.

The short version: if you're a US or Singapore company and want dollars in the bank, Coinbase Business is the natural next step. If you chose Commerce because the money was yours from the moment the customer paid, Payzum keeps that model, adds a counter and payouts, and isn't tied to a US or Singapore entity.

How to move from Coinbase Commerce to Payzum, step by step

If you used a cart plugin, the move is mostly installing the Payzum plugin for your platform and pasting your keys. If you built on the Commerce API, here's the order that avoids losing a paid order.

1. Close out Commerce. Confirm every Commerce wallet is swept (see the steps above), and keep whatever history you exported. Then list every place a Commerce link or button still lives: product pages, invoice emails, saved buttons, old docs.
2. Count what your customers actually paid with. Group your last months of payments by coin and network. If most of it was USDC on Base or Polygon, nothing changes for your buyers.
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 charge call. Swap POST /charges for POST /v1/payment. Send the price as price_amount and price_currency, set pay_currency to "all" so the buyer picks the coin, and redirect to the returned invoice_url instead of hosted_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. Our guide to signed webhooks covers the details.
6. Map the statuses. Payzum sends five statuses (table below). Fulfil on finished, after checking the amount, and nowhere else. Never fulfil on the customer's return to your success page.
7. Cut over and clean up. Run one small real payment, switch new checkouts to Payzum, then replace old links and buttons so no customer pays into a flow you no longer watch.

Here's the core change in a typical integration:

# Before: Coinbase Commerce Charge API
POST https://api.commerce.coinbase.com/charges
X-CC-Api-Key: <Commerce API key>
{ "pricing_type": "fixed_price",
  "local_price": { "amount": "49.00", "currency": "USD" },
  "metadata": { "order_id": "1042" },
  "redirect_url": "https://shop.example/thanks",
  "cancel_url": "https://shop.example/cart" }
# -> send the buyer to hosted_url
# Webhook: X-CC-Webhook-Signature = HMAC-SHA256(raw body, shared secret)

# 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 the Commerce charge statuses, as Coinbase's migration guide lists them, map to Payzum:

A refund on Payzum is a new on-chain payment you send to the customer, so record it in your own system.

Coinbase Commerce alternatives in practice: seven merchants, seven answers

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

• An online store in Lisbon. It used Commerce for two years, and its customers paid mostly in USDC on Base and Polygon. Portugal isn't eligible for Coinbase Business. It installs Payzum's open-source WooCommerce plugin, connects its own wallet, and buyers pay on the same networks as before. Order status comes from the signed IPN, not the return page.
• A web host in Toronto on Blesta. The Commerce gateway disappeared in Blesta 6, and Canada isn't covered by Coinbase Business. It installs Payzum's official Blesta gateway, tests one invoice on a staging copy, and offers crypto again on renewals. See the WHMCS and Blesta setup.
• A SaaS company in Austin that wants dollars in the bank. It's a US company and custody doesn't worry its finance team. Coinbase Business, or Stripe if it already bills there, is the shorter path. Payzum doesn't pay out fiat.
• A Shopify store in Madrid. Spain is on Shopify's USDC list, so enabling USDC in Shopify Payments is the fastest fix, with payouts in euros. Payzum's Shopify app is self-hosted from source and needs Shopify's payments-partner approval, so it's the longer road here.
• A café with a webshop in Mexico City. It used a Commerce link on a tablet at the till. With Payzum, the same account runs the webshop checkout and the POS: a new QR per sale on any phone, PIN logins for each barista, and USDC in the café's wallet in seconds, with no chargebacks.
• A design agency paying freelancers abroad. It collected client invoices through Commerce and paid contractors by hand. On Payzum, invoices with an expiry date come in, and mass payouts in USDC on Base or Polygon go out from the same dashboard.
• A Bitcoin-only merchant with a sysadmin. It valued Commerce's self-custody and never took stablecoins. BTCPay Server keeps that model at no software cost. If it later wants stablecoins without running a server, Payzum also settles BTC to its own wallet.

Common objections to switching

"Self-custody nearly cost us our money at the deadline."

That's a lesson about operations, not about custody. Commerce spread funds across thousands of addresses and relied on one tool to gather them. Whatever you choose next, know exactly where each payment lands, keep the recovery phrase in more than one safe place, and run a test withdrawal before you need one. A custodial balance removes that job, but it adds another risk: the provider can change the product, the countries it serves or your account status. The Commerce shutdown is an example of the first one.

"We'd rather stay with Coinbase."

If you're a US or Singapore company and custody is fine, that's a reasonable choice. Go in knowing it's USDC only for now, the Checkouts API runs on Base, and your integration still needs rebuilding.

"We need fiat in the bank."

Then Payzum isn't the right fit. It's crypto-only. BitPay, CoinGate, Stripe, Shopify Payments or Coinbase Business can pay out fiat, depending on where your company is.

"Rewriting the webhook will take weeks."

It's one handler: verify the signature, check the age of the event, deduplicate, and map five statuses. With an official SDK, the verification is a function call. Plan for a careful test pass on the sandbox, not a project.