CVV Test SCA: Card Verification in Strong Customer Authentication

What CVV test SCA means

CVV test SCA is a method to check card verification value (CVV) in a Strong Customer Authentication (SCA) flow. Test card numbers from payment processors stand in for real card data. The test numbers return known CVV results. This lets developers confirm that their payment system handles CVV checks under SCA rules.

read more

What CVV is

CVV is a 3 or 4 digit code on a payment card. Visa, Mastercard, and American Express use CVV2 or CVC2 for online transactions. The code proves the card holder has the physical card. Merchants send the CVV to the payment processor. The processor checks the code with the issuer.

CVV Test SCA Overview: A Guide for Buyers and Sellers

What SCA is

Strong Customer Authentication is a requirement from the EU Payment Services Directive 2 (PSD2). SCA needs two of three factors: something you know, something you have, something you are. A password plus a phone code is one example. SCA applies to electronic payments in the European Economic Area. The US has no federal SCA mandate.

CVV Test SCA Explanation

How SCA affects CVV checks

SCA changes the payment flow. The issuer may ask for a second factor. The CVV check runs. A transaction can fail if the CVV is wrong. A transaction can fail if SCA is not completed. Processors send an error code for each case. Developers need test cases for both.

Test CVV numbers for SCA

Payment processors publish test card numbers. Stripe lists test cards for SCA. For example, the Visa test card 4000 0000 0000 3220 requires 3D Secure authentication. The CVV for that card is any 3 digits. The test card 4000 0000 0000 3063 returns a CVV failure. These numbers work in test mode. They do not work with live accounts.

Limits of CVV test SCA

Test numbers do not mimic every issuer rule. Some issuers treat CVV checks as optional. Some SCA exemptions skip the second factor. A test environment cannot cover all real-world cases. Developers should read the processor documentation for each region.

Common errors

• Using a live card number in a test environment.
• Expecting a test CVV to pass on all processors.
• Ignoring SCA error codes that appear with a valid CVV.