Test Credit Card numbers for Stripe

Basic test card numbers

Genuine card information cannot be used in test mode. Instead, use any of the following test card numbers, a valid expiration date in the future, and any random CVC number, to create a successful payment. Each basic test card’s billing country is set to U.S. If you need to create test card payments using cards for other billing countries, use our international test cards.

We recommend using our test IDs when testing your integration and creating charges, instead of passing card information directly to the API. Using these test IDs in place of card numbers helps ensure your production integration is developed in a PCI compliant manner and isn’t going to handle card information directly. Each test ID is human-readable and represents card information that has been tokenized with our client-side libraries (for example, Stripe Elements, Stripe.js).

International test card numbers

You can use any of the following test cards to simulate a successful payment for different billing countries.

Regulatory (3D Secure) test card numbers

The following card information tests payments affected by regional regulations such as Strong Customer Authentication (SCA). Use it to test saving cards with the Setup Intents API.

3D Secure test card numbers and tokens

Not all cards support 3D Secure or require you to redirect the customer to their card issuer’s authentication page. Use the following card information to test 3D Secure payments—be aware that 3D Secure redirects won’t occur for payments created directly in the Stripe Dashboard.

All other Visa and Mastercard test cards do not require authentication from the customer’s card issuer.

Testing for specific responses and errors

You can use the following test cards to create payments that produce specific responses—useful for testing different scenarios and error codes. Verification checks only run when the required information is provided (for example, for cvc_check to be set to fail, a CVC code must be provided).

By default, passing address or CVC data with the card number causes the address and CVC checks to succeed. If this information isn’t specified, the value of the checks is null. Any expiration date in the future is considered valid.

You can also provide invalid card details to test specific error codes resulting from incorrect information being provided. For example:

• invalid_expiry_month: Use an invalid month (for example, 13)
• invalid_expiry_year: Use a year in the past (for example, 1970)
• invalid_cvc: Use a two digit number (for example, 99)

Cartes Bancaires test card numbers

In test mode, you can use the test cards below to simulate a Cartes Bancaires charge:

Disputes

In test mode, you can use the test cards below to simulate a disputed transaction:

Submit either of the following values for uncategorized_text to test a won or lost dispute outcome:

You can also use these values to test dispute outcomes in the Dashboard. Enter one of these values into the Additional Information field during evidence submission and then click Submit evidence.

Link with Stripe

You can create test mode accounts for Link with Stripe using any valid email address. You can use fixed one-time passcode values for authenticating test mode accounts, as outlined below:

Rate limits

It is extremely unlikely for users to experience any rate limits with normal usage of the API, even at high volume. The most common causes for a user to experience rate limits are bugs, bulk data fetches, or extreme load testing.

If your requests begin to receive 429 HTTP errors, reduce the frequency of your requests. Each failed request is safe to retry as rate limiting takes place before any other action and prevents the request from being processed. When reducing your request frequency, we recommend an exponential backoff by first waiting one second before trying again. If your request continues to receive the same response, wait two seconds, then four seconds, and so on.

The rate limit in test mode is lower than the one in live mode. If you are experiencing rate limits but are unable to determine why, please let us know.

Sources

Use the following information when testing payments using Sources.

Redirect sources

When creating a test Source object that uses a redirect flow (for example, iDEAL), you can follow the URL returned in the redirect[url] field. This leads to a Stripe page that displays information about the API request, and where you can either authorize or cancel the payment.

Authorizing the payment redirects you to the URL specified in redirect[return_url].

BECS Direct Debit in Australia

You can create a test PaymentIntent that either succeeds or fails by doing the following:

1. Create a test PaymentMethod with the test BSB 000-000 and a test account number from the list below.
2. Use the resulting PaymentMethod in a confirmAuBecsDebitPayment request to create the test charge.

Test account numbers

SEPA Direct Debit

You can create a test PaymentIntent that either succeeds or fails by doing the following:

1. Create a test PaymentMethod with a test account number.
2. Use the resulting PaymentMethod in a confirmSepaDebitPayment request to create the test charge.

Test account numbers

Webhooks

To test your integration, perform actions using the API (in test mode) to send legitimate events to your endpoint. For instance, creating a charge triggers the charge.succeeded event that contains the charge data. You can easily trigger events with the Stripe CLI or Stripe for Visual Studio Code. You can then use the API to verify the resulting event data. If you’re migrating to the Payment Intents API, also see Monitoring a PaymentIntent with Webhooks.

You can also send test events to your integration’s endpoint within your account’s webhooks settings. However, the event data contained within these events is fabricated and not available in the API—its purpose is only to test that your endpoint is working and configured correctly.

See also