Skip to content

PCI DSS Compliance Guide (v4.0.1): Requirements, Levels, SAQs, Testing and Costs

PCI DSS v4.0.1 explained from PCI SSC, Visa and Mastercard sources: the 12 requirements, March 2025 changes, levels, SAQs, ASV scans, pentests and fines.

Wahid IqbalBy , Head of Compliance19 min read

Network Penetration Testing ServicesExternal from $4,200, internal from $6,000Fixed scope, free retest, no hourly billing.

Get my fixed price

This guide covers what PCI DSS v4.0.1 requires and how compliance is proven: the 12 requirements, the changes mandatory since March 31, 2025, merchant and service provider levels, SAQ types, ROC vs SAQ, ASV scans, penetration and segmentation testing, and what non-compliance costs. It is built from PCI Security Standards Council documents, Visa’s and Mastercard’s compliance program pages, Visa’s published rules and state attorney general announcements.

How to cite: link to this page or to the primary source beside each figure. Requirement numbers come from PCI DSS v4.0.1 (June 2024).

Key points at a glance

1. What PCI DSS is and who must comply

PCI DSS (the Payment Card Industry Data Security Standard) is a baseline of technical and operational requirements for protecting payment account data. It is published by the PCI Security Standards Council, which was founded in 2006 by American Express, Discover, JCB International, Mastercard and Visa.

The standard applies to every entity that stores, processes or transmits cardholder data or sensitive authentication data, or that could affect its security. That covers merchants, processors, acquirers, issuers and other service providers (PCI DSS v4.0.1, Section 2). Cardholder data is the primary account number (PAN) and the name, expiry date and service code stored with it; sensitive authentication data is track data, card verification codes and PINs.

Three points matter most:

  • It is enforced by contract, not by a government regulator. The Council writes the standard; the card brands and acquiring banks enforce it. Visa says the Council “owns, maintains and manages” PCI DSS while Visa manages compliance enforcement and validation (Visa AIS Program page).
  • Outsourcing does not remove responsibility. Entities that outsource payment operations “remain responsible” for making sure the third party protects the data (PCI DSS v4.0.1, Section 2).
  • Compliance and validation are different things. Every merchant must comply. How you prove it is set by the brands and your acquirer (sections 4 and 5).

2. The 12 PCI DSS requirements, summarized

The titles below are the Council’s own, from Table 1 of PCI DSS v4.0.1. For an item-by-item version, use our PCI DSS compliance checklist.

# Requirement What it means in practice
1 Install and Maintain Network Security Controls Traffic into the cardholder data environment (CDE) limited to what is necessary (1.3.1); rulesets reviewed every six months (1.2.7).
2 Apply Secure Configurations to All System Components Hardening standards for every system component (2.2.1).
3 Protect Stored Account Data No sensitive authentication data after authorization, even encrypted (3.3.1); stored PAN unreadable (3.5.1).
4 Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks Strong cryptography and valid, trusted certificates for PAN in transit (4.2.1).
5 Protect All Systems and Networks from Malicious Software Anti-malware on at-risk systems, plus automated anti-phishing mechanisms (5.4.1).
6 Develop and Maintain Secure Systems and Software Risk-ranked vulnerabilities (6.3.1), critical patches within one month (6.3.3), automated protection for public web apps (6.4.2), payment page script control (6.4.3).
7 Restrict Access to System Components and Cardholder Data by Business Need to Know Least-privilege access model (7.2.1); user accounts reviewed at least every six months (7.2.4).
8 Identify Users and Authenticate Access to System Components Unique IDs, inactive accounts disabled within 90 days (8.2.6), 12-character passwords (8.3.6), MFA for all non-console access into the CDE (8.4.2).
9 Restrict Physical Access to Cardholder Data Facility entry controls, media handling and destruction (9.4), card reader tamper inspections (9.5).
10 Log and Monitor All Access to System Components and Cardholder Data Daily log review (10.4.1), automated (10.4.1.1); logs kept 12 months, three immediately available (10.5.1).
11 Test Security of Systems and Networks Regularly Quarterly wireless checks (11.2.1), quarterly internal and ASV scans (11.3), annual penetration tests (11.4), intrusion detection (11.5.1), payment page tamper detection (11.6.1).
12 Support Information Security with Organizational Policies and Programs Annual policy review (12.1.2), targeted risk analyses (12.3.1), annual scope confirmation (12.5.2), awareness training (12.6), service provider oversight (12.8), annual incident response test (12.10.2).

