Skip to main content
The Anton sandbox runs the same API, the same state machine, the same compliance checks, and the same webhook delivery pipeline as production. What it doesn’t do is move funds. Rail submission, settlement, and counterparty communication are handled by internal mocks with deterministic outcomes — so you can build and test without waiting for a real bank transfer, and without exposing real beneficiaries to screening hits.

​
Getting a sandbox key

1

Sign in to the dashboard

Go to app.antonpayments.com and authenticate. Sandbox access is available from day one — you do not need to complete KYB to use it.
2

Create a test key

Generate a new API key in the API Keys section. Keys prefixed ant_oc_test_ only work against https://api.antonpayments.dev.
3

Set your base URL

Use https://api.antonpayments.dev as the host for every request.

​
What’s identical to production

  • Authentication — same Authorization: DPoP <access_token> + DPoP: <proof> header pair, same 401 responses, same rotation flow. Sandbox access tokens live 8 hours rather than 1.
  • Data model — beneficiaries, payouts, instruments, batches, and webhooks all share the same schemas.
  • State machine — a payout moves through pending_screening → approved → processing → sent → completed exactly as it would in production.
  • Idempotency — Idempotency-Key behaves the same way and enforces the same 24-hour window.
  • Rate limits — sandbox applies the same per-merchant ceilings. Test your handling of 429 here before production traffic exposes gaps.
  • Webhooks — subscribed endpoints receive real HTTP deliveries with real signatures. Verify your signing code in sandbox.

​
What’s mocked

  • Rail settlement — payouts transition to sent and then completed on a compressed timeline (seconds, not hours). No real bank is contacted.
  • Timing — sandbox deliberately moves faster than production so integration tests complete in reasonable CI windows.
  • Risk outcomes — the Anton Engine runs in sandbox with a controlled signal set. You can trigger specific verdicts using test fixtures from the seeders.

​
Triggering specific scenarios

Test data

Reset your sandbox and seed sample beneficiaries and payouts in a single call.

Risk evaluation

How payouts are scored and what each terminal state means for your integration.

​
When you’re ready for production

Sandbox and production are completely isolated. Keys, data, webhooks, and merchant accounts do not carry over. Before you switch to a live key, walk through the Going Live checklist — sandbox can’t simulate everything, and a missed item tends to be a painful discovery on day one.