,

PCI DSS Compliance: Requirements, Levels, and How Validation Works (v4.0.1)

PCI DSS compliance means meeting the Payment Card Industry Data Security Standard: 12 security requirements for any organization that stores, processes, or transmits payment card data, or that can affect its security.

  • Version: the current version is PCI DSS v4.0.1. All of its requirements have been mandatory since March 31, 2025.
  • Enforcement: the card brands and acquiring banks enforce compliance, not the PCI Security Standards Council.
  • Validation: organizations prove compliance through an annual self-assessment questionnaire (SAQ) or an on-site assessment by a Qualified Security Assessor (QSA), depending on their merchant or service provider level.

Current status: October 2026

Version PCI DSS v4.0.1 (June 2024) is the only active version. v4.0 retired on December 31, 2024.
In force All 51 formerly future-dated requirements, mandatory since March 31, 2025.
Coming The PCI SSC has begun work on the next iteration of the standard. We’ll update this page when a new version is published.

Track PCI DSS updates

What is PCI DSS?

PCI DSS is a security standard published by the PCI Security Standards Council (PCI SSC). The major card brands formed the Council to set one baseline for protecting cardholder data. It covers network security, data protection, access control, monitoring, testing, and security policy.

PCI DSS is a contractual standard, not a law. It applies through the agreements merchants and service providers sign with their acquiring banks and the card brands. For a deeper introduction, see what PCI DSS is.

The 12 PCI DSS requirements

Goal Requirements
Build and maintain a secure network and systems 1. Install and maintain network security controls
2. Apply secure configurations to all system components
Protect account data 3. Protect stored account data
4. Protect cardholder data with strong cryptography during transmission over open, public networks
Maintain a vulnerability management program 5. Protect all systems and networks from malicious software
6. Develop and maintain secure systems and software
Implement strong access control measures 7. Restrict access to system components and cardholder data by business need to know
8. Identify users and authenticate access to system components
9. Restrict physical access to cardholder data
Regularly monitor and test networks 10. Log and monitor all access to system components and cardholder data
11. Test security of systems and networks regularly
Maintain an information security policy 12. Support information security with organizational policies and programs

Each requirement breaks down into detailed sub-requirements and testing procedures. See PCI DSS requirements explained.

What data does PCI DSS protect?

PCI DSS protects account data, in two categories:

  • Cardholder data: the primary account number (PAN), plus the cardholder name, expiration date, and service code when stored with the PAN.
  • Sensitive authentication data: full magnetic-stripe or chip data, card verification codes (CVV2, CVC2, CID), and PINs or PIN blocks. Sensitive authentication data must not be stored after authorization, even if it’s encrypted.

The PAN is what brings systems into scope. Any system that stores, processes, or transmits it is part of the cardholder data environment (CDE). So is any system connected to the CDE or able to affect its security.

Who needs to comply with PCI DSS?

  • Merchants that accept payment cards, whether online, in person, or by phone, regardless of size.
  • Service providers that store, process, or transmit cardholder data on behalf of others, or that can affect the security of that data. Examples include payment processors, payment gateways, hosting and cloud providers, and managed security providers.

Outsourcing payments doesn’t remove the obligation. A merchant using a compliant payment processor still has to validate its own compliance, though its scope and SAQ may be much smaller. See who needs PCI DSS.

Who enforces PCI DSS?

The PCI Security Standards Council writes and maintains the standard, but it doesn’t enforce it. Enforcement runs through the payment chain:

  • Card brands (Visa, Mastercard, American Express, Discover, JCB) each run their own compliance programs. They set merchant levels and validation requirements, and they can fine acquiring banks.
  • Acquiring banks (acquirers) contract with merchants. They require proof of compliance, typically pass card brand fines on to the merchant, and can raise fees or end the relationship.
  • Merchants and service providers validate compliance and submit the results to their acquirer or to the card brands.

