What a Test Stripe Card Is

A test Stripe card is a card number that Stripe accepts only while your account is in test mode. It passes the same validation path as a live card but never touches a real bank network, so no funds move and no cardholder is charged.

stripe test cards

The number most developers start with is 4242 4242 4242 4242. Use any future expiry date, any three digit CVC, and any postal code. That combination returns a successful charge every time.

stripe card tester

Prerequisites

  • A Stripe account with access to the Dashboard.
  • The test mode toggle switched on.
  • Your test API keys, which begin with pk_test_ and sk_test_.
  • A checkout page, payment form, or API client that points at those test keys.

How to Run a Test Payment

  1. Open the Stripe Dashboard and confirm the test mode toggle is active.
  2. Copy the publishable test key into your front end configuration.
  3. Copy the secret test key into your server environment variables.
  4. Load your payment form and enter 4242 4242 4242 4242 in the card field.
  5. Enter any future expiry date, such as 12/34.
  6. Enter any three digit CVC, or four digits if you use an American Express test number.
  7. Submit the payment and confirm the response object shows a succeeded status.
  8. Open the Payments list in the Dashboard and verify the charge appears under test mode.

Test Numbers by Outcome

  • 4242 4242 4242 4242 charges with no authentication step.
  • 4000 0025 0000 3155 forces a 3D Secure authentication challenge.
  • 4000 0000 0000 0002 returns a generic card decline.
  • 4000 0000 0000 9995 returns an insufficient funds decline.
  • 4000 0000 0000 0069 returns an expired card decline.
  • 4000 0000 0000 0127 returns an incorrect CVC decline.
  • 5555 5555 5555 4444 is a Mastercard approval.
  • 3782 822463 10005 is an American Express approval.

CVC, Expiry, and Postal Code Rules

Stripe does not validate the CVC or postal code on most test cards, so any value is accepted. The exception is the small set of numbers built to trigger specific error codes, such as the incorrect CVC card above. Expiry dates must still be in the future, otherwise the request fails validation before it reaches the decline logic.

related article

Common Mistakes

  • Mixing a live publishable key with a test secret key, which produces an authentication error.
  • Testing a decline card and then assuming the integration is broken.
  • Building decline handling only after launch instead of simulating it in test mode.
  • Storing CVC values after authorization, which PCI DSS prohibits.

Run each outcome at least once before you switch to live keys. A payment flow that handles the generic decline, the insufficient funds decline, and the 3D Secure challenge covers the scenarios most real customers will hit.

The Ultimate Guide to Choosing the Best Stripe Card Checker