Skip to main content
Anton has two environments — sandbox and production. They run the same API with the same endpoints, validation, and behavior. The difference is whether real money moves and real compliance checks execute. Each environment is completely isolated. API keys, payees, payouts, balances, and webhook subscriptions created in one environment do not exist in the other.
SandboxProduction
Base URLhttps://api.antonpayments.devhttps://api.antonpayments.com
API key prefixak_test_ak_live_
Compliance screeningSimulated (auto-pass)Real OFAC, PEP, and sanctions checks
FundsPre-loaded test balancesReal money — must fund account
Payout deliveryInstant simulationReal rail processing (minutes to days)
WebhooksDelivered normallyDelivered normally
Rate limitsRelaxedEnforced per plan

​
Sandbox

The sandbox is your development and testing environment. It behaves identically to production — same endpoints, same request/response formats, same validation rules — so code that works in sandbox will work in production without changes. 
https://api.antonpayments.dev

​
What you can do in sandbox

  • Create payees and attach payment instruments
  • Submit payouts and observe the full lifecycle
  • Upload and process batch payouts
  • Register webhook endpoints and receive deliveries
  • Query balances and transaction history
  • Test error handling with invalid inputs

​
How sandbox differs from production

Compliance screening is simulated

All payouts pass compliance screening automatically. No real OFAC, PEP, or sanctions checks are performed. In production, payouts can be held for manual review or rejected by the screening engine.
Sandbox payouts move through every lifecycle status — screening, processing, sent, completed — but transitions happen in seconds rather than minutes or days. Use this to verify your status handling logic without waiting.
Your sandbox account comes with test balances in supported currencies. These reset periodically. In production, you must fund your account before submitting payouts.
Nothing submitted in sandbox results in a real payment. You cannot accidentally send real funds from the sandbox environment.

​
Sandbox access

Sandbox access is provisioned after your merchant application is approved or by your account manager. It is not self-service. See Going Live for the full onboarding process.

​
Production

Production processes real payouts through real payment rails. Compliance checks run against live sanctions lists. Funds are delivered to real bank accounts, mobile wallets, and crypto addresses. 
https://api.antonpayments.com
Production payouts are irreversible once they reach sent status. Verify payee details and amounts before submitting. Use idempotency keys on every request to prevent duplicates.

​
Requirements

You must complete all of the following before submitting production payouts:
  1. Approved merchant application — KYB verification, document review, and compliance approval
  2. Certification call — technical walkthrough of your integration with our team
  3. Funded account — wire funds to your production account and confirm balances via the API
  4. Production API keys — generate ak_live_ keys from the merchant portal
For the full checklist, see Going Live.

​
Identifying your environment

You can always determine which environment you are using by checking your API key prefix: 
ak_test_...  ->  Sandbox   (api.antonpayments.dev)
ak_live_...  ->  Production (api.antonpayments.com)
Using a sandbox key against the production URL (or vice versa) will return a 401 Unauthorized error. Keys are scoped to their environment and cannot cross over.
Keep environments separate. Use environment variables to manage your base URL and API keys. Never hardcode either — and never use production keys in development or CI.