Coinbase Commerce Alternative: Best Options for Global Merchants

On March 31, 2026, Coinbase permanently shut its self-custodial Commerce product for every merchant outside the United States and Singapore. There were no extensions. If you ran a store in Europe, Latin America, Southeast Asia, Africa, or the Middle East and accepted crypto through Coinbase Commerce, your checkout stopped working and you needed a new gateway. The fastest coinbase commerce alternative search traffic in years came from merchants who did nothing wrong and were cut off anyway.

That second sentence is the whole story. A working integration was switched off by a business decision the merchant had no vote in. So the real question is not which provider looks most like Coinbase Commerce. The real question is which kind of provider can never do this to you again, and how you move without losing in-flight payments. This guide answers both, compares the live alternatives on the dimensions that actually decide the outcome, and gives you a migration checklist you can run today.

Why did Coinbase Commerce shut down for international merchants?

Coinbase is folding its merchant tooling into Coinbase Business, a custodial product currently offered only in the United States and Singapore. Merchants in those two markets were pointed toward Business. Everyone else was pointed toward the exit.

To understand why this could happen at all, start from the most basic fact about how Coinbase Commerce worked. It was a service operated by one company, and that company decided which countries it would serve. When a single operator owns the on/off switch, the switch can be flipped for reasons that have nothing to do with your business. Your sales could be healthy, your account in good standing, your customers happy, and you would still lose the integration if the operator exits your region. That is exactly what happened here.

This is not a criticism unique to Coinbase. It is a property of any model where one company sits between you and your customer's payment. The lesson for merchants is structural rather than emotional. If being cut off is even possible, then sooner or later it becomes a risk you have to price in, and that risk should shape which alternative you pick next.

What actually matters when choosing a Coinbase Commerce alternative?

Most "best alternative" lists rank providers by logo recognition or checkout design. Those are the wrong first filters. The dimension that determines whether you can be offboarded again is custody, so that is where any honest comparison has to begin.

Custody is the dividing line

A custodial gateway takes your customer's payment into wallets it controls, then pays you out later from its own balance. Because it holds the funds and the keys, it can freeze your account, delay settlement, or stop serving your country. A non-custodial gateway never holds your keys. Payments settle to addresses you control, and the provider only coordinates and reports. The practical difference is simple. With non-custodial infrastructure, there is no account for anyone to close out from under you, because the value was always yours.

If you want the full mechanics of why this matters, we cover them in depth in our guide to what a non-custodial crypto payment gateway is. The short version is that custody is the single feature that decides whether the Coinbase Commerce situation can repeat for you.

Geography, settlement asset, and fee model

After custody, three more dimensions decide fit. Geographic availability tells you whether the provider can legally serve your customers, which is the exact constraint that stranded Coinbase merchants just ran into. The settlement asset tells you what you actually hold after a sale, because settling in a volatile coin is very different from settling in a dollar-pegged stablecoin. The fee model tells you what the relationship costs over a year of real volume, and it has two sides that providers often blur together, the pay-in fee on money coming in and the payout fee on money going out.

How do the main alternatives compare?

The table below compares live options on the four dimensions that decide the outcome. Where a competitor's exact figure is not something we can verify firsthand, it is marked as varies so you confirm it with the provider rather than trusting a number we cannot stand behind. The accuracy of your own decision depends on doing that check.

Provider	Custody model	Geographic availability	Settlement asset	Fee model
Coinbase Commerce	Was self-custodial, now shut down outside US and Singapore	Discontinued for non-US, non-Singapore merchants	Crypto, varied by integration	No longer available
Coinbase Business	Custodial	US and Singapore only	Varies, verify with provider	Varies, verify with provider
MoonPay	Varies, verify with provider	Depends on licensing per country	Varies, verify with provider	Varies, verify with provider
Request Network	Non-custodial payment protocol	Broad, verify per region	Crypto and stablecoins	Varies, verify with provider
AIO.cash	Non-custodial, merchant holds keys	Global, multi-chain via one API	Stablecoins (USDT, USDC) and supported crypto	0.3% pay-in, 0% payout

Read the table top to bottom and a pattern appears. The providers that cannot offboard you the way Coinbase just did are the non-custodial ones, because they never hold the funds in the first place. Among those, the deciding factors become geographic reach, the settlement asset you keep, and what the fee model does to your margin over a year.

Why does AIO fit merchants leaving Coinbase Commerce?

AIO is a non-custodial crypto payment gateway, which means it answers the exact failure that stranded these merchants. Because AIO stores no private keys and payments settle to addresses you control, there is no account anyone can switch off and no funds anyone can hold hostage. That is the structural fix, not a promise.

From there, the practical features map cleanly onto how Coinbase Commerce merchants actually sold. AIO supports two pay-in types that cover the common cases. A one-time pay-in generates an invoice-style address for a single order, which is what most checkouts need. A long-time pay-in gives you a reusable address that stays valid for repeat customers and subscriptions, so you are not minting a fresh address for every recurring charge.