3. PCI DSS v4.0.1 and the requirements mandatory since March 31, 2025

The Council published v4.0.1 on June 11, 2024, as a limited revision with “no additional or deleted requirements”; v4.0 was retired on December 31, 2024 (PCI SSC blog, June 2024). In v4.0.1, the one-month patch deadline (6.3.3) applies to critical vulnerabilities; other patches follow the entity’s own risk-based time frame.

Of the 64 new requirements introduced in v4.x, 51 were future-dated, labeled “best practice until March 31, 2025,” and are now mandatory (PCI SSC blog, August 2024). Among them:

Requirement What became mandatory on March 31, 2025
5.4.1 Automated mechanisms detect and protect staff against phishing.
6.4.2 An automated technical solution (for example, a web application firewall) in front of public-facing web applications. It replaces Requirement 6.4.1, which also allowed periodic application reviews instead.
6.4.3 Every script on payment pages is authorized, integrity-checked and inventoried with a justification.
8.3.6 Passwords of at least 12 characters (eight if the system cannot support 12).
8.4.2 MFA for all non-console access into the CDE, not only administrator access (which 8.4.1 already covered).
10.4.1.1 Automated mechanisms for audit log review.
11.3.1.2 Internal vulnerability scans are authenticated.
11.6.1 A change- and tamper-detection mechanism checks payment pages and their HTTP headers at least weekly (or at a risk-based frequency).
12.3.1 A documented targeted risk analysis for each requirement that calls for one, such as those where you set your own frequency.
12.5.2.1 Service providers confirm PCI DSS scope every six months.
12.6.3.1 Awareness training covers phishing and social engineering.

Source for every row: the applicability notes on each requirement in PCI DSS v4.0.1.

Requirements 6.4.3 and 11.6.1 target e-commerce skimming. On January 30, 2025, the Council removed them, with 12.3.1, from SAQ A and added an eligibility criterion instead: the merchant must confirm its site “is not susceptible to attacks from scripts” that could affect its e-commerce systems (PCI SSC blog, January 2025). The requirements themselves stay in PCI DSS. FAQ 1588 added that merchants can meet the criterion with 6.4.3 and 11.6.1 techniques or with confirmation from their PCI DSS compliant payment provider, and that it applies only to sites embedding a provider’s payment form (such as an iframe), not to redirects (PCI SSC blog, February 2025). Our e-commerce penetration testing guide covers how this is tested.

See what a real pentest finds. Read our sample report, then get a fixed quote in writing.

4. Merchant and service provider levels

Levels are set by each card brand, not by PCI DSS, and decide how you validate. Our PCI compliance levels guide adds American Express and Discover and explains edge cases.

Merchant levels

Level Visa Mastercard Minimum validation
1 Over 6 million Visa transactions a year, or a global merchant any Visa region rates Level 1 More than 6 million Mastercard and Maestro transactions a year, Visa Level 1 merchants, or as Mastercard designates Annual Report on Compliance (ROC) and Attestation of Compliance (AOC)
2 1 million to 6 million Visa transactions a year More than 1 million and up to 6 million Annual SAQ. Mastercard Level 2 merchants completing SAQ A, A-EP or D must also engage a QSA or ISA
3 Fewer than 1 million Visa e-commerce transactions a year (Visa’s wording) More than 20,000 and up to 1 million e-commerce transactions Annual SAQ
4 No longer a separate Visa level All other merchants Mastercard: must comply, but validation to Mastercard is not required unless law requires it