Is PCI DSS a law? No. It’s a contractual requirement. Some U.S. states reference PCI DSS in data security laws, and failing to protect card data can still trigger breach-notification laws and regulatory action.

PCI compliance levels

Card brands sort merchants into levels by annual transaction volume, and the level determines how compliance must be validated. Thresholds vary by brand. Visa’s merchant levels are the most widely referenced:

Merchant level Annual Visa transactions (all channels unless noted) Typical validation
Level 1 More than 6 million, or any merchant that’s had a breach Annual Report on Compliance (ROC) by a QSA (or an internal auditor, where allowed), quarterly ASV scans, and an AOC
Level 2 1 million to 6 million Annual SAQ (some brands require a ROC), quarterly ASV scans, and an AOC
Level 3 20,000 to 1 million e-commerce transactions Annual SAQ, quarterly ASV scans, and an AOC
Level 4 Fewer than 20,000 e-commerce, or up to 1 million total Annual SAQ and quarterly ASV scans, as required by the acquirer

Service providers have their own levels. Level 1 service providers, generally those handling more than 300,000 transactions a year, need an annual ROC from a QSA. Your acquirer and the card brands have the final word on your level.

How PCI DSS validation works

Every organization in scope validates compliance once a year. The core documents are:

  • Report on Compliance (ROC): a detailed assessment by a QSA, or by an Internal Security Assessor (ISA) where the brands allow it.
  • Self-Assessment Questionnaire (SAQ): a self-assessment. The SAQ type depends on how you accept payments. For example, SAQ A covers fully outsourced e-commerce, and SAQ D covers merchants that store card data and all service providers.
  • Attestation of Compliance (AOC): the signed declaration of compliance that goes to your acquirer or customers, alongside the ROC or SAQ.
  • ASV scan reports: quarterly external vulnerability scans by a PCI SSC-approved scanning vendor, required for most organizations with internet-facing systems in scope.

PCI DSS also requires quarterly internal vulnerability scans, annual penetration testing (with segmentation testing if you rely on segmentation), and ongoing monitoring between assessments. See how PCI DSS assessment works.

What changed in PCI DSS v4.0 and v4.0.1

PCI DSS v4.0 (March 2022) was the first major revision in more than a decade. It added 64 new requirements, 51 of which were future-dated until March 31, 2025. v4.0.1 (June 2024) corrected and clarified the text without adding or removing requirements. Some of the most significant changes:

  • MFA for all access into the CDE, not just remote and administrative access (8.4.2).
  • Stronger passwords: a minimum of 12 characters where systems support it (8.3.6).
  • Payment page script controls: an inventory and authorization of scripts on payment pages (6.4.3), plus change and tamper detection (11.6.1). Some SAQ A merchants now meet an eligibility criterion instead.
  • Authenticated internal vulnerability scans (11.3.1.2).
  • Anti-phishing mechanisms (5.4.1).
  • Targeted risk analyses that let organizations set the frequency of some activities themselves.
  • The customized approach: a new option to meet a requirement’s objective with controls other than the defined approach. It’s validated by a QSA.

See PCI DSS updates.

How to reduce your PCI DSS scope

  • Don’t store card data you don’t need. Never store sensitive authentication data after authorization.
  • Tokenization: replace PANs with tokens so systems don’t handle real card numbers.
  • Point-to-point encryption (P2PE): use a validated P2PE solution for card-present payments.
  • Outsourced payment pages: use iframes or redirects to a compliant provider for e-commerce.
  • Network segmentation: isolate the CDE from the rest of the network, and test that the segmentation works.

Using a compliant provider like a major payment processor reduces scope, but it doesn’t make you compliant. You’re still responsible for your own environment and your SAQ.

