guides

Test cards and sandbox

The sandbox runs simulated processors that behave like real ones. Use these numbers to drive every outcome.

Cards

Any future expiry date and any 3 or 4 digit CVC.

Number	Network	Result
`4242 4242 4242 4242`	Visa	Succeeds
`4111 1111 1111 1111`	Visa	Succeeds
`5555 5555 5555 4444`	Mastercard	Succeeds
`3782 822463 10005`	American Express	Succeeds
`6011 1111 1111 1117`	Discover	Succeeds
`3800 0000 0000 06`	Diners Club	Succeeds
`4000 0000 0000 0002`	Visa	Declined (`DC_08`, card declined)
`5105 1051 0510 5100`	Mastercard	Declined
`4000 0000 0000 9995`	Visa	Processor error (retry scenario)
`4000 0000 0000 9987`	Visa	Declined, lost card
`4000 0000 0000 9979`	Visa	Declined, stolen card
`4000 0038 0000 0446`	Visa	3-D Secure challenge page, then succeeds

Any other number is rejected as unsupported.

Sandbox processors

Processor	What it simulates
Stripe Test	Card authorisation, capture, refunds, 3DS challenge page
PayPal Test	Redirect wallet with an approval page
Adyen Test, Checkout Test	Same card behaviour, useful to test routing between processors

Payments settle instantly. Refunds succeed immediately. Disputes can be raised from the dashboard on succeeded payments.

Wallets in sandbox

Apple Pay and Google Pay need a real processor sandbox (for example a Stripe or Adyen test account) because the wallet token is decrypted by the processor. See Wallets. The buttons appear automatically once such a processor is attached to your profile.

Sandbox limits

Sandbox data can be reset; do not rely on it for records.
Rate limit: 60 requests per second per key.
Keys are prefixed snd_ (secret) and pk_snd_ (publishable). Live keys will be issued separately at go-live.

Questions: dev@apay.to · Back to docs