Sources: Visa AIS Program page; Mastercard SDP page. Visa merged Levels 3 and 4 effective April 25, 2024, with no change to compliance requirements (Visa WTDIC v10.0, 2026). Mastercard sets levels on volume from the most recent 52-week period.

Service provider levels

  • Visa Level 1: VisaNet processors, or any service provider handling over 300,000 Visa transactions a year. Annual on-site assessment with an AOC signed by the service provider and a QSA. Level 2: fewer than 300,000; SAQ D or an AOC with QSA signature. (Visa AIS Program page).
  • Mastercard Level 1: all third-party processors, merchant payment gateways, token and 3-D Secure providers and several other types, plus data storage entities, payment facilitators and AML/sanctions providers above 300,000 combined Mastercard and Maestro transactions a year; annual ROC. Level 2: those at 300,000 or fewer, and terminal servicers; annual SAQ (Mastercard SDP page).

Visa’s Technology Innovation Program can remove the annual validation requirement for eligible merchants when at least 75% of transactions come through EMV chip terminals, a validated P2PE solution or EMVCo tokenization (Visa AIS Program page). Compliance itself is still required.

5. SAQ types, and ROC vs SAQ

A Self-Assessment Questionnaire (SAQ) is a self-assessment against only the requirements that apply to one way of taking payments. The Council’s SAQ Instructions and Guidelines v4.0 (2023) define these types:

SAQ Who it is for
A Card-not-present merchants that fully outsource account data functions (redirect or embedded payment form)
A-EP E-commerce merchants whose site does not receive card data but affects the payment page (direct post, merchant-delivered JavaScript)
B Imprint machines or standalone dial-out terminals only, no electronic storage
B-IP Standalone PCI-approved PTS terminals with an IP connection to the processor, no electronic storage
C-VT Manual entry, one transaction at a time, into a third-party virtual terminal on an isolated device
C Payment application systems connected to the internet, no electronic storage
P2PE Only hardware terminals in a validated, PCI-listed P2PE solution
SPoC A phone or tablet with a secure card reader from a validated SPoC solution (new in v4.0)
D for Merchants Every merchant not covered by the types above
D for Service Providers Service providers that a payment brand allows to self-assess

A Report on Compliance (ROC) is a formal assessment of every applicable requirement on the Council’s template, by a Qualified Security Assessor (QSA) or, where the brand allows, an Internal Security Assessor (ISA). Both end in a signed Attestation of Compliance (AOC) (PCI DSS v4.0.1, Sections 11 and 12).

A ROC is required at Level 1 for merchants and service providers; SAQs are allowed below that. Only a ROC can use the customized approach (meeting a requirement’s objective with a different control); SAQ filers are not eligible (PCI DSS v4.0.1, Appendix D). In August 2026 the Council also revised FAQ 1331 to say merchants should always confirm validation and reporting requirements with their “Compliance Accepting Entities,” meaning the acquirer or brand (PCI SSC bulletin, 2026). What each path costs is broken down in PCI compliance cost: SAQ A to ROC.

6. ASV scans vs penetration testing (Requirements 11.3 and 11.4)

Scanning and penetration testing meet different requirements. The standard says a penetration test “differs from a vulnerability scan” because it is an active process that usually includes exploiting vulnerabilities (PCI DSS v4.0.1, 11.4.1 guidance).

Internal scan (11.3.1) ASV scan (11.3.2) Penetration test (11.4)
Frequency Every three months and after significant change Every three months and after significant change Every 12 months and after significant change
Who Qualified, independent personnel A PCI SSC Approved Scanning Vendor Qualified, organizationally independent internal or external tester; need not be a QSA or ASV
Pass condition High-risk and critical findings resolved and rescanned; authenticated since March 31, 2025 (11.3.1.2) Passing scan under the ASV Program Guide Exploitable findings corrected per risk and the test repeated to verify (11.4.4)
Scope Internal network Internet-facing systems Entire CDE perimeter and critical systems, from inside and outside, application and network layers, plus segmentation controls (11.4.1)

