1. Request production access
Contact your Circle representative to request production API access. Production access requires a signed agreement with Circle.2. Replace sandbox URLs with production URLs
Update the base URL in your application from the sandbox endpoint to the production endpoint.3. Replace your API key
Replace your sandbox API key with your production API key. Your production API key is provided by Circle after your production access is approved. If you operate in an EU/EEA member state under MiCA, your entity also authenticates to Circle with mutual TLS (mTLS). mTLS applies to all of your entity’s API traffic as the distributor, not per end customer, and uses the regional EU API endpoint. See How mTLS authentication works.4. Account for production settlement times
In sandbox, wire deposits and blockchain transactions settle instantly. In production, be aware of the following differences:
Update your application’s user interface to set the right expectations for your
end customers about processing times.
5. Verify KYB onboarding flow
In sandbox, KYB verification is automatically approved. In production, Circle performs real KYB checks on your end customers. Ensure your integration handles the following scenarios:- Pending verification: The account is created but not yet active while Circle reviews the business entity
- Rejected verification: The business entity does not pass KYB checks and the account is not activated
6. Review transaction limits
Sandbox limits differ from production limits. Verify the applicable limits for your end customers’ risk tiers and ensure your integration handles limit errors gracefully. See Limits and risk ratings for details.7. Set up webhook notifications
If you haven’t already, configure webhook notifications for your production environment to receive real-time updates on deposits, withdrawals, and transfers. Using webhooks reduces the need for polling and ensures you respond quickly to account events.8. Review your non-custodial relay
Non-custodial accounts aren’t available in production yet. When they are, review your backend relay before you go live. Confirm that it does the following:- Authenticates the signed-in user.
- Forwards only the SDK’s routes.
- Forwards writes only for the user’s own non-custodial account.
- Checks that every unsigned request, such as a read, belongs to the signed-in
user’s
clientEntityId.
Register your Google client IDs
In production, Circle accepts a Google ID token only if itsaud value is an
approved client ID. Sign in to Circle Hub, go to
Settings > Digital Asset Accounts > Social login, and set:
- Web application: your Web application client ID from Google Cloud. Your
Android app passes it to Google Sign-In as
serverClientId. - iOS: your iOS client ID from Google Cloud. You need it only if your iOS
app doesn’t set
serverClientIDto your Web application client ID.
aud isn’t approved, completeSocialSession fails with HTTP
403.
Production checklist
Before going live, confirm that you have completed each of the following items:- Obtained a production API key from Circle
- Updated all API calls to use the production base URL
- Tested authentication with the production API key
- Handled KYB pending and rejected states in your onboarding flow
- Accounted for real-world settlement times in your user interface
- Configured webhook notifications for production
- Verified that transaction limit errors are handled gracefully
- For non-custodial accounts, reviewed your relay’s authentication, route allowlist, and ownership checks
- For non-custodial accounts, registered your Google client IDs in Circle Hub