On March 31, 2026, Coinbase Commerce stops serving merchants outside the US and Singapore. Eight thousand merchants lose their checkout integration. The migration data so far shows a clean split: roughly 40 percent went to direct custodial alternatives (BitPay, NOWPayments), 35 percent went non-custodial (BTCPay Server, Request Network, Aurpay), and the remaining 25 percent are either still on the old integration counting down or quietly winding down their crypto acceptance entirely.
Here is what the displaced 8,000 actually did, who took the volume, and what the post-Coinbase landscape looks like.
The migration deadline and what triggered it
Coinbase announced in Q1 2026 that Commerce would "permanently shut down its self-custodial Coinbase Commerce platform for merchants outside the United States and Singapore, with the shutdown date being March 31, 2026, and no extensions offered." The official path for US and Singapore merchants is migration to Coinbase Business, Coinbase's regulated custodial product. Coinbase Business "is available to merchants in the United States and Singapore, but is not yet available in other regions, leaving a large cohort of international merchants with a tight window to find alternatives."
Translation: 8,000 merchants in Europe, Latin America, Africa, Asia, and Oceania were told they had 90 days to migrate to something else. Coinbase did not offer to help them migrate. Coinbase did not extend the deadline. The structural lesson is the one every custodial-gateway customer eventually learns: the processor is not your partner. The processor is a vendor with a strategic plan that does not include you.
Where the volume went: four migration paths
Path 1: Stay custodial, swap brand (~40 percent of merchants).
The path of least resistance was to switch from Coinbase Commerce to BitPay or NOWPayments. Both offer comparable checkout integrations, comparable KYC requirements, and comparable percentage fees. The merchant changes one integration string and keeps moving.
The hidden cost: the structural problem (your funds custodied by a third party who can decide your category is no longer worth supporting) does not change. The merchant has bought 18 to 36 months of stability at the cost of repeating the migration cycle when BitPay or NOWPayments decides their strategic focus has shifted.
BitPay's pricing sits at 1 to 2 percent + $0.25 per transaction. NOWPayments is 0.5 to 1 percent. Both are similar to what Coinbase Commerce charged. Migration friction is low. Structural improvement is zero.
Path 2: Non-custodial managed (~25 percent of merchants).
A meaningful slice migrated to non-custodial alternatives like BTCPay Server, Aurpay, Request Network, and a few smaller players. These gateways do not hold merchant funds at any step. The merchant connects an existing wallet. Settlement happens on-chain directly.
The benefit: the structural risk that prompted the original Coinbase shutdown (the processor decides your category is no longer worth supporting) is eliminated because the rail has no balance to freeze. The cost: slightly more setup work (wallet management, gas considerations) and less mature plugin ecosystems compared to BitPay.
Path 3: Full self-host (~10 percent of merchants).
A smaller but committed group migrated to fully self-hosted infrastructure: BTCPay Server on their own VPS, PayRam, or open-source alternatives. The merchant takes full ownership of the gateway. Costs drop to VPS rental ($20/month range). Setup time is reportedly under 10 minutes for technically-comfortable operators.
Path 4: Quiet wind-down (~25 percent of merchants).
A surprising slice did not migrate. They removed crypto acceptance from their checkout and went back to cards-only. The reasons varied: crypto was less than 5 percent of total volume, the migration effort was not worth the revenue retained, or they used the shutdown as cover to exit crypto entirely.
This is the silent failure mode of the Coinbase Commerce shutdown: thousands of merchants who could have been long-term crypto payment customers are now reverted to traditional rails for the foreseeable future.
Who actually gained from the shutdown
Migration data and inferred volume share so far:
- •BitPay picked up the largest single share of displaced merchants, mostly Shopify and WooCommerce stores who valued integration maturity over structural reform.
- •NOWPayments picked up the long-tail-token merchants who specifically needed Coinbase Commerce's broad asset support.
- •BTCPay Server picked up the technically sophisticated merchants who wanted full sovereignty after watching the rug-pull.
- •Aurpay, MoonPay Commerce, Request Network, and QBitFlow divided the remaining migration volume between them.
Aurpay's positioning post-shutdown targets the Shopify-merchant slice specifically. Request Network's migration guide targets the developer-integrated checkout slice.
The structural lesson nobody is naming
The Coinbase Commerce shutdown is not an isolated event. It is the second time in three years that a US-regulated crypto payment processor decided to deprecate its international product (Stripe deprecated its first crypto product in 2018 before relaunching in 2024). The structural property of US-regulated SaaS gateways is that their commercial strategy is downstream of US regulatory pressure. When the regulatory environment shifts, the product shifts. Merchants are downstream of the merchant's processor's regulatory environment.
For US merchants this is fine. For everyone else, it is the rug pull waiting to happen.
The non-custodial migration share (35 percent combined of Path 2 + Path 3) suggests a meaningful slice of merchants finally internalized the structural lesson. The next time a SaaS processor shutters their geography, those merchants will not be affected because their rail does not depend on a processor's continued operation.
What to do if you missed the migration window
If you are reading this after March 31, 2026, and your Coinbase Commerce integration is still running, it is not running. Test your checkout. Confirm whether your customers can actually pay.
If you migrated to BitPay or NOWPayments and want to harden against future shutdowns, evaluate a non-custodial alternative for the medium term. The migration cost is roughly the same as your last migration. The next shutdown cycle is roughly 24 to 36 months out.
If you reverted to cards-only, the cost of re-adopting crypto is not the integration. It is the conversion lift you stopped getting from the customer segment that prefers crypto. Industry data suggests that segment is 8 to 15 percent of e-commerce revenue depending on vertical.
Where Plaitr fits
Plaitr is structurally in Path 2: non-custodial managed gateway with same-day settlement, flat fee instead of percentage, no per-transaction cost. The merchant connects their existing wallet, integrates a single REST endpoint, accepts payments on every L1 and L2. Funds settle direct to wallet. There is no Plaitr-side balance to freeze.
The Coinbase Commerce shutdown is the structural argument for non-custodial. The migration data is the empirical evidence. The merchants who learned the lesson are running on rails that cannot be shut down on them. The merchants who did not are setting up to relearn the lesson in 24 to 36 months.