Frequently Asked Question

How does PCI DSS apply to EMVCo Payment Tokens?
Payment Tokens, as defined by EMVCo in the "EMVCo Payment Tokenisation Specification - Technical Framework", are provided to merchants and acquirers in lieu of the cardholder's PAN. They are routed through the payment networks in the same way as a PAN and allow transactions to occur without the merchant being exposed to the underlying PAN.
Payment Tokens must be used in conjunction with a dynamic token cryptogram and/or other sufficient domain controls that are enforced during a payment transaction (as defined by the EMVCo Payment Tokenisation Specification - Technical Framework) to adequately prevent fraud. It is also not feasible to recover the PAN value associated with the Payment Token through knowledge of only the Payment Token, multiple Payment Tokens, or other Payment Token to PAN combinations.
Applicability of PCI DSS to Payment Tokens is described below.
For entities designated by EMVCo as Token Service Providers:
For all other entities (including merchants and acquirers):
PCI DSS still applies anywhere Account Data is stored, processed, or transmitted. If any system storing, processing, or transmitting Payment Tokens also stores, processes, or transmits Account Data (such as a PAN), or is connected to systems that store, process or transmit Account Data, those systems remain in scope for PCI DSS requirements.
Please note that while some EMV-compliant chip cards and mobile phones may use Payment Tokens for payment, the use of an EMV-capable terminal or the acceptance of mobile or EMV chip transactions is not an indication that Payment Tokens are necessarily in use. Payment Tokens may be used in multiple types of payment transactions, including from chip cards, mobile devices, and card-on-file services. For more information about Payment Tokens, refer to the EMVCo website — www.emvco.com.
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?