FAQ
Can I still use the Charge API?
We recommend migrating to the Checkouts API to take advantage of improved reliability, new features like settlement details, and modernized authentication.What cryptocurrencies are supported?
The Checkouts API supports USDC on Base. Support for additional networks and tokens will be added in the future.How do I handle multiple payment options?
Create multiple checkouts for different amounts or purposes. Each checkout has a unique URL and ID.Can I update a checkout after creation?
Checkouts cannot be updated after creation. To change details, deactivate the existing checkout and create a new one.What happens to existing Charge webhooks?
Existing Commerce webhooks will continue to work for the Charge API. For the Checkouts API, set up new webhook subscriptions withcheckout.* event types. See the Webhooks documentation for setup instructions.
How do I monitor payment status?
Payment confirmation is asynchronous. After the customer pays, the checkout may still beACTIVE when they return to your site.
Use webhooks (checkout.payment.success) as the fulfillment signal. Alternatively, poll Get Checkout until status is COMPLETED, FAILED, EXPIRED, or DEACTIVATED; fulfill only when the status is COMPLETED. Do not treat a success redirect or a single ACTIVE GET as paid.
Can customers pay with different cryptocurrencies?
The Checkouts API currently supports USDC on Base. Support for additional networks will be added in the future.Support and resources
Checkouts API docs
New API documentation and guides
API reference
Complete endpoint reference
Authentication guide
CDP API key setup and JWT tokens
Developer Discord
Get help from the community