Founder deal: 75% off the lifetime licence. Unlimited sites, one payment, every update.See the founder plan
Home / Docs / Testing and sandbox

Testing and sandbox

What to test before you take real money, and how to force the failures you need to see.

Test cards

NumberBrandCVVResult
4111 1111 1111 1111Visa999Approves
5431 1111 1111 1111Mastercard999Approves
6011 6011 1111 1111Discover999Approves
3714 4963 5398 431Amex9997Approves

Any future expiry date works. Use 10 / 25 to force an expired card decline.

Forcing failures

The sandbox uses the order total to trigger specific outcomes, which is how you test your error handling without waiting for a real decline.

Total ends inResult
.00Approved
.05Declined
.10Processor error or timeout

Test ACH details

Routing number 123123123 Account number 1234567890 Account type Checking SEC code WEB

Pre launch checklist

  1. Sale approves and the order completes
  2. Decline shows a usable message rather than a raw gateway code
  3. Partial refund appears in both WooCommerce and the gateway
  4. Void works on an uncaptured authorization
  5. Saved card appears in My Account and can be deleted
  6. Second order with a saved card completes without card entry
  7. Subscription renewal charges the vault token, if you sell subscriptions
  8. The gateway log contains no card number, CVV or security key
  9. Checkout works on a phone, not just a desktop browser
  10. One live transaction with a real card, then refunded

Testing on staging

Staging sites do not consume a licence slot. Use sandbox credentials there permanently, and keep the sandbox banner enabled so a copied database never quietly charges a real card.