Processing times depend on the payment method and corridor:

These are business day estimates. Bank holidays in the sending or receiving country may add time.

No. Once a payout reaches processing status, it has been submitted to the payment rail and cannot be cancelled. You can cancel a payout only while it is in created, pending_screening, pending_approval, or approved status by calling POST /v1/payouts/{id}/cancel.

When a payout is returned by the receiving bank, the funds are automatically credited back to your Anton balance. No action is required on your part. You will receive a payout.returned webhook event, and the payout status will update to returned with a return_reason field explaining why.

Minimum and maximum amounts are corridor-dependent. They vary by the source currency, destination currency, and destination country. Use GET /v1/corridors to retrieve the specific limits for each corridor you plan to use. Your account may also have custom limits configured by your account manager.

Anton supports a wide range of fiat currencies and stablecoins. The full list of supported currencies is available via GET /v1/currencies, or in the merchant portal under Settings. Supported currencies are updated as new corridors are added.

Use GET /v1/countries for the full list of supported destination countries, and GET /v1/corridors to see which source-destination currency pairs are available. Country availability depends on your account configuration and active rail providers.

No. Sandbox payouts (api.antonpayments.dev) are entirely simulated. No real money is moved, no real bank transfers are initiated, and no real sanctions screening occurs. Sandbox is designed for integration testing. Use sandbox API keys (prefixed ak_test_) to authenticate.

Anton provides a webhook test endpoint. After registering a webhook URL via POST /v1/webhooks, you can trigger a test event by calling:

This sends a sample event to your registered URL so you can verify your endpoint is receiving and processing events correctly. You can also create payouts in sandbox to trigger real webhook events through the full flow.

Every webhook request includes an X-Anton-Signature header containing an HMAC-SHA256 signature. Compute the HMAC-SHA256 of the raw request body using your webhook signing secret, and compare it to the header value. Reject any request where the signature does not match.

Anton retries failed webhook deliveries with exponential backoff. The retry schedule is: 1 minute, 5 minutes, 30 minutes, 2 hours, 12 hours, and 24 hours. After all retries are exhausted, the event is marked as failed. You can view failed deliveries in the merchant portal and manually replay them.

API keys are managed in the merchant portal under Settings. You can rotate keys there at any time. API keys cannot be created or rotated via the API itself. When you rotate a key, the old key is immediately invalidated — update your integration before rotating.

No. Sandbox and production are completely separate environments with separate databases. Payees, instruments, payouts, and all other resources created in sandbox do not exist in production. You must recreate your payees and instruments in production when you go live.

If your question is not answered here, contact Anton support through the merchant portal or email support. When reaching out, include the relevant resource IDs (pay_, pye_, ins_) and the environment (sandbox or production) to help us assist you faster.