The Commerce Charge API stops working
Coinbase Commerce API
Stopped working
On March 31, 2026, the Commerce Charge API will stop working, and requests sent to api.commerce.coinbase.com will fail. Developers are instructed to migrate to the Checkouts API for modern authentication and additional capabilities. After this date, existing charge integrations will no longer be supported.
What to use instead of these calls
Switch to the Coinbase Business Checkouts API using a CDP API key with Bearer JWT authentication instead of X-CC-Api-Key charges. This change requires more than updating an identifier, as the Checkouts API requires a Coinbase Business account, which is open only to US and Singapore businesses.
The Checkouts API requires a Coinbase Business account, open only to US and Singapore businesses, and a new CDP API key.
In Coinbase Commerce API's words
Migrate from Commerce Charge API to the Checkouts API for improved reliability, simplified integration, modern authentication, and additional capabilities including settlement details.
Facts
- API
- Coinbase Commerce API
api.commerce.coinbase.com - Kind
- Version retirement
- Takes effect
- March 31, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Coinbase Commerce API's own pages
Questions
When does this change take effect?
Calls to these calls on Coinbase Commerce API stopped working on March 31, 2026.
What happens to calls after March 31, 2026?
They have failed since March 31, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.