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 evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
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
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
Most Recently Updated
-
How does encrypted cardholder data impact PCI DSS scope for third-party service providers?
-
Does PCI SSC provide a list of PCI DSS-compliant third-party service providers?
-
How does encrypted cardholder data impact PCI DSS scope?
-
What effect does the use of a PCI-listed P2PE solution have on a merchant's PCI DSS validation?
-
Are Mobile Payments on COTS (MPoC)™ solutions, Software-based PIN Entry on COTS (SPoC)™ solutions, or Contactless Payments on COTS (CPoC™) solutions eligible for a P2PE Solution approval?