Production is a separate environment with its own base URL, credentials and data. Nothing in your sandbox carries over.
| Sandbox | Production | |
|---|---|---|
| Base URL | https://api.antonpayments.dev | https://api.antonpayments.com |
client_id | Starts ant_oc_test_ | Starts ant_oc_live_ |
| Access token lifetime | 8 hours | 1 hour |
| Moves | Simulated payouts | Real funds |
Start the approval first
A live call does nothing useful until three things are true of your account:
- Your business is verified.
- Anton has underwritten the account and approved it for live operation.
- The corridor you want is enabled.
An account that is not active gets 403 merchant_not_active. Sandbox needs none of this, which is why it gets left to the end. GET /v1/corridors lists the corridors Anton pays out through.
Walk the checklist
A live payout draws from your balance, and one it cannot cover is 422 insufficient_balance. POST /v1/sandbox/deposits exists only in sandbox and answers 404 in production.
Build each Idempotency-Key from your own record, such as an invoice number, so a retry after a timeout returns the payout you already made. PATCH and DELETE accept a key and do not need one. Keys last 24 hours. See Idempotency.
Create a subscription against production, verify every delivery and deduplicate on the event id. A subscription belongs to one environment, so the sandbox one does not follow you. See Track payouts with webhooks and Verify webhook signatures.
Production webhooks come from fixed IP addresses, listed in the dashboard. Allow them before your first live event, or the deliveries fail at your edge.
Write down who rotates the signing secret and where it is stored before you need to. Run webhooks in production covers the 24-hour overlap and immediate=true for a leak.
Wait at least Retry-After seconds, with jitter when many requests retry together. Your ceiling is in X-RateLimit-Limit. A response without the X-RateLimit-* headers means the limit is unknown, not unlimited. See Rate limits.
Read error.code on each 4xx and 5xx and decide whether you retry, escalate, show the user or fail the job. See Errors.
A held payout is under review, carries no reason and cannot be cancelled. Show your user a pending state. status_message is the only text, and an RFI that holds a payout is answered in the dashboard by a person with rfis.respond (Respond to an RFI).
Never in source or frontend code. See Authentication.
Switch over
- Create production credentials in the merchant dashboard. A sandbox client cannot mint tokens against production, and the reverse also fails.
- Put the production credentials in your production secrets manager and change the base URL to
https://api.antonpayments.com. - Create the production webhook subscription and store its secret.
- Redeploy.
- Send one small payout to a payee you control, and watch it through its events before you raise volume.
Cancel works only until Anton hands the payout to a rail: from created, pending_approval, and early in processing. After that a live payout can only finish, so make the first one small.
When it goes wrong
client_id and the base URL.request_id.Retry-After seconds, with jitter.If something looks wrong, stop creating payouts and contact help.antonpayments.com with the request_id from the error body or the Request-Id response header. Environments and the Sandbox overview cover re-testing.