Stripe Test CVV: Test Card CVC Codes for Test Mode

The top pick for a Stripe test CVV is any three-digit value, such as 123, paired with the standard test card 4242 4242 4242 4242. Stripe test mode does not check the CVC against a real issuer, so the field accepts most three-digit inputs. The criteria used here: the value must come from Stripe's own test documentation, it must work with test API keys, and it must let you trigger a specific outcome such as a failed CVC check.

Any 3-digit CVC with 4242 4242 4242 4242

This is the default choice for a successful test payment. Use a future expiry date, any three-digit CVC, and any postal code your test flow requires. The same rule applies to most of Stripe's standard test numbers.

• Pros: fast to type, works for one-time payments, subscriptions, and saved payment methods. No special setup in the Dashboard.
• Pros: the same card number appears throughout Stripe's documentation, so results are easy to compare with other developers.
• Cons: it never triggers a CVC rejection, so it cannot test your error copy or retry path for a failed verification.
• Cons: it only works with test API keys. A live key will reject the card.

Use it when you need a clean success path: a checkout page that completes, a subscription that starts, or a payment method that saves to a customer.

Dedicated test numbers for CVC check failures

Stripe documents test card numbers that force a CVC problem. Two common examples are 4000 0000 0000 0101 and 4000 0000 0000 0127. The first is used to simulate a CVC check that fails at the issuer. The second is used to simulate an incorrect CVC decline. With either number, the CVC field still takes three digits; the card number controls the outcome.

• Pros: lets you verify that your form shows a clear message when the CVC is wrong and that your retry logic does not create duplicate charges.
• Pros: useful for support scripts and QA checklists that cover decline handling.
• Cons: you must change the card number, not the CVC, to get the failure. Typing 999 in the CVC field of the standard success card does nothing special.
• Cons: some outcomes depend on your account settings and on whether you use Payment Intents or Charges.

Use these numbers when you build or audit decline handling, especially the copy shown to a customer after a failed CVC check.

3D Secure test cards and the CVC field

Authentication tests need their own card numbers. Stripe documents cards such as 4000 0000 0000 3220 for a 3D Secure 2 challenge and 4000 0000 0000 3063 for a 3D Secure challenge. The CVC rule stays the same: any three digits in test mode. The card number drives the authentication step, and the CVC field just needs a valid length.

• Pros: covers the full flow, including the challenge window and the return to your site.
• Cons: adds a browser step, so automated tests need a way to complete or bypass the challenge.

Use a 3DS test card when your integration must handle authentication before capture, and keep a plain 4242 test for the non-authenticated path.

Common mistakes with Stripe test CVCs

• Using a live secret key with test card numbers. Switch to test keys first.
• Believing 123 is the only valid test CVC. Stripe test mode accepts most three-digit values for standard test cards.
• Forgetting that American Express test cards use a four-digit CVC. Pair a 4-digit value with a test Amex number such as 3782 822463 10005.
• Using an expired date. Test cards still need a future expiry month and year.
• Testing CVC failure by changing only the CVC. Use a dedicated failure card number instead.

Picking the right test CVV for your case

1. Happy path: 4242 4242 4242 4242 with CVC 123 and any future expiry.
2. CVC decline: 4000 0000 0000 0101 or 4000 0000 0000 0127 with any three-digit CVC.
3. 3D Secure: 4000 0000 0000 3220 with any three-digit CVC.
4. Amex format: 3782 822463 10005 with a four-digit CVC.

Keep test keys separate from live keys, log the card number used in each test case, and confirm the outcome in the Dashboard before you sign off on a release.