Anton.Docs
Dashboard (opens in a new tab)
Launch

Go live

Sandbox needs no approval and production needs three, so start the one you cannot test first.

Production is a separate environment with its own base URL, credentials and data. Nothing in your sandbox carries over.

SandboxProduction
Base URLhttps://api.antonpayments.devhttps://api.antonpayments.com
client_idStarts ant_oc_test_Starts ant_oc_live_
Access token lifetime8 hours1 hour
MovesSimulated payoutsReal funds
Before you begin

Start the approval first

A live call does nothing useful until three things are true of your account:

  1. Your business is verified.
  2. Anton has underwritten the account and approved it for live operation.
  3. 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

1
Fund the balance

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.

2
Key every POST

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.

3
Receive events and verify them

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.

4
Allowlist Anton, if you firewall

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.

5
Plan the secret rotation

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.

6
Back off on 429

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.

7
Give every error a behavior

Read error.code on each 4xx and 5xx and decide whether you retry, escalate, show the user or fail the job. See Errors.

8
Treat on_hold as waiting

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).

9
Keep credentials in a secrets manager

Never in source or frontend code. See Authentication.

Switch over

  1. Create production credentials in the merchant dashboard. A sandbox client cannot mint tokens against production, and the reverse also fails.
  2. Put the production credentials in your production secrets manager and change the base URL to https://api.antonpayments.com.
  3. Create the production webhook subscription and store its secret.
  4. Redeploy.
  5. 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

403key_environment_mismatch
A sandbox credential reached production. Check the client_id and the base URL.
403merchant_not_active
Your account is not active yet. Finish approval in the dashboard.
403capability_required
Your account lacks the capability this endpoint needs. See Capabilities.
403insufficient_scope
The credential was created without the scope this endpoint needs. Create a new credential with the right scope.
422insufficient_balance
Fund the account and retry with a new key.
422cannot_be_processed
Anton could not process the payout and gives no reason. Contact support with the request_id.
429rate_limit_exceeded
Wait 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.

Next

Something wrong or missing here? Open an issue (opens GitHub in a new tab) ↗