Skip to main content
Use these test cards to simulate the outcome of a card payment or a subscription in Sandbox. These predetermined card outcomes and the simulation controls below are available to customers only in Sandbox.

How to use test cards

Enter a test card in the sandbox dashboard’s card payment form.
  • Use any future expiration date and any three-digit CVC.
  • Complete the required cardholder and billing details.
  • Use one of the card numbers below. Any other card number produces a failed attempt with no failure.code and does not charge the card.

Apple Pay

Sandbox checkout offers Apple Pay. It doesn’t offer Google Pay.
  • Pay with your own card in the Apple Pay sheet. It isn’t charged.
  • Every Apple Pay payment succeeds. Test declines with the typed test cards below.
  • If your team can’t use real cards, use Apple’s sandbox tester accounts.

Successful payments

Use these cards to test an accepted payment. Funds become available to the merchant after you simulate settlement.

3-D Secure

Sandbox runs 3-D Secure on a checkout payment with a typed card only when Natural’s risk check on that payment asks for it. A saved card is charged without 3-D Secure, unless an earlier payment on the same checkout link failed. Sandbox 3-D Secure is simulated: it always passes, and the payer sees no challenge. Use this card to test a payment that runs 3-D Secure. It asks for 3-D Secure every time it is typed at checkout, then pays like 4111 1111 1111 1111. Once saved, it is charged like any other saved card.

Declined payments

Use these cards to test issuer declines. A declined payment fails without moving money. You can retry an open payment intent with a success card. After five issuer declines, the intent closes. A non-test card does not count toward that limit. If Natural cannot verify a card’s fixture identity, the request returns an error without creating a payment attempt; retry the request.

Subscriptions

Use these cards to test a subscription’s later charges. Entering any card in this table at checkout pays payment 1 and saves the card. The saved card’s normal outcome applies to every later charge attempt, including retries, unless you set a one-time decline override. Insufficient funds is retryable. An expired-card decline stops collection and puts the subscription in needs_attention. A stopped-payment decline cancels the subscription. 4000 0000 0000 0002 declines the first payment, so no subscription starts. A one-time payment with any card in this table succeeds. A subscription’s checkout doesn’t need a verified phone. It opens with Save my information on and the phone step open, so turn that off to pay without verifying. Saving a payer’s information and paying with a saved card both need verification. Sandbox sends no text message; enter 000000.

Subscription simulations

Open Accept → Subscriptions in the Sandbox dashboard, select a subscription, and choose Simulate. You can advance its test clock or make its next charge decline. A subscription paid with Apple Pay always succeeds, so you can’t make its next charge decline. Setting a decline override doesn’t charge the card or move the clock. It applies to one actual charge attempt. If Natural refuses a request before creating a charge, the override stays pending. After that attempt, later attempts return to the saved test card’s normal outcome. A decline that stops collection or cancels the subscription still prevents further scheduled charges. Advancing the test clock charges what falls due. Those charges use the subscription’s simulated date, so Transactions can show future dates. To test a temporary decline, start a subscription with no end using 4111 1111 1111 1111 and let payment 1 succeed. Set the next charge to decline for Insufficient funds, then advance to payment 2. Payment 2 declines once. Choose what to test next:
  • Retry payment 2 to advance to its next retry. The retry succeeds because the one-time override has been spent and the saved card normally succeeds.
  • Advance to payment 3 to skip payment 2’s remaining retries. Payment 2 stays missed and owed, payment 3 succeeds, and the subscription is past_due. Advancing doesn’t retry or pay payment 2.
With 4000 0000 0000 9995, every later attempt normally declines for insufficient funds. A one-time override changes only one attempt; it doesn’t make that card’s later retries succeed.

Saved cards

To save a test card at checkout, keep Save my information on and enter 000000 as the verification code. A subscription’s checkout keeps its card for that subscription’s later charges, with or without Save my information. A saved card pays later checkouts, including a new subscription’s first payment, with the outcome of the test card it was saved from. If checkout says a card was saved before sandbox started recording test cards, choose to use a different card and enter a test card again.

Cancels

To cancel an accepted test payment, request a full refund before you simulate settlement.
  • Dashboard: Open Accept → Transactions, select the payment, and choose Refund for the full amount.
  • API: Call POST /refunds at https://api.sandbox.natural.com with the full payment amount and a sandbox key.
Cancellations complete automatically. The refund receipt shows Processed as: Void, and the payment is not added to the merchant’s available sandbox balance.

Refunds

To test a full or partial refund, first settle a successful test payment. Wait until Settlement status shows Settled.
  • Dashboard: Open Accept → Transactions, select the payment, and choose Refund.
  • API: Call POST /refunds at https://api.sandbox.natural.com with a sandbox key.
Refunds complete automatically and reduce the merchant’s available sandbox balance by the refunded amount. If POST /refunds answers 409 with code: "conflict" and no refund of that payment is pending, refunds are not enabled in that Sandbox environment yet. No refund was created, and the request can be retried later.