The cryptocurrency payment landscape shifted dramatically when Coinbase announced the decommissioning of its self-custodial Commerce platform for merchants outside the United States and Singapore. The final shutdown date was March 31, and after that deadline the Commerce portal became permanently inaccessible. Businesses that relied on this infrastructure had to migrate funds, update integrations, or find alternative providers. For merchants still navigating the fallout or evaluating their options, understanding what happened and what comes next is essential.
If you are searching for information about the coinbase commerce shutdown transition notice merchants, this guide covers the full scope of the transition, migration paths, fund recovery procedures, and how to evaluate alternatives that fit your operational model.
What Changed and Why
Coinbase Commerce launched during an earlier phase of cryptocurrency adoption, when the dominant expectation was that buyers would spend volatile assets and merchants would self-custody their funds on-chain. The market evolved significantly since then. Modern businesses accepting crypto payments need custody solutions, compliance frameworks, fiat off-ramps, accounting integrations, and operational tooling that the original Commerce product did not provide.
Coinbase Consolidated Commerce into Coinbase Business, a custodial platform designed around stablecoin-first payments with bank integration, invoicing, yield on idle balances, and accounting software connectivity. This shift made sense from a product perspective but created immediate disruption for merchants who valued self-custody or operated outside the regions where Coinbase Business launched.
Migration Paths by Region
Eligibility for Coinbase Business depends on your business registration location. The platform initially launched only for entities registered in the United States and Singapore, with planned expansion to additional countries throughout the year.
Merchants in the United States and Singapore
These merchants could apply for a Coinbase Business account at coinbase.com/business using a registered business entity and business bank account. Existing Commerce API integrations required updates — the new platform uses JWT-based authentication through CDP API keys instead of the legacy X-CC-Api-Key header, and the base URL changed from https://api.commerce.coinbase.com to https://business.coinbase.com/api/v1.
Merchants already settling payments to Coinbase Exchange received automatic transitions without reapplication. Their accounts moved smoothly, and incoming payments began settling to the main Coinbase platform rather than the exchange interface.
Merchants Outside the United States and Singapore
Businesses in other regions faced a harder reality. Coinbase Business was unavailable in their markets, meaning they needed to identify alternative payment processors before the Commerce portal closed. These merchants were advised to stop creating new charges well ahead of the deadline, export transaction history, withdraw all remaining funds, and communicate with customers about ongoing payment flows.
Feature Comparison
| Feature | Coinbase Commerce (Legacy) | Coinbase Business |
|---|---|---|
| Payment links | UI + API | UI + API |
| Transaction fee | 1% | 1% for migrating merchants |
| Supported networks | Ethereum, Polygon, Base | Five major EVM networks |
| Custody model | Self-custodial | Custodial |
| Fiat off-ramp | Not available | Direct bank transfer |
| Accounting integrations | None | QuickBooks + Xero |
| Invoicing | Not available | Full suite |
| Multi-asset support | Hundreds of assets | USDC (USDT added later) |
Fund Recovery Before the Deadline
Commerce wallets operated on a self-custodial model, meaning merchants controlled access via their seed phrase and Coinbase never held that information. After the shutdown, the withdrawal tool was permanently disabled, making pre-deadline action critical.
Two withdrawal approaches existed. The Commerce dashboard withdrawal tool scanned all addresses associated with a merchant’s account and consolidated funds into a single transaction — the recommended method, especially for merchants receiving Bitcoin or other UTXO-based assets where funds could be spread across hundreds of individual addresses. Alternatively, merchants who retained their 12-word seed phrase could import it into compatible wallets like MetaMask or Coinbase Wallet, though this approach often failed to surface the complete balance since standard wallet scanners typically check only the first twenty unused addresses.
Merchants who lost their seed phrases faced the most difficult situation. Because Commerce was genuinely self-custodial by design, Coinbase could not recover lost credentials or access locked funds. Support was available at [email protected] for account access issues, but seed phrase recovery was outside Coinbase’s capabilities.
API Integration Changes
Developers maintaining Commerce integrations needed to rewrite several components of their payment flows. The charge resource replaced by checkout objects, status values shifted from NEW, SIGNED, PENDING, COMPLETED, EXPIRED, FAILED to ACTIVE, PROCESSING, COMPLETED, DEACTIVATED, EXPIRED, FAILED, and amount structures simplified from nested local_price.amount fields to flat amount and currency properties.
Payment URLs also changed — the hosted_url field became simply url. Webhook signatures required updating from HMAC-based Commerce verification to JWT token validation. Merchants with automated settlement rules, custom redirect flows, or embedded checkout experiences needed to test every component against the Coinbase Business sandbox before switching production traffic.
Evaluating Alternative Providers
For merchants unable to use Coinbase Business, selecting a replacement payment processor requires examining several factors beyond basic processing fees. The ideal provider should align with your custody preferences, supported asset list, regional availability, and technical integration complexity.
Custodial processors offer simplicity — the provider handles wallet management, compliance, and fiat conversion. This matches the Coinbase Business model and suits businesses prioritizing ease of operation over direct asset control. Self-custodial alternatives exist for merchants who want on-chain control while still benefiting from hosted checkout pages, webhook verification, and automated settlement routing.
Regional availability matters significantly. Some providers operate globally with minimal restrictions, while others mirror Coinbase’s geographic limitations. Processing fees vary widely, typically ranging from 0.5% to 2.5% per transaction depending on volume tiers and supported networks. Settlement speed differs too — stablecoin payments settle near-instantly on most networks, while Bitcoin transactions depend on network confirmation times.
| Consideration | Custodial Provider | Self-Custodial Provider |
|---|---|---|
| Asset control | Provider holds funds | You control private keys |
| Setup complexity | Low — KYB required | Moderate — wallet setup needed |
| Fiat conversion | Built-in off-ramp | Manual or third-party |
| Compliance burden | Provider-managed | Merchant responsibility |
| Best for | Businesses prioritizing simplicity | Merchants wanting full control |
Lessons for Future Transitions
The Commerce shutdown demonstrated why merchants should maintain backup payment infrastructure regardless of their primary processor’s reputation. Diversifying across multiple payment providers reduces concentration risk and ensures continuity when regulatory changes, product pivots, or geographic restrictions disrupt operations.
Exporting transaction data regularly, maintaining clean records of API credentials and webhooks, and documenting settlement configurations become critical habits when relying on any single payment infrastructure. The merchants who navigated the Commerce transition smoothly were those who acted early, verified their integrations thoroughly, and kept their customer communication channels open throughout the process.