Top pick: 4000 0000 0000 0127. This Stripe test card returns an incorrect CVC error, which makes it the clearest choice when you need to verify that your checkout handles CVC validation failures. The criteria used here are predictable CVC behavior, support for 3D Secure, usefulness for decline handling, and whether the card works in standard test mode without real charges.
stripe test card cvv procedure
Top pick: 4000 0000 0000 0127 for CVC failure testing
This card is designed to simulate a CVC mismatch. It is the most direct way to check that your payment form shows the right error and stops the charge.
Pros
- Returns an incorrect CVC error in Stripe test mode.
- Lets you test error messaging and form validation.
- Creates no real charge.
Cons
- Covers only the failure path.
- Does not confirm that a valid CVC succeeds.
Use-case recommendation: use this card when you need to confirm that a CVC mismatch blocks the payment and displays a clear message to the customer.
Stripe Card CVV Test: How CVC Checks Work in Test Mode
Baseline success card: 4242 4242 4242 4242
This is the standard Stripe Visa test card. Stripe accepts any three-digit CVC with it, so it is useful for the happy path, not for CVC rejection testing.
Pros
- Accepts any three-digit CVC.
- Works across most Stripe test flows.
- Simple to use for smoke tests.
Cons
- Does not test CVC rejection.
- Can hide gaps in CVC error handling.
Use-case recommendation: use this card for initial checkout tests and happy-path order creation before you test failure cases.
CVC check failure card: 4000 0000 0000 0101
This card simulates a failed CVC check. It is different from an incorrect CVC error, so it is useful when your integration relies on the cvc_check field from Stripe.
Pros
- Simulates a failed CVC check.
- Useful for testing risk rules and manual review flows.
- Creates no real charge.
Cons
- The outcome depends on how your integration reads cvc_check.
- Not a generic decline card.
Use-case recommendation: use this card when you need to verify that your system reacts correctly to a failed CVC check rather than a simple incorrect CVC error.
3D Secure card with CVC: 4000 0000 0000 3220
This card triggers 3D Secure 2 authentication in test mode. Stripe still accepts any three-digit CVC with it, so it tests authentication and CVC handling together.
Pros
- Triggers a 3D Secure 2 challenge.
- Accepts any CVC for the CVC field.
- Tests authentication and payment confirmation in one flow.
Cons
- Adds an authentication step to every test run.
- Not a pure CVC validation test.
Use-case recommendation: use this card when your checkout requires 3D Secure and you still need to confirm that CVC input is handled correctly.
Generic decline card: 4000 0000 0000 0002
This card returns a generic decline. It is useful for decline handling, but it does not test CVC validation directly.
Pros
- Produces a predictable decline.
- Tests decline messaging and order state.
- Creates no real charge.
Cons
- Not CVC-specific.
- Does not validate CVC input behavior.
Use-case recommendation: use this card to confirm that declined payments do not create orders, send duplicate receipts, or trigger retry loops.
How Stripe handles CVC in test mode
Stripe does not contact card issuers in test mode. Most Stripe test cards accept any three-digit CVC, and American Express test cards accept a four-digit CVC. The card number determines the result. Some test cards are hard-coded to return CVC errors, so a random CVC will not fail on 4242 4242 4242 4242. You must choose the test card that matches the scenario you want to exercise.
Criteria for choosing a Stripe test card
Use these criteria to build a checkout test plan that covers CVC success, CVC failure, and authentication.
Pros
- Catches CVC handling gaps before launch.
- Covers success, failure, and 3D Secure paths.
- Keeps testing predictable and repeatable.
Cons
- Requires multiple test runs.
- Needs separate card numbers for each scenario.
- Predictable CVC outcome: the card should either accept any CVC or fail with a known CVC error.
- No real charges: the card must work only in Stripe test mode.
- Coverage of failure paths: the card should test incorrect CVC, cvc_check failure, or 3D Secure.
- Compatibility with your flow: one-time payments, subscriptions, and 3D Secure may need different cards.
Use-case recommendation: apply these criteria when you build a checkout test plan for a new Stripe integration or a change to your payment form.
Common mistakes
- Using live API keys with test card numbers.
- Assuming Stripe stores the CVC. PCI rules prohibit storing CVV values after authorization.
- Testing only 4242 4242 4242 4242 and never testing a CVC failure card.
- Forgetting that American Express test cards use a four-digit CVC.
- Treating a cvc_check failure as the same thing as an incorrect CVC error.
Recommendation
Start with 4242 4242 4242 4242 for the happy path. Then use 4000 0000 0000 0127 to test incorrect CVC handling and 4000 0000 0000 0101 to test cvc_check failures. Add 4000 0000 0000 3220 when your checkout includes 3D Secure. Keep all testing in Stripe test mode, and never store CVV values in your database or logs.