Reconciliation is where many gateways get vague, and AIO is deliberately concrete here. Every payment is a parent transaction that fans out into sub-transactions, where each sub-transaction is one on-chain movement with its own hash and addresses. When a customer pays in two installments, or a batch payout goes to several recipients, you see each leg rather than a single blurred total. For a finance team rebuilding its books after a forced migration, that detail is the difference between a clean ledger and a guessing game. Our merchant guide to accepting crypto payments walks through how this maps to day-to-day operations.

On the money math, AIO charges 0.3% on pay-ins and 0% on payouts, and AIO covers the network gas through a pre-funded address pool so you never touch it. The 0% payout matters more than it first looks. Many gateways quote a low headline rate and then take a second cut when you move funds out, so your real cost is two fees stacked. Removing the payout fee removes that second bite entirely, which is why merchants doing high payout volume feel it most.

Operationally, payouts above a threshold you configure route to a review-and-approve step instead of paying automatically, which gives a finance lead a control point and an audit trail on large movements while small routine payouts still clear without friction. And every webhook AIO sends is HMAC-SHA256 signed, so your server can verify that a payment notification genuinely came from AIO and was not forged or replayed. If you want the architecture in full, see what AIO crypto payment infrastructure is.

How do you migrate off Coinbase Commerce without losing payments?

Migration goes wrong in predictable places, so run it as an ordered checklist rather than a scramble. The three things that actually break are webhooks pointed at the old endpoint, payments that land during the cutover window, and a settlement asset chosen by accident instead of on purpose. Work through these steps in order.

1. Pick your settlement asset before anything else, because every later step depends on it. If you want price stability, settle in a dollar-pegged stablecoin like USDC or USDT rather than a volatile coin, so a sale today is still worth the same when you spend it.
2. Create your new gateway account and generate test pay-in addresses, then run a small real transaction end to end so you confirm money arrives at an address you control before you cut traffic over.
3. Re-point your webhooks to the new endpoint and verify the signature check works, because a payment notification your server cannot validate is a payment your system will not record correctly.
4. Reconcile every in-flight Coinbase Commerce payment first, meaning any order a customer started but had not completed, so nothing falls into the gap between the old system going dark and the new one going live.
5. Switch your checkout to the new gateway during a low-traffic window, watch the first live payments land and reconcile cleanly, then keep the old records exportable for your books and tax filing.

The single most common mistake is treating the webhook swap as a one-line config change. It is not. A webhook your server cannot verify is worse than no webhook, because it can let a forged notification mark an unpaid order as paid. Verifying the signature is the step that protects you, which is why AIO signs every callback by default.

Frequently asked questions

Where this leaves global merchants

The Coinbase Commerce shutdown will not be the last time a custodial processor reshapes its footprint, and the merchants who get hit hardest next time will be the ones who simply moved to the next gateway that holds their keys. The way to stop the cycle is to choose infrastructure where being offboarded is not even possible, because the funds were always yours and the provider only coordinates. That is the difference between renting a checkout and owning your payment flow.

If you are migrating off Coinbase Commerce and want a non-custodial gateway with 0.3% pay-ins, 0% payouts, multi-chain settlement through a single API, and HMAC-signed webhooks you can verify, AIO.cash was built for exactly this. Book a demo or talk to our team about your migration, and we will help you re-point webhooks, handle in-flight payments, and settle in the stablecoin you choose so the switch is clean and you are never cut off again.

Frequently Asked Questions

Is Coinbase Commerce really gone for international merchants?

Yes. Coinbase permanently shut its self-custodial Commerce product for all merchants outside the United States and Singapore on March 31, 2026, with no extensions. Merchants in those two markets were directed to Coinbase Business, while everyone else had to migrate to a different gateway.

What is the safest type of Coinbase Commerce alternative?

A non-custodial gateway is the structurally safest choice because it never holds your keys or funds, so no provider can freeze your account or exit your region the way Coinbase Commerce just did. The value settles to addresses you control, which removes the single point of failure that stranded these merchants.

Will I lose payments during migration?

Not if you reconcile in-flight payments before cutover and test the new gateway end to end first. The two riskiest steps are re-pointing webhooks to the new endpoint and handling orders that customers started during the switch, so run both deliberately in a low-traffic window.

How does AIO keep my crypto payment fees low?

AIO charges 0.3% on pay-ins and 0% on payouts, and it covers the network gas through a pre-funded address pool so you never pay for it. Removing the payout fee matters because many gateways take a second cut when you move funds out, so a 0% payout removes that stacked cost.

Can I accept both one-time and subscription payments after migrating?

Yes. AIO supports one-time pay-ins with an invoice-style address for single orders and long-time pay-ins with a reusable address for repeat customers and subscriptions. That covers both standard checkout and recurring billing through a single API.