What happens if you’re not PCI compliant?

  • Fines: card brands can fine acquirers, who typically pass the fines on. Amounts aren’t published by the PCI SSC and vary by brand and circumstance.
  • Higher fees or termination: an acquirer can raise transaction fees or stop processing your card payments.
  • Breach costs: forensic investigation, card reissuance, fraud losses, and legal exposure, plus mandatory Level 1 validation afterward.
  • Lost customers and contracts: many B2B customers require a current AOC before they’ll work with a service provider.

See why PCI DSS matters.

How to achieve PCI DSS compliance

  1. Identify your obligations: your merchant or service provider level, your SAQ type, and what your acquirer requires.
  2. Define and reduce scope: map every place card data flows, then shrink the CDE.
  3. Run a gap assessment against all applicable v4.0.1 requirements.
  4. Remediate, prioritizing the controls that protect stored data and access to the CDE.
  5. Engage an ASV for quarterly external scans, and schedule penetration testing.
  6. Validate: complete your SAQ, or schedule your ROC with a QSA, and submit your AOC.
  7. Maintain: monitor continuously. PCI DSS v4.x expects compliance to be ongoing, not annual.

See how to prepare for PCI DSS and PCI DSS cost and timeline.

Frequently asked questions

Is PCI compliance required by law?
PCI DSS is not a federal law. It is a contractual requirement that card brands and acquiring banks impose on merchants and service providers that accept or handle payment cards. Some U.S. states reference PCI DSS in their data security laws, and failing to protect card data can trigger breach-notification and other legal obligations.
What is the current version of PCI DSS?
PCI DSS v4.0.1, published in June 2024, is the only active version. PCI DSS v4.0 was retired on December 31, 2024, and the 51 requirements that v4.0 introduced as future-dated became mandatory on March 31, 2025. Version 4.0.1 clarified the standard without adding or removing requirements.
Who enforces PCI compliance?
The card brands and acquiring banks enforce PCI DSS, not the PCI Security Standards Council. Card brands set validation requirements and can fine acquirers, which typically pass fines and fees on to merchants. Acquirers require proof of compliance and can raise fees or stop processing card payments for non-compliant merchants.
What are the PCI compliance levels?
Card brands assign merchant levels 1 through 4 based on annual transaction volume. Under Visa’s program, Level 1 is more than 6 million transactions a year and requires an annual Report on Compliance from a Qualified Security Assessor. Levels 2 through 4 generally validate with a Self-Assessment Questionnaire. Service providers have separate levels.
What is the difference between a ROC and an SAQ?
A Report on Compliance (ROC) is a detailed assessment performed by a Qualified Security Assessor, or an approved internal assessor, and is required for Level 1 merchants and service providers. A Self-Assessment Questionnaire (SAQ) is completed by the organization itself. Both are accompanied by a signed Attestation of Compliance (AOC).
Does using a payment processor like Stripe make you PCI compliant?
No. A PCI-compliant payment processor reduces your scope, often enough to qualify for a shorter self-assessment questionnaire, but it doesn’t make your business compliant. You remain responsible for your own systems, website, and processes, and you must still validate compliance each year.
How often do you need to validate PCI DSS compliance?
Compliance is validated annually through a Report on Compliance or Self-Assessment Questionnaire with an Attestation of Compliance. Quarterly external vulnerability scans by an Approved Scanning Vendor, quarterly internal scans, and annual penetration testing are also required for most organizations, and PCI DSS v4.x expects controls to operate continuously.

Explore the PCI DSS resource hub

Work with RSI Security

RSI Security is a PCI Qualified Security Assessor (QSA) company, an Approved Scanning Vendor (ASV), and a PCI Software Security Framework Assessor Company.

  • Assessments: we perform PCI DSS assessments (ROC and AOC) and quarterly ASV scans.
  • Readiness: organizations that need readiness support can work with RSI Security through a separate advisory engagement.
  • Independence: RSI Security provides either advisory or assessment to a given client, never both.

Schedule a PCI DSS assessment · Get quarterly ASV scans · Talk to an advisor about readiness