Sandbox

A sandbox that behaves like live.

Test keys route every call to a simulator. Same API, same code, same responses, with no real cards and no real money.

Test mode is a route

Test keys reach a simulator. Live keys reach the gateway.

Test mode is not a second system. A call made with a test key, such as sk_test_…, runs through the same engine and goes to the simulator instead of the gateway.

  • The same engine code runs in both modes. Only the route differs.
  • Webhooks go to your test endpoints, marked as test events.
  • Test mode is not billed and never touches real cards or money.
The sandbox: test cards, the sandbox clock, amount tails and test tokens

Example data

Make anything happen

Test cards and amount tails for every outcome.

Online, use a test token. At a test terminal, the last two digits of the amount choose the outcome.

Test tokens

TokenWhat happens
tok_test_approvedApproved (Visa, last four 4242)
tok_test_declined_insufficientDeclined: insufficient funds
tok_test_declined_do_not_honorDeclined: do not honor
tok_test_timeout_authorizedThe gateway goes quiet after it approved. Reconcile finds the payment.
tok_test_timeout_unauthorizedThe gateway goes quiet before it approved.
tok_test_partialPartial approval for half the amount
tok_test_retryable_errorAn error, then approved on retry
tok_test_amexApproved (American Express)
tok_test_debitApproved (Visa debit)

Amount tails

CentsWhat happens
.00 to .49Approved
.51Declined: insufficient funds
.52Declined: do not honor
.61Times out, but the gateway approved
.62Times out, and the gateway did not approve
.63Times out after approval, and the first lookup fails
.71Partial approval for half the amount
.81An error on the first try, approved on retry

Refunds and captures use tails too: .61 times out after the gateway acted, and .62 times out before it saw the call.

Test clock

Fast-forward instead of waiting.

Move the test clock forward to see what happens tomorrow, next week or at the end of a dispute.

  • Settle the day and see the batch, the fees and the deposit.
  • Raise a dispute and decide it.
  • Release a held refund before its undo window ends.
  • Replay or duplicate webhooks, or send them late and out of order.
  • Expire checkout sessions.

One test payment, fast-forwarded

  • NowPayment captured
  • Settle the dayBatch and estimated fees
  • Advance the clockDeposit expected
  • Raise a disputeDispute opened, deadline set
  • Decide itWon or lost
  • Each stepSends its webhook

Example

Sandbox access

Tell us what you're building.

We'll set up a sandbox with test keys, test cards and the developer docs.

  • Test mode is not billed and never touches real cards or money.
  • Docs, OpenAPI, the SDK and llms.txt included.
  • Going live needs each merchant's own merchant account from a payments provider.

Run a single business? Your developers use your Sovara One™ account. An ISO or sub-ISO? Start with Sovara Hub™.

We use your details only to set up your sandbox and reply to you. Test mode never touches real cards or money.