PCI compliance means following the Payment Card Industry Data Security Standard (PCI DSS), the security rulebook that every business storing, processing, or transmitting credit card data has to meet. The current version is v4.0.1, and every requirement in it has been fully enforceable since March 31, 2025. What compliance actually looks like for your business depends on how many card transactions you handle each year: smaller merchants fill out a self-assessment questionnaire, while the largest pay for an annual on-site audit by a certified assessor. Falling short can cost you monthly fines, your ability to accept cards at all, and serious legal exposure if customer data is stolen.
Who Has to Comply
Any business that accepts credit cards is subject to PCI DSS. The standard was first published in 2004 by Visa, Mastercard, American Express, Discover, and JCB International, and is now maintained by the PCI Security Standards Council. The council writes the rules but doesn’t enforce them; each card brand runs its own compliance program and leans on acquiring banks to police the merchants they serve.
Card brands sort merchants into four levels based on annual transaction volume, and the level sets how much validation work you owe each year. Visa’s thresholds are the most commonly referenced, and the other brands line up closely:
- Level 1: more than 6 million transactions a year. Annual on-site assessment by a Qualified Security Assessor (QSA), quarterly network scans by an Approved Scanning Vendor (ASV), and an Attestation of Compliance.
- Level 2: 1 million to 6 million transactions a year. Annual Self-Assessment Questionnaire (SAQ), quarterly ASV scans, and an Attestation of Compliance.
- Level 3: 20,000 to 1 million e-commerce transactions a year. Same validation requirements as Level 2.
- Level 4: fewer than 20,000 e-commerce transactions or up to 1 million total transactions a year. The acquiring bank sets the validation requirements, though an annual SAQ and quarterly scans are recommended.
Levels are set per card brand, not combined. A business processing 5 million Visa transactions and 2 million Mastercard transactions is Level 1 with both brands, not Level 2 with either.1Visa. Security and Compliance2Mastercard. Site Data Protection (SDP) Program A merchant that suffers a data breach can also be escalated to a higher level regardless of volume.3Visa. Validation of Compliance
Service providers (companies that handle cardholder data on behalf of merchants) have their own two-tier structure. Under Visa and Mastercard programs, Level 1 service providers handle more than 300,000 transactions a year and must complete an annual QSA audit; Level 2 handle 300,000 or fewer and can typically self-assess using the SAQ D form, unless their bank or a card brand demands a full audit.4Mastercard. Service Provider Categories and PCI
The Twelve Security Requirements
PCI DSS organizes its rules into twelve requirements grouped under six broad goals. Every merchant and service provider has to meet all of them, regardless of level. The difference between levels is how you prove it, not what you have to do.
- Requirement 1 — Install and maintain network security controls (firewalls or equivalent) around the systems where cardholder data lives.
- Requirement 2 — Change every vendor-default password and setting before putting a system into production.
- Requirement 3 — Minimize what you store. Any cardholder data you do keep has to be encrypted, with tight control over who can access the keys.
- Requirement 4 — Use strong cryptography whenever cardholder data crosses an open or public network.
- Requirement 5 — Run and keep current anti-malware software on all systems susceptible to malicious code.
- Requirement 6 — Follow secure coding practices for custom applications, and install critical security patches within 30 days of release.5PCI Security Standards Council. Just Published: PCI DSS v4.0.1
- Requirement 7 — Limit access to cardholder data to people whose jobs require it.
- Requirement 8 — Give every user a unique ID. Shared accounts are not acceptable.
- Requirement 9 — Physically secure servers, network equipment, and any location where cardholder data is handled.
- Requirement 10 — Log access to systems and cardholder data, and review the logs regularly.
- Requirement 11 — Run quarterly ASV vulnerability scans and perform internal and external penetration tests at least once a year.6PCI Security Standards Council. Resource Guide: Vulnerability Scans and Approved Scanning Vendors
- Requirement 12 — Maintain a written information security policy covering all PCI DSS requirements, review it annually, and train everyone who touches cardholder data.
Requirements 3 and 6 cause most of the remediation work in practice, because they force businesses to confront what they actually store and how fast they can patch across their environment.
How You Prove You’re Compliant
Merchants at Levels 2 through 4 validate by completing a Self-Assessment Questionnaire tailored to their payment setup. Picking the wrong one can invalidate your submission. The main choices:
- SAQ A: card-not-present merchants who have fully outsourced all payment functions to a validated third party. No electronic cardholder data touches your systems.7PCI Security Standards Council. PCI DSS v4.0 SAQ A
- SAQ A-EP: e-commerce merchants who outsource processing but whose own website affects the security of the transaction.
- SAQ B and B-IP: merchants using only imprint machines, standalone dial-out terminals, or PTS-approved IP-connected terminals, with no electronic storage.
- SAQ C and C-VT: merchants with internet-connected payment applications, or those keying in transactions one at a time through a hosted virtual terminal.
- SAQ P2PE: merchants using a PCI-validated point-to-point encryption solution, with no electronic cardholder data storage.
- SAQ D: the catch-all for everyone else, and the form all service providers that self-assess must use. It’s the longest.
Alongside the SAQ you file an Attestation of Compliance, a formal declaration signed by a QSA or an authorized company officer.8PCI Security Standards Council. Attestation of Compliance – Merchants Quarterly ASV scan reports go with it. Everything is submitted to your acquiring bank, usually through a portal the bank provides.
Level 1 merchants and Level 1 service providers can’t self-assess. They have to hire a Qualified Security Assessor, an independent firm certified by the PCI Security Standards Council, to run an on-site audit and produce a Report on Compliance.9PCI Security Standards Council. Qualified Security Assessors Some organizations train staff as Internal Security Assessors to supplement a QSA engagement; an ISA cannot replace a QSA at Level 1, but having one on staff cuts the external billable hours.
Costs scale sharply. A straightforward Level 1 QSA audit typically runs $45,000 to $75,000, and a full-scope engagement for a multi-location enterprise can exceed $250,000. Those numbers cover the assessor only; fixing whatever the audit finds is on top. A small merchant filling out an SAQ may spend only a few hundred dollars on the questionnaire, scans, and basic training in a year, assuming nothing significant needs remediation.
What Changed in Version 4.0
Version 3.2.1 was retired on March 31, 2024.10PCI Security Standards Council. PCI DSS v3.2.1 Is Retiring on 31 March 2024 – Are You Ready? Version 4.0 took its place, with a minor clarifying revision (v4.0.1) published in June 2024.5PCI Security Standards Council. Just Published: PCI DSS v4.0.1 Several v4.0 requirements were labeled best practices until March 31, 2025, and are now fully mandatory. If your program still references v3.2.1, it needs an immediate overhaul. The changes most likely to require work:
- Minimum password length rose from 7 characters to 12, or 8 if a system cannot support 12.11PCI Security Standards Council. Summary of Changes from PCI DSS Version 3.2.1 to 4.0
- Multi-factor authentication is now required for everyone accessing the cardholder data environment, not just remote administrators. Someone with both console and remote access needs MFA for each separately.
- E-commerce merchants have to authorize and monitor every script running on their payment pages and deploy a tamper-detection mechanism, aimed at digital skimming attacks that inject malicious code into checkout pages.12PCI Security Standards Council. Securing Different Types of Payment Pages from E-commerce Skimming Attacks
- Several controls now let you set their frequency based on a documented targeted risk analysis instead of a fixed schedule. The flexibility comes with real documentation work: you have to justify your chosen frequency and update the analysis whenever your environment changes.13PCI Security Standards Council. Just Published: PCI DSS v4.x Targeted Risk Analysis Guidance
Version 4.0 also introduced a “customized approach” that lets businesses meet a requirement’s objective through alternative controls. It requires a targeted risk analysis for each customized requirement and substantially more audit documentation, so most small and mid-sized merchants will stay with the defined approach.
Shrinking What’s In Scope
The more systems that touch cardholder data, the more requirements apply and the more expensive compliance becomes. Two technologies exist specifically to shrink that footprint.
Tokenization replaces real card numbers with substitute values that have no exploitable meaning if stolen. Systems that only store and process tokens can fall outside the cardholder data environment, meaning fewer systems to assess and fewer controls to maintain.14PCI Security Standards Council. PCI DSS Tokenization Guidelines The tokenization system itself, including the vault and keys, stays fully in scope. The scope reduction only works where there is genuine segmentation between token-only systems and the tokenization engine.
A PCI-validated point-to-point encryption (P2PE) solution encrypts card data at the point of interaction using keys the merchant never controls. Because you can’t decrypt what moves through your network, everything between the card reader and the solution provider’s decryption environment drops out of your PCI DSS scope.15PCI Security Standards Council. Assessor Viewpoint: On PCI Point-to-Point Encryption (P2PE) Solutions Merchants using a validated P2PE solution can complete the much shorter SAQ P2PE instead of a full SAQ D. For brick-and-mortar retailers, P2PE is often the single most effective step for cutting compliance costs.
What Non-Compliance Costs
Penalties flow through a chain. Card brands fine the acquiring bank, and the bank passes the fine on to the merchant through the processing agreement. Monthly fines for sustained non-compliance are commonly reported in the range of $5,000 to $100,000, escalating the longer the violations continue. Exact amounts are set by individual card brand programs and are not publicly standardized; what you’d actually owe depends on which brands you accept and how serious the problem is.
Fines are often the smaller problem. Acquiring banks can raise your per-transaction fees to offset the risk, restrict your processing privileges, or close your merchant account entirely. For a business where card payments are most of revenue, losing processing capability is usually worse than any fine.
If an account is terminated for security violations, the business can be added to the MATCH database (Mastercard Alert to Control High-Risk Merchants), which is shared across processors. Records stay on MATCH for five years, and most processors will decline applications from listed businesses during that period. Being listed effectively locks a business out of card processing for years.
Legal Exposure If There’s a Breach
Card brand fines are the start of the damage from a breach. The Federal Trade Commission treats failure to maintain reasonable data security as an unfair business practice under Section 5 of the FTC Act and brings enforcement actions against companies whose security falls short.16Federal Trade Commission. Policy Statement on Section 5 of the FTC Act Regarding Unfair or Deceptive Acts or Practices in Connection with Information Security FTC orders typically require comprehensive security programs and independent third-party assessments for years afterward, and the commission can also seek monetary relief, including consumer redress.
Class action lawsuits add another layer. Courts have increasingly let breach-related claims proceed, and settlements can be large: the Equifax breach settlement included up to $425 million in compensation for 147 million affected individuals.17Federal Trade Commission. Equifax Data Breach Settlement Most merchant breaches are far smaller, but legal defense alone can dwarf the card brand fines.
State attorneys general can also bring actions under state breach and consumer protection laws, and nearly every state has a breach notification statute requiring affected individuals to be told. These obligations are separate from and in addition to card brand requirements.
What Happens After a Breach
If you discover a breach involving cardholder data, the clock starts immediately. Card brand rules generally require notice to your acquiring bank or payment processor within 24 hours of discovering the compromise. The brands will typically require a forensic investigation by a PCI Forensic Investigator, a third-party firm certified by the Council, to examine how the breach happened, what data was exposed, and whether you were compliant at the time.
These investigations commonly cost $10,000 to $50,000 for smaller merchants, and more for complex environments. The merchant pays regardless of the outcome. If the report shows you were non-compliant when the breach happened, the brands will impose additional penalties and may require a full QSA reassessment before you can resume processing. Businesses that were demonstrably compliant at the time face far lighter consequences, which is the strongest practical argument for treating PCI compliance as a year-round program rather than an annual checkbox exercise.