

The payment fails because debits aren’t authorized.

The payment fails due to insufficient funds. The payment fails because no account is found. The payment fails because the account is closed. This is true whether you’re serving a payment form you can test interactively or writing test code.ĭifferent payment methods have different test procedures: Non-card paymentsĪny time you use a test non-card payment method, use test API keys in all API calls. See our documentation on load testing for an alternative approach. Because the load limiter is stricter in test mode, you might see errors that you wouldn’t see in production. We don’t recommend load testing your integration using the Stripe API in test mode. These errors come from our rate limiter, which is stricter in test mode than in live mode.

If your requests in test mode begin to receive 429 HTTP errors, make them less frequently.
