Frequently Asked Question

Are merchants allowed to request card-verification codes/values from cardholders?
Yes. These values are typically used for card-not-present (CNP) transactions, where the card is not physically present at the merchant location (for example, during e-commerce or mail order/telephone order transactions). In many cases, it is necessary for the merchant to request this information in order to conduct a CNP transaction.
The card verification code or value (also referred to as CVV2, CVC2, CID, or CAV2) is the three- or four- digit code printed on the front or back of a payment card which provides additional assurance that the card is in the possession of the authorized cardholder. Card verification codes/values are considered to be sensitive authentication data (SAD) and merchants and other entities involved in payment card processing are required to strictly protect this data and securely delete it after authorization in accordance with PCI DSS Requirement 3.2.
The card verification code or value (also referred to as CVV2, CVC2, CID, or CAV2) is the three- or four- digit code printed on the front or back of a payment card which provides additional assurance that the card is in the possession of the authorized cardholder. Card verification codes/values are considered to be sensitive authentication data (SAD) and merchants and other entities involved in payment card processing are required to strictly protect this data and securely delete it after authorization in accordance with PCI DSS Requirement 3.2.
January 2015
Article Number: 1319
Related
-
How should PCI DSS v4.x requirements noted as superseded by another requirement be reported after 31 March 2025?
-
Are providers of third-party scripts for e-commerce environments considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
Why do requirements 8.3.9 and 8.3.10.1 focus on passwords/passphrases used for single-factor authentication, when multi-factor authentication is required for all access into the CDE?
Featured FAQ Articles
Featured
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Is the PCI DSS Attestation of Compliance intended to be shared?
-
How does an entity report the results of a PCI DSS assessment for new requirements that are noted in PCI DSS as best practices until a future date?
-
Where do I direct questions about complying with PCI standards?
-
Can SAQ eligibility criteria be used for determining applicability of PCI DSS requirements for assessments documented in a Report on Compliance?
Most Popular
-
How should PCI DSS v4.x requirements noted as superseded by another requirement be reported after 31 March 2025?
-
Are providers of third-party scripts for e-commerce environments considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
Why do requirements 8.3.9 and 8.3.10.1 focus on passwords/passphrases used for single-factor authentication, when multi-factor authentication is required for all access into the CDE?
-
Do PCI DSS Requirements 8.3.9 and 8.3.10.1 apply to all system components?
-
Is the cardholder in scope for PCI DSS?
Most Recently Updated
-
How should PCI DSS v4.x requirements noted as superseded by another requirement be reported after 31 March 2025?
-
Are providers of third-party scripts for e-commerce environments considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
Why do requirements 8.3.9 and 8.3.10.1 focus on passwords/passphrases used for single-factor authentication, when multi-factor authentication is required for all access into the CDE?
-
Do PCI DSS Requirements 8.3.9 and 8.3.10.1 apply to all system components?
-
Is the cardholder in scope for PCI DSS?