Source: Requirements 11.3.1, 11.3.1.2, 11.3.1.3, 11.3.2, 11.3.2.1 and 11.4.1 to 11.4.4 of PCI DSS v4.0.1.

A first-time assessment does not need four passing ASV scans if the latest one passed and quarterly scanning is documented (11.3.2). Pentest results and remediation records must be kept for at least 12 months (11.4.1). The guidance to 11.4.3 adds that a test that found nothing is “typically indicative of shortcomings of the penetration tester.”

For the full comparison see ASV scan vs penetration test, for the line-by-line requirement see PCI DSS penetration testing requirements, and for budgets see PCI penetration testing cost.

7. Segmentation testing

Segmentation, isolating the CDE from the rest of the network, “is not a PCI DSS requirement,” but without it the entire network is in scope (PCI DSS v4.0.1, Section 4). If you use it to shrink scope, you must prove it works:

  • Merchants: penetration tests on segmentation controls at least once every 12 months and after any change to segmentation controls or methods (11.4.5, PCI DSS v4.0.1).
  • Service providers: at least once every six months and after any change (11.4.6, PCI DSS v4.0.1).
  • Coverage: every segmentation method, confirming it isolates the CDE from all out-of-scope systems.

Regulators have required it too: Target’s $18.5 million settlement with 47 states and the District of Columbia, over a breach of more than 41 million payment card accounts, required it to segment its cardholder data environment (Connecticut Attorney General, 2017). We run these tests as a standalone network segmentation testing service.

8. PCI DSS timeline and recurring calendar

The version timeline: v4.0 published March 2022 (PCI DSS v4.0.1, Table 6), v3.2.1 retired March 31, 2024 (PCI SSC blog, 2024), v4.0.1 published June 11, 2024, v4.0 retired December 31, 2024, and the future-dated requirements and revised SAQ A in force from March 31, 2025. From then on, compliance runs on a fixed calendar.

Recurring compliance calendar

  • Daily: security log review (10.4.1, PCI DSS v4.0.1).
  • Weekly: payment page tamper detection, unless a targeted risk analysis sets another frequency (11.6.1, PCI DSS v4.0.1).
  • Every three months: internal and ASV scans (11.3), wireless access point checks (11.2.1); for service providers, reviews that staff follow security procedures (12.4.2, PCI DSS v4.0.1).
  • Every six months: firewall ruleset reviews (1.2.7), user access reviews (7.2.4); for service providers, segmentation tests (11.4.6) and scope confirmation (12.5.2.1, PCI DSS v4.0.1).
  • Every 12 months: penetration tests (11.4.2, 11.4.3), merchant segmentation tests (11.4.5), scope confirmation (12.5.2), policy review (12.1.2), awareness training (12.6.3), incident response test (12.10.2), service provider compliance monitoring (12.8.4), and the ROC or SAQ itself (PCI DSS v4.0.1).

How these map against other frameworks is in how often should you do a penetration test.

9. Common compliance failures

  1. Scope drawn too small. 12.5.2 requires mapping every data flow and channel yearly, and Visa’s list of validation errors starts with unassessed payment channels (Visa PCI DSS Validation Best Practice Review, 2018).
  2. Incomplete paperwork. The same Visa review lists missing descriptions, unchecked boxes and missing signatures and dates on the AOC.
  3. Wrong SAQ. Using SAQ A when the merchant’s own scripts affect the payment page (an SAQ A-EP case), or ignoring the 2025 script-attack criterion.
  4. Scans treated as a penetration test. Quarterly ASV reports do not satisfy 11.4 (PCI DSS v4.0.1).
  5. Untested segmentation used to claim systems are out of scope (11.4.5, 11.4.6, PCI DSS v4.0.1).
  6. Unauthenticated internal scans after March 31, 2025 (11.3.1.2, PCI DSS v4.0.1).
  7. Missing targeted risk analyses where you set your own frequency (12.3.1, PCI DSS v4.0.1).
  8. Controls “planned” instead of in place. Requirements are not considered in place if they are scheduled for a future date (PCI DSS v4.0.1, Section 12).
  9. No annual check of service providers’ compliance status (12.8.4, PCI DSS v4.0.1).

