Stripe checks a card CVV during the authorization request. The card network returns a CVC result to Stripe. Stripe shows the result in the payment record. A mismatch can cause a decline. Merchants cannot read or store the CVV. Buying CVVs is card fraud and is illegal.
stripe test card cvv procedure
What the check covers
CVV means card verification value. Stripe uses the term CVC, card verification code. For online payments the value is the 3 or 4 digit code printed on the card. The check compares the submitted code with data held by the card issuer. Stripe sends the check as part of the payment authorization. The issuer returns pass, fail, unavailable, or unchecked.
Where the result appears
For Payment Intents, the result is in payment_method_details.card.checks.cvc_check. For older Charge objects, the result is in card.cvc_check. A failed check can return the decline code incorrect_cvc. A pass means the issuer matched the code. A pass does not prove the person owns the card. A pass does not block stolen card data. Use 3D Secure, Radar rules, and address checks with the CVV result.
What a merchant can store
PCI DSS bars storage of sensitive authentication data after authorization. That data includes the CVV. Stripe does not give merchants the CVV. Store the check result, not the code. Do not ask customers to send CVV by email or chat. Do not put CVV in order notes. Limit access to payment data.
Limits
Some issuers do not return a CVV result. Some card types and regions do not support the check. The result can be unavailable. A decline can come from the issuer for other reasons. Check the full decline code and the payment record. Do not treat a CVV pass as proof of identity.
Fraud warning
Sites that sell CVVs traffic in stolen card data. Use of that data is fraud. Card networks and banks monitor such activity. Merchants should block suspicious payments and report fraud. This guide does not cover buying CVVs.