What is PCI data?
PCI data is payment card information protected under the Payment Card Industry Data Security Standard (PCI DSS). It has two parts. Cardholder data includes the primary account number (PAN), cardholder name, expiration date and service code. Sensitive authentication data includes full magnetic-stripe or chip data, card verification codes and PINs.
For example, a customer disputing a charge types their full card number and security code into a support chat. The chat transcript goes to an AI model for a summary, then into a ticket, a log file and an analytics warehouse. Each of those systems now stores card data, and each one may now fall inside PCI DSS scope.
Cardholder data vs sensitive authentication data
| Element | Category | Storage rule |
|---|---|---|
| Primary account number (PAN) | Cardholder data | May be stored only if rendered unreadable, for example by tokenization, truncation or strong cryptography |
| Cardholder name, expiration date, service code | Cardholder data | Must be protected when stored with the PAN |
| Full track or chip data | Sensitive authentication data | Must not be stored after authorization, even if encrypted |
| Card verification code (CVV2, CVC2, CID) | Sensitive authentication data | Must not be stored after authorization, even if encrypted |
| PIN | Sensitive authentication data | Must not be stored after authorization, even if encrypted |
PCI DSS version 4.0.1 is the current version of the standard. Its newer requirements, which were phased in, became mandatory on March 31, 2025. PCI DSS also limits how much of a PAN can be displayed, to no more than the BIN and last four digits for people without a business need to see more.
How tokenization shrinks PCI scope
Every system that stores, processes or sends cardholder data is in scope for PCI DSS, along with systems connected to it. Replacing the PAN with a token early means downstream systems only hold tokens. If those systems cannot reach the token vault or the real card numbers, they may fall outside scope. Your Qualified Security Assessor (QSA) decides what is in scope. Fewer systems in scope usually means fewer controls to test and a smaller audit each year.
Chat input: My card 4929 3810 4756 1203 was charged twice. To the model: My card <CREDIT_CARD>tok_c4d9</CREDIT_CARD> was charged twice.
Why PCI data matters for AI systems
Card numbers show up in places nobody planned for: chat messages, call-center transcripts, email threads and scanned forms. When AI systems summarize or search that text, card data spreads into prompts, vector stores and logs. A rule that tokenizes PANs and drops security codes before text reaches a model keeps those copies clean. This guide to PII, PHI and PCI explains how the three data types overlap.
How Protecto helps
Protecto Vault detects card numbers and other PCI entity types among 200+ built-in types, and replaces them with tokens in prompts, transcripts and data pipelines. Format-preserving masking keeps the shape of the value where downstream checks need it. Authorized users and tools receive real values only where policy allows.
Frequently asked questions
Is the cardholder name PCI data?
Yes, when it is stored, processed or sent together with the primary account number. On its own, a name is not cardholder data.
Can a business store the CVV after a payment?
No. PCI DSS does not allow card verification codes to be stored after authorization, even in encrypted form.
Does tokenization take systems out of PCI DSS scope?
It can reduce scope. Systems that hold only tokens and cannot reach the vault or real card numbers may be out of scope, but a Qualified Security Assessor confirms it.
Related terms
PCI DSS · Tokenization · Format-preserving encryption · Sensitive data