10. What non-compliance can cost

PCI DSS has no government fine schedule. Costs arrive through the acquiring bank, forensic investigations and, after a breach, regulators. These are the amounts the brands and regulators publish.

  • Visa assessments go to the bank first. If a merchant or service provider does not comply, Visa may assess the issuer or acquirer (Visa AIS Program page), which must pay whether it absorbs the amount, passes it on or increases it when billing customers (Visa Core Rules, October 2026, ID# 0001054).
  • Up to USD 100,000 per incident for failing to notify Visa of a suspected or confirmed compromise, or to respond adequately (Visa Product and Service Rules, October 2026, Section 12.5.1.3, ID# 0003524). Notification is due within three calendar days (Visa WTDIC v10.0, 2026).
  • Breaking Visa’s compromise-response rules costs USD 100,000 for Level 1 and 2 merchants. Since February 9, 2025, Level 3 merchants start at USD 25,000 (500,000 to 1,000,000 transactions), USD 10,000 (100,000 to 500,000) or USD 5,000 (1 to 100,000), which Visa can raise to USD 100,000 (Visa WTDIC v10.0, 2026).
  • Forensic investigation. Visa can require a PCI Forensic Investigator (PFI) under contract within five business days, a preliminary report within five business days after that, and a final report within ten business days of completion. If the investigation runs past four full calendar months, Visa may charge USD 10,000 per month (Level 1 and 2 merchants) or a USD 3,000 flat fee (Level 3) (Visa WTDIC v10.0, 2026).
  • Regulators. Home Depot paid $17.5 million to settle a multistate investigation into a breach of payment card information of about 40 million customers (California Attorney General, 2020). Target paid $18.5 million to 47 states and the District of Columbia (Connecticut Attorney General, 2017).

Amounts for AIS program non-compliance itself are set in Visa’s AIS Program Guide, not in the published rules themselves (Visa Product and Service Rules, Section 12.5.1.1, ID# 0008193). State, HIPAA, GDPR and other penalties that can follow a card data breach are compared in data breach fines and penalties by law.

PCI DSS compliance checklist (summary)

  1. Map every payment channel and data flow, and confirm scope (12.5.2).
  2. Confirm your level and validation route with your acquirer, in writing.
  3. Pick the right SAQ, or plan a ROC with a QSA.
  4. Cut scope: outsource, tokenize, use validated P2PE, segment the CDE.
  5. Close the March 31, 2025 gaps: MFA everywhere into the CDE, 12-character passwords, payment page script controls, authenticated scans, targeted risk analyses.
  6. Book quarterly ASV and internal scans and fix findings until they pass.
  7. Run annual internal and external penetration tests, plus segmentation tests (six-monthly for service providers), and retest fixes.
  8. Collect AOCs from every service provider and track them annually.
  9. Train staff, test the incident response plan and know Visa’s three-day notification rule.
  10. Complete the SAQ or ROC and the AOC, and submit them to your acquirer or customers.

The full version with evidence for each item is our PCI DSS compliance checklist. For help with the testing requirements, see our PCI DSS compliance services.

What changes for 2027

No new PCI DSS version has a published date. What is confirmed:

  • v4.0.1 remains the active standard. The Council ran a request for comments on v4.0.1 from June 3 to July 20, 2026, to gather feedback “to help shape the future of the standard,” without stating a publication timeline (PCI SSC blog, June 2026).
  • Guidance keeps changing between versions. The August 2026 FAQ 1331 revision (PCI SSC, 2026) shows applicability guidance can shift without a new version; check FAQs before each assessment.

Sources

  • PCI Security Standards Council, Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4.0.1, June 2024. PCI SSC Document Library
  • PCI Security Standards Council, Self-Assessment Questionnaire Instructions and Guidelines, v4.0, September 2023. PCI SSC Document Library
  • PCI Security Standards Council, “Just Published: PCI DSS v4.0.1,” June 11, 2024. Link
  • PCI Security Standards Council, “Now is the Time for Organizations to Adopt the Future-Dated Requirements of PCI DSS v4.x,” August 20, 2024. Link
  • PCI Security Standards Council, “Important Updates Announced for Merchants Validating to Self-Assessment Questionnaire A,” January 30, 2025. Link
  • PCI Security Standards Council, “FAQ Clarifies New SAQ A Eligibility Criteria for E-Commerce Merchants,” February 28, 2025. Link
  • PCI Security Standards Council, “Bulletin: Revised Update to FAQ 1331,” August 4, 2026. Link
  • PCI Security Standards Council, “Request for Comments: PCI DSS v4.0.1,” June 3, 2026. Link
  • PCI Security Standards Council, “About Us,” accessed November 2026. Link
  • Visa, “Account Information Security Program and PCI,” accessed November 2026. Link
  • Visa, What To Do If Compromised, Version 10.0, effective June 25, 2026. Link
  • Visa, Visa Core Rules and Visa Product and Service Rules, October 24, 2026. Link
  • Visa, PCI DSS Validation Best Practice Review, September 20, 2018. Link
  • Mastercard, “Site Data Protection Program and PCI,” accessed November 2026. Link
  • California Attorney General, “Attorney General Becerra Announces $17.5 Million Settlement Against Home Depot Over Credit Card Data Breach,” November 24, 2020. Link
  • Connecticut Attorney General, “AG Jepsen: Conn. Leads $18.5M Settlement with Target Corporation over 2013 Data Breach,” May 23, 2017. Link

Frequently asked questions

Is PCI DSS compliance required by law? PCI DSS is an industry standard enforced by contract, not a government regulation. Visa, for example, requires it of every entity that stores, processes or transmits Visa cardholder data (Visa AIS Program page). Regulators can still act after a breach, as the $17.5 million Home Depot and $18.5 million Target state settlements show.

How often does PCI DSS require penetration testing? Internal and external penetration tests at least once every 12 months and after any significant change; segmentation tests every 12 months for merchants and every six months for service providers (Requirements 11.4.2, 11.4.3, 11.4.5, 11.4.6, PCI DSS v4.0.1). SAQ D and a ROC include 11.4; other SAQs vary.

What happens if a merchant is not PCI compliant? Visa can assess the merchant’s acquiring bank, which can pass the cost on, including up to USD 100,000 per incident when a compromise is not reported in time. After a breach, Visa can require a PCI Forensic Investigator and charge USD 10,000 a month for Level 1 and 2 merchant investigations running past four months (Visa WTDIC v10.0, 2026).

Do small merchants have to validate PCI compliance? They must comply. Validation depends on the brand and the acquirer: Mastercard does not require Level 4 merchants to validate to Mastercard unless law requires it (Mastercard SDP page), while Visa lists an annual SAQ for its Level 3, which since 2024 includes the former Level 4.

Wahid Iqbal

Written by

Wahid Iqbal, Head of Compliance

20+ years in the field. Focus: PCI DSS, ISO 27001 & ISO 22301. Part of the team that scopes, tests, and reports for our clients. Full profile →

Find out what an attacker sees.

Tell us what to test and see your fixed price.

Prefer the full scoping questionnaire? 
Start the conversation

Get a quick proposal

We are online