What is PCI DSS?
The Payment Card Industry Data Security Standard (PCI DSS) is a set of security requirements for any organization that stores, processes or transmits payment card data, or can affect its security. The PCI Security Standards Council, founded by the major card brands, maintains it. The current version is PCI DSS v4.0.1.
For example, a retailer adds an AI assistant to its contact center to summarize calls. Customers read their card numbers aloud to pay, a speech-to-text service transcribes them, and the transcripts go to a language model and a log store. The AI pipeline now handles cardholder data, so it falls inside the retailer’s PCI DSS scope. This is a summary, not legal advice.
PCI DSS v4.0.1 key dates
- March 2022. PCI DSS v4.0 is published.
- June 2024. PCI DSS v4.0.1, a limited revision, is published.
- December 31, 2024. v4.0 is retired, leaving v4.0.1 as the only active version.
- March 31, 2025. The future-dated requirements introduced in v4.0 become mandatory.
The 12 PCI DSS requirements
- Install and maintain network security controls.
- Apply secure configurations to all system components.
- Protect stored account data.
- Protect cardholder data with strong cryptography during transmission over open, public networks.
- Protect all systems and networks from malicious software.
- Develop and maintain secure systems and software.
- Restrict access to system components and cardholder data by business need to know.
- Identify users and authenticate access to system components.
- Restrict physical access to cardholder data.
- Log and monitor all access to system components and cardholder data.
- Test security of systems and networks regularly.
- Support information security with organizational policies and programs.
What data PCI DSS protects
Account data has two parts. Cardholder data is the primary account number (PAN), cardholder name, expiration date and service code. Sensitive authentication data includes full track data, card verification codes and PINs, and must not be stored after authorization, even if encrypted. Wherever the PAN is stored, it must be unreadable, for example through strong cryptography, truncation, one-way hashing or index tokens. See how PCI data differs from PII and PHI.
Why PCI DSS matters for AI systems
Card numbers turn up in places no one designed for them: chat messages, call transcripts, support tickets and emails. When those feed a model, a vector database or prompt logs, each of those systems can come into scope. Replacing the PAN before it enters the AI pipeline keeps those systems from storing readable card data, which can reduce scope. Your qualified security assessor (QSA) makes the final scope decision. Also check retention: requirement 3 expects stored account data to be kept only as long as needed, and that applies to prompt logs and chat histories as much as to databases.
How Protecto helps
Protecto detects PCI data, including card numbers, in structured and unstructured text, and replaces it with format-preserving tokens before it reaches models, logs or analytics. Authorized users and systems see real values only where policy allows, and audit logs record each access. See tokenization for data lakes.
Frequently asked questions
Is PCI DSS a law?
No. It is an industry standard enforced through contracts with card brands and acquiring banks. Penalties for noncompliance usually come as fines or higher fees from those parties.
What is the current version of PCI DSS?
PCI DSS v4.0.1, published in June 2024. Version 4.0 was retired on December 31, 2024, and the future-dated requirements became mandatory on March 31, 2025.
Does tokenization reduce PCI DSS scope?
It can. Systems that hold only tokens, with no way to recover the PAN, may fall out of scope, but the tokenization system itself stays in scope. Your QSA makes the final call.
Related terms
PCI data · Tokenization · Format-preserving encryption · Data encryption · Sensitive data