A Stripe test card CVV example is any three-digit number, such as 123 or 456, entered with any future expiry date. For American Express test cards, use any four-digit CVV instead. Stripe accepts these placeholder values in test mode, so you never need real card data to check a payment flow.
CVV rules for Stripe test cards
Test mode does not validate the CVV against an issuing bank, so the value itself rarely matters. What matters is the length, because the field is formatted by card brand.
- Visa, Mastercard, Discover, JCB, Diners Club, UnionPay: any three digits, for example 123.
- American Express: any four digits, for example 1234.
- Expiry date: any date in the future.
- ZIP or postal code: any value, unless the specific test card is built to trigger an address check result.
The rule of thumb is simple: if the card number is a Stripe test number, the CVV is a placeholder too.
Common Stripe test card numbers
These are the card numbers most developers pair with a test CVV. Each one sits in a range that issuers never assign to live accounts.
Stripe Test Card CVV Generator: A Comprehensive Guide
- 4242 4242 4242 4242 (Visa)
- 4000 0566 5566 5556 (Visa debit)
- 5555 5555 5555 4444 (Mastercard)
- 5200 8282 8282 8210 (Mastercard debit)
- 3782 822463 10005 (American Express)
- 3714 496353 98431 (American Express)
- 6011 1111 1111 1117 (Discover)
- 3056 9300 0902 0004 (Diners Club)
- 3566 0020 2036 0505 (JCB)
- 6200 0000 0000 0005 (UnionPay)
With any of these, a Stripe test card CVV example like 123 or 1234 completes the form and the charge succeeds in test mode.
Test cards that simulate a CVV failure
Sometimes you want the payment to fail so you can style the error state. Stripe publishes dedicated decline cards for that purpose. For example, 4000 0000 0000 0127 returns an incorrect CVC response, which lets you verify how your checkout screen handles a failed verification message. Other cards in the same family cover generic declines, expired cards, and cards that require 3D Secure authentication.
One detail worth noting: when you use a plain success card, Stripe does not force a CVC mismatch, so any digits you type pass. To see the failure path, you have to choose a card number built for it.
Keep test values inside test mode
Test card numbers and placeholder CVVs belong only in sandbox environments, local builds, and automated test suites. Three habits keep the boundary clear:
- Use publishable and secret keys from test mode, never live keys, when running sample payments.
- Never paste a real card number or CVV into a test form, a screenshot, or a code comment.
- Do not log or store the CVV of any card, including in staging databases that mirror production.
Card verification values are meant to be passed through for a single authorization and then dropped. That rule applies to test data hygiene as much as it does to live traffic.
Confirming current values
Card brands and processors update their test ranges from time to time, and new decline scenarios get added. Before you hard-code anything into a test suite, check the testing page in Stripe's documentation and the test card list in your own dashboard, which reflects the API version your account uses. That way your Stripe test card CVV example stays accurate as the platform evolves.