CVV
What is CVV
CVV, or Card Verification Value, is a crucial security feature on credit and debit cards. It consists of a three- or four-digit number printed on the card, typically on the back for Visa, MasterCard, and Discover, and on the front for American Express. The CVV serves as an additional layer of protection during online and in-person transactions. When making a payment, the CVV is required to verify that the person using the card has physical possession of it. This helps reduce the risk of unauthorized transactions, as even if someone has the card number and expiration date, they would still need the CVV to complete a payment.
CVV Response Codes
At Preczn, we streamline the CVV response process by normalizing responses across connections into a unified set of standardized response codes. This approach ensures consistency and simplifies the interpretation of CVV results regardless of which connections you decide to use.
| Code | Result | Description |
|---|---|---|
N | No CVV Match | Returned for transactions where a CVV is provided but is incorrect, and CVV validation is enabled on the merchant account at the processor. |
M | CVV Match | Returned when the provided value is correct, and CVV validation is enabled on the merchant account at the processor. |
U | CVV Unchecked | Returned when the processor does not validate the CVV value provided, typically when the merchant account at the processor is not configured to validate CVV, or if the CVV value is not provided. (NOTE - This can be tested by providing only the number and expiration properties of the payment object of the /v1/transactions endpoint request body.) |
Note
CVV validation does not occur using PaymentFields to create a single-use token. However, you can check the validity of the CVV represented in the resulting single-use token by sending that token in a Verify request!
Updated 9 months ago