
⏱ 2-minute read · open “Read more” for the details
If your company stores, processes or sends card numbers, you have to follow PCI DSS (security rules for protecting card data). It doesn’t matter if you are a corner shop, a fintech startup or a global bank. Yet in my experience many teams still treat it as a yearly paperwork exercise. That’s how card data gets stolen.
This is Part 1 of two. It explains PCI DSS in plain English: what it is, which version applies today, what “certification” really means, and how it fits with Visa, Mastercard, Amex, Apple Pay and PayPal.
What is PCI DSS?
Meet Leo, a product manager at an online store. The store takes card payments, so PCI DSS applies.
- PCI DSS is a set of security rules for protecting card data.
- It is written by the PCI Security Standards Council.
- It isn’t a law, but the card brands require it and banks write it into contracts.
Read more: What is PCI DSS?
PCI DSS (Payment Card Industry Data Security Standard) is a set of security rules for protecting card data. It is written by the PCI Security Standards Council, founded by Visa, Mastercard, American Express, Discover and JCB.
It isn’t a government law. But the card brands require it, and your bank (the acquirer) writes it into your contract. If you don’t comply, you can face fines, higher fees, or even lose the right to accept cards.
Which version applies today?
Leo checks which version applies.
- PCI DSS v4.0.1 is the only active version.
- Since 31 March 2025, every requirement is mandatory.
- In June 2026, the Council opened a new round of feedback.
Read more: Which version applies today?
- PCI DSS v4.0.1 is the only active version. It was published in June 2024, and the older v4.0 was retired at the end of 2024.
- Since 31 March 2025, every requirement is mandatory, including the ones that used to be “best practice” during the transition.
- In June 2026, the Council opened a request for comments to gather industry feedback for the next version, but no release date has been announced. For now, all assessments use v4.0.1.
Why it matters: the cost of getting it wrong
Getting it wrong is expensive.
- A breach in financial services costs $5.56 million on average (IBM, 2025).
- Fines, higher fees and lost customers can follow.
Read more: Why it matters: the cost of getting it wrong
According to IBM’s 2025 Cost of a Data Breach report, a breach in the financial industry costs $5.56 million on average, the second-highest of any industry. In the United States, the average breach cost reached a record $10.22 million. Card brand penalties, lost customers and a damaged reputation come on top of that.
The 12 requirements, in plain English
There are 12 requirements, grouped into six goals.
- Secure the network and systems.
- Protect card data, and encrypt it when it travels.
- Manage weaknesses, control access, monitor and test, and keep a security policy.
Read more: The 12 requirements, in plain English
PCI DSS has 12 main requirements, grouped into six goals:
| Goal | # | What it means |
|---|---|---|
| Secure network | 1 | Control what traffic can reach card systems (firewalls and network rules) |
| 2 | Set up every system securely; no default passwords | |
| Protect card data | 3 | Store as little card data as possible, and protect what you keep |
| 4 | Scramble (encrypt) card data when it travels over public networks | |
| Manage weaknesses | 5 | Protect systems against malware (viruses and other harmful software) |
| 6 | Build software securely and install security fixes (patches) quickly | |
| Control access | 7 | Give access only to people who need it |
| 8 | Identify every user, with strong passwords and multi-factor login | |
| 9 | Restrict physical access to card data and devices | |
| Monitor and test | 10 | Log and watch all access to card systems |
| 11 | Test security regularly with scans and penetration tests (hiring experts to try to break in) | |
| Policy | 12 | Keep a security policy and program, and train your people |
“PCI certified”: what it really means
There is no certificate you earn once. Leo must prove compliance every year.
- Level 1, over 6 million card transactions a year: a yearly formal report.
- Smaller merchants: a yearly self-assessment questionnaire.
- Your level decides the kind of proof.
Read more: “PCI certified”: what it really means
Here’s a common myth: there is no official “PCI certificate” that you earn once. Instead, you prove compliance every year, and the kind of proof depends on your size. For merchants, the card brands set four levels. Here are Visa’s:
| Level | Card transactions per year | What you must provide |
|---|---|---|
| Level 1 | More than 6 million | A yearly Report on Compliance (ROC) by a qualified assessor, quarterly external scans, and an Attestation of Compliance (AOC) |
| Level 2 | 1 million to 6 million | A yearly Self-Assessment Questionnaire (SAQ), quarterly scans, and an AOC |
| Level 3 | 20,000 to 1 million online | A yearly SAQ, quarterly scans, and an AOC |
| Level 4 | Fewer than 20,000 online, or up to 1 million in total | A yearly SAQ, plus scans if your bank asks |
Each card brand sets its own limits. American Express’s Level 1 starts lower, for example, so check every brand you accept. Service providers like processors and gateways have just two levels. Visa and Mastercard draw the line at 300,000 transactions a year.
Start on the left with who does the checking. Follow the arrows to see what each one produces. An outside or internal auditor writes a ROC. Smaller businesses fill in an SAQ. An approved scanning vendor (ASV) produces a quarterly scan report. It all comes together in the AOC, your signed proof, which goes to your bank and on to the card brands.
The key terms, simply:
- QSA (Qualified Security Assessor): an approved outside auditor.
- ISA (Internal Security Assessor): a trained, certified auditor inside your company.
- ASV (Approved Scanning Vendor): a company approved to scan your internet-facing systems every quarter.
- ROC (Report on Compliance): the full audit report.
- SAQ (Self-Assessment Questionnaire): the self-check form for smaller businesses. There are several types, depending on how you take payments.
- AOC (Attestation of Compliance): the signed statement you give your bank. This is the closest thing to a “certificate”.
How it fits with Visa, Mastercard, Amex, Apple Pay and PayPal
One rulebook, many referees.
- The Council writes the rules.
- The card brands and banks enforce them, each with its own program.
- Mobile wallets and PayPal each handle card data in their own way.
Read more: How it fits with Visa, Mastercard, Amex, Apple Pay and PayPal
One rulebook, many referees. The card brands wrote PCI DSS together, but the Council only writes the rules. The card brands and the banks enforce them. Each brand runs its own compliance program on top of PCI DSS, deciding who must prove what, how, and what happens if you don’t.
| Brand | Its own program | What it means for you |
|---|---|---|
| Visa | Account Information Security (AIS) program, once called CISP in the US | Sets the four merchant levels most businesses use. You prove compliance through your bank. |
| Mastercard | Site Data Protection (SDP) | Levels similar to Visa’s, but stricter at Level 2: merchants using certain SAQ types must have a qualified assessor (QSA) or certified internal assessor (ISA) validate. |
| American Express | Data Security Operating Policy (DSOP) | Lower limits: Level 1 starts at more than 2.5 million Amex transactions a year. Amex can charge non-compliance fees or end your agreement. |
| Discover | Discover Information Security Compliance (DISC) | Follows PCI DSS, with its own merchant levels. |
| JCB | Data Security Program | Only two merchant levels. |
Your level can be different for each brand, so check every brand you accept.
Apple Pay and other mobile wallets
Apple Pay isn’t a card brand. It’s a secure way to use a card. When a card is added, the bank creates a token called a Device Account Number. At checkout, the merchant gets that token plus a one-time security code, never the real card number. For recurring payments, Apple Pay can give a merchant-specific token (MPAN) that works on all the customer’s devices.
What this means for PCI: Apple Pay greatly lowers the risk, because there is no real card number to steal. But it doesn’t switch PCI DSS off. Customers still pay you with Visa, Mastercard or Amex cards, your terminals and checkout pages are still part of the payment flow, and your bank still expects your yearly proof.
PayPal
PayPal is a PCI DSS Level 1 service provider, the highest level. If you send customers to PayPal’s own hosted checkout, card details are entered on PayPal’s systems, not yours, so your part is small and you can usually use the shortest form, SAQ A. But you still complete that SAQ every year yourself.
The key point: Apple Pay, PayPal and hosted payment pages don’t make you exempt from PCI DSS. They make your part smaller. That’s exactly why they’re worth using.
The yearly compliance cycle
Every year, Leo’s team runs the same cycle.
- Find every place card data lives.
- Compare it with the 12 requirements and fix the gaps.
- Prove it, then keep it up all year.
Read more: The yearly compliance cycle
Read the boxes from left to right. First find every place card data lives (scope), compare it against the 12 requirements, and fix the gaps. Then prove it with a ROC or SAQ, and send the signed AOC to your bank. Step 6 is the one teams forget: keep monitoring all year. The dashed line shows the loop starts again every year, and whenever your systems change.
The smartest move: shrink your scope
The cheapest way to comply is to touch less card data.
- Use tokens instead of card numbers.
- Use your provider’s hosted payment page.
- Wall off card systems from the rest, and never store the CVV.
Read more: The smartest move: shrink your scope
Every system that touches card data is “in scope” and must meet all the rules. So the cheapest way to comply is to touch less card data:
- Use tokens. Replace card numbers with tokens so your systems never see the real number.
- Use your provider’s hosted payment page or form. The card details go straight to the payment provider, not through your servers.
- Use certified point-to-point encrypted (P2PE) terminals in stores.
- Separate your networks, so card systems are walled off from everything else.
- Never store the security code (CVV) after a payment is approved. This is not allowed, even if it’s encrypted.
What v4.0.1 asks for now
A few newer rules catch many teams out.
- Multi-factor login into the card data environment.
- Passwords of at least 12 characters.
- A list of every script on payment pages, and automated log reviews.
Read more: What v4.0.1 asks for now
A few requirements that became mandatory in March 2025 catch many teams out:
- Multi-factor login for all access into the card data environment, not just remote access.
- Longer passwords: at least 12 characters.
- Payment page scripts: keep a list of every script on your checkout page, approve each one, and detect tampering.
- Automated log reviews, instead of people reading logs by hand.
- Targeted risk analysis to justify how often you do certain checks.
My take
PCI DSS isn’t a certificate on the wall. It’s a promise to your customers and your bank that card data is safe every day. Keep your scope small, build the rules into how you work, and prove it once a year.
Read Part 2: PCI DSS in practice. What really happens in an audit, how to measure true and false findings, what it means for software teams, and why it matters to customers.
Working on a payments project?
I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.
Connect on LinkedInSee how I can help