Frequently Asked Question

Which types of tokens are addressed by the PCI SSC tokenization documents?
PCI SSC has published a number of documents and supporting FAQs that are each intended for a specific type(s) of tokens. An overview of the documents and the applicability is provided below.
-
Additional Security Requirements and Assessment Procedures for Token Service Providers (EMV Payment Tokens) (2015): An additional standard intended for entities designated by EMVCo as Token Service Providers for Payment Tokens. These requirements apply in addition to PCI DSS for the protection of the environment where the Token Service Provider performs tokenization services (token data environment). Assessment and validation against these requirements may be required by payment brands for registered Token Service Providers
-
Tokenization Product Security Guidelines (2015): Technical best practices for the development of tokenization solutions for acquiring tokens. The Tokenization Product Security Guidelines are intended as guidance only; there is no program or validation associated with the guidelines.
-
PCI DSS Information Supplement: PCI DSS Tokenization Guidelines (2011): General guidance on the use of acquiring tokens in the payment industry. These guidelines provide a high-level introduction to tokenization concepts and security considerations, and do not define any technical specifications or implementation requirements. This document is intended as general guidance only.
For more information about types of tokens used in the payment industry, refer to What is the difference between 'acquiring tokens', 'issuer tokens', and 'Payment Tokens'?
Related
-
What are the expectations for entities when assigning risk rankings to vulnerabilities and resolving or addressing those vulnerabilities?
-
Is phishing-resistant authentication alone acceptable as multi-factor authentication for PCI DSS Requirements 8.4.1 and 8.4.3?
-
Are passkeys synced across devices, implemented according to the FIDO2 requirements, acceptable for use as phishing-resistant authentication to meet PCI DSS Requirement 8.4.2?
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 as a guide for determining applicability of PCI DSS requirements for merchant assessments documented in a Report on Compliance?
Most Popular
-
What are the expectations for entities when assigning risk rankings to vulnerabilities and resolving or addressing those vulnerabilities?
-
Is phishing-resistant authentication alone acceptable as multi-factor authentication for PCI DSS Requirements 8.4.1 and 8.4.3?
-
Are passkeys synced across devices, implemented according to the FIDO2 requirements, acceptable for use as phishing-resistant authentication to meet PCI DSS Requirement 8.4.2?
-
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?
Most Recently Updated
-
How often must service providers test penetration testing segmentation controls under PCI DSS?
-
Are merchants allowed to request card-verification codes/values from cardholders?
-
What is the maximum period of time that cardholder data can be stored?
-
How can an entity ensure that hashed and truncated versions cannot be correlated?
-
Are point-of-interaction devices required to be physically secured (for example, with a cable or tether) to prevent removal or substitution to meet PCI DSS Requirement 9.5?