Short answer
In Stripe test mode, the CVC field accepts any three digits. Stripe does not send test transactions to a real issuer, so 123, 000, and 999 all pass when paired with a standard test card such as 4242 4242 4242 4242. Real CVC validation starts only when you switch to live keys and a real cardholder enters a real card.
If you need a failed CVC response, Stripe publishes a test card that forces the incorrect_cvc decline code, so you can test your error handling without guessing.
Prerequisites
- A Stripe account with access to test mode
- Your test keys, pk_test and sk_test, from the Dashboard
- A server environment, the Stripe CLI, or an API client such as curl
- A card number taken from Stripe's public test list
Run a CVC test
- Open the Stripe Dashboard and confirm the Test mode toggle is enabled.
- Go to Developers, then API keys, and copy the test secret key.
- Create a PaymentIntent with the test key and a small amount in your account currency.
- Enter card number 4242 4242 4242 4242 with any future expiry date and any 3-digit CVC.
- Submit the confirmation request and read the returned status.
- Repeat the request with card number 4000 0000 0000 0127 to trigger the
incorrect_cvcdecline. - Log the
decline_codefrom the response and compare it with the value you expected. - Fire your webhook handler and confirm it processes the
payment_intent.payment_failedevent without errors.
What the test proves
A test-mode CVC run verifies your client code, not the cardholder. It shows that your form accepts three or four digits, that your server passes the CVC to Stripe, that your interface displays a decline message when Stripe returns one, and that your webhook listener handles the failure event. Covered declines for lost card, stolen card, and expired card can be exercised the same way with the other public test numbers.
What the test does not prove
Test mode skips the issuer. It returns no real CVC match result, no address verification result tied to a real bank, and no 3D Secure challenge unless you use one of the 3DS test cards that Stripe documents for that purpose. A passing test charge is not evidence that a live card is valid.
Boundaries that keep the test legal
- Use only numbers from Stripe's published test list. Never type a real card number into test mode.
- Do not run card enumeration, low-value probing, or CVC guessing against live keys. Stripe's Services Agreement and the card network rules prohibit it.
- In the United States, trafficking in or using card account numbers you are not authorized to use falls under 18 U.S.C. 1029.
- Keep CVC data out of logs, databases, and analytics, per PCI DSS requirement 3.2.
In short, a Stripe CVC test is a developer check on your own code path. Treat the test card list as the only input source, and treat every live card number as data you must not touch.