Short answer

Stripe test mode does not check a real CVC. Any 3-digit number works with the standard success cards such as 4242 4242 4242 4242. The digits only matter when you want a specific outcome, like a failed CVC check or an incorrect_cvc decline. For those results you must use a card number that Stripe maps to that response, not a random CVC on a success card.

stripe cvv checker

Prerequisites

• A Stripe account with test mode keys, meaning a test publishable key and a test secret key.
• A checkout page, form, or script that points at those test keys.
• Optional: the Stripe CLI installed and logged in if you plan to test from the command line.

Test a CVV in five steps

1. Open your checkout page in test mode, or open the test card list in the Stripe Dashboard under Developers.
2. Enter the card number 4242 4242 4242 4242.
3. Enter any 3-digit CVC, any future expiry date, and any 5-digit postal code.
4. Submit the payment and confirm the PaymentIntent shows a status of succeeded in the Dashboard.
5. Repeat the same flow with a CVC test card, then read the decline code or the cvc_check value on the resulting charge.

Test cards that produce a CVC result

• 4000 0000 0000 0101: the check returns fail for cvc_check and the payment does not go through.
• 4000 0000 0000 0127: the payment is declined with the code incorrect_cvc.
• 4242 4242 4242 4242: succeeds with any 3-digit CVC.
• 3782 8224 6310 005: American Express, which uses a 4-digit CID instead of a 3-digit CVC.

Stripe edits its test card list as new decline paths are added. Check the current testing page before you build assertions on one number.

Stripe CVV Test Card: Guide to Purchasing

Token and PaymentMethod shortcuts

Server side tests can skip the card form. Create a token such as tok_visa or a PaymentMethod such as pm_card_visa, then confirm the PaymentIntent with it. These helpers carry no card verification value, so cvc_check comes back as unavailable rather than pass or fail. Use raw test card numbers when the CVC result itself is the thing you are testing.

test cvv stripe

Why a CVC test fails in your own integration

• The CVC field is sent as a string with spaces, dashes, or letters in it.
• The field length does not match the brand, so a 4-digit Amex CID is submitted into a 3-digit field.
• The PaymentIntent is confirmed without the PaymentMethod that holds the card details.
• Test keys are paired with live card numbers, or live keys are paired with test card numbers.
• Your form blocks the submit before the value ever reaches the API.

What test mode does not prove

• Issuer behavior on real cards, address verification results, and 3D Secure challenges from a real bank.
• Storage rules. A CVC is sensitive authentication data under PCI DSS and must not be stored after authorization, in test mode or live mode.
• That your production keys, webhook endpoints, and error handling work the same way they do in the sandbox.