PCI compliance levels sort businesses that handle payment card data into tiers by annual transaction volume, and each tier carries its own validation obligations under the Payment Card Industry Data Security Standard. Merchants fall into one of four levels; service providers fall into one of two. The level you land in determines whether you can validate through a self-assessment questionnaire or must undergo a full onsite audit by a Qualified Security Assessor, how often you scan, and who signs the paperwork.
Merchant Levels by Transaction Volume
Visa, Mastercard, and the other major card brands each publish their own level definitions, but in practice the thresholds align closely enough that a merchant usually sits at the same level across all brands. The classification runs on a rolling twelve-month transaction count.
- Level 1: more than six million card transactions per year across all channels, including in-store, online, and phone.
- Level 2: between one million and six million total transactions per year across all channels.
- Level 3: between 20,000 and one million e-commerce transactions per year. This level targets online volume specifically, reflecting the higher fraud risk of card-not-present payments.
- Level 4: fewer than 20,000 e-commerce transactions per year, or up to one million total transactions through any channel. Most small businesses sit here.
Two situations push a merchant to Level 1 regardless of volume. Any merchant that has suffered a data breach exposing card data is automatically reclassified as Level 1. A card brand can also designate any merchant as Level 1 at its own discretion. The breach escalation catches companies off guard: a Level 3 retailer can wake up facing Level 1’s full audit requirements the week after a compromise.
Because card brands monitor the thresholds on a rolling basis, a growing business should track its own count and start preparing for the next level’s obligations well before it crosses the line.
Service Provider Levels
Service providers are companies that store, process, or transmit cardholder data on behalf of other businesses: payment gateways, hosting providers, third-party processors, and similar entities. A single compromised service provider can expose data from hundreds of merchants at once, so the levels address that cascading risk directly.
Level 1 service providers handle more than 300,000 transactions per year and must complete an annual onsite assessment by a QSA, along with quarterly ASV scans. Level 2 service providers handle 300,000 or fewer transactions annually and may validate through a Self-Assessment Questionnaire.1Mastercard. Site Data Protection (SDP) Program and PCI
If you’re a merchant using third parties that touch card data, you have a due-diligence obligation to confirm they’re compliant. Visa publishes a Global Registry of Service Providers listing compliant entities, and merchants should check it before signing contracts.2Visa. Visa Global Registry of Service Providers
Validation Requirements at Each Level
The gap between Level 1 and everyone else is wide. Level 1 merchants complete an annual Report on Compliance, a detailed security audit conducted onsite by a QSA, or by an internal auditor whose report is signed by a company officer. They also submit an Attestation of Compliance and pass quarterly external vulnerability scans performed by an Approved Scanning Vendor.3PCI Security Standards Council. PCI DSS ROC Reporting Template
Level 2, 3, and 4 merchants complete an annual Self-Assessment Questionnaire instead of a full onsite audit. They still need quarterly ASV scans and must submit an Attestation of Compliance. For Level 4 merchants, the acquiring bank sets the specific validation requirements, so the exact obligations can vary with your payment processor’s policies.
Every level also requires annual internal and external penetration testing, plus additional testing after significant infrastructure changes. If you use network segmentation to isolate your cardholder data environment, segmentation-specific testing is required every six months. Penetration tests actively try to exploit vulnerabilities, while ASV scans only identify them, so the two obligations don’t substitute for one another.
ASV scans fail if they find any vulnerability with a Common Vulnerability Scoring System base score of 4.0 or higher on a 10-point scale. Scores from 4.0 through 6.9 are medium severity; 7.0 through 10.0 are high severity. Either produces a failing scan, and you must remediate and rescan until the result passes before your compliance is considered valid.4PCI Security Standards Council. ASV Program Guide
The Attestation of Compliance accompanies both the ROC and the SAQ. It’s a formal declaration, signed by an executive officer of the merchant, affirming the organization meets all applicable requirements. The AOC form doesn’t restrict which executive title can sign, but the signer must hold an executive officer position.5PCI Security Standards Council. Attestation of Compliance for Onsite Assessments – Merchants You submit these documents to your acquiring bank or directly to the card brands you accept, and compliance status requires annual renewal.
Picking the Right Self-Assessment Questionnaire
If you’re below Level 1, choosing the correct SAQ is the single most consequential decision in your compliance program. Each version is tailored to a specific technical environment. Picking the wrong one can mean answering hundreds of unnecessary questions, or skipping requirements that actually apply to you.
Under PCI DSS v4.0, ten SAQ types exist:
- SAQ A: for merchants that fully outsource all cardholder data handling to a validated third party, with no electronic storage, processing, or transmission on their own systems. Under v4.0, SAQ A merchants must now perform quarterly ASV vulnerability scans for the first time.6PCI Security Standards Council. Now is the Time for Organizations to Adopt the Future-Dated Requirements of PCI DSS v4.x
- SAQ A-EP: for e-commerce merchants that outsource payment processing but whose website can still affect transaction security, such as by hosting the checkout page while card data flows directly to the processor.7PCI Security Standards Council. Understanding SAQs for PCI DSS
- SAQ B: for brick-and-mortar or mail/phone-order merchants using only imprint machines or standalone dial-out terminals, with no electronic cardholder data storage. Not applicable to e-commerce.
- SAQ B-IP: for brick-and-mortar merchants using standalone, PCI-approved point-of-interaction devices that connect to the processor via IP. The device must be segmented from other systems and cannot rely on a computer, phone, or tablet for its connection.
- SAQ C: for merchants with payment application systems connected to the internet, but no electronic cardholder data storage.
- SAQ C-VT: for merchants that manually enter one transaction at a time through a virtual terminal on a standalone computer. Under v4.0, the eligibility criteria clarify that the terminal must be on an isolated, standalone machine.
- SAQ P2PE: for merchants using only a validated, PCI-listed point-to-point encryption solution, where the merchant never has access to clear-text card data.8PCI Security Standards Council. PCI DSS v4.0 Self-Assessment Questionnaire P2PE
- SAQ SPoC: added in 2023 for merchants using Software PIN entry on commercial off-the-shelf devices, such as tablets accepting PIN-based payments.9PCI Security Standards Council. PCI DSS v4 Whats New with Self-Assessment Questionnaires
- SAQ D (Merchants): the catch-all for any merchant that doesn’t fit the categories above, including those that store cardholder data electronically. It covers the full range of PCI DSS requirements and is the longest and most demanding.
- SAQ D (Service Providers): the equivalent catch-all for service providers that self-assess, now with additional reporting sections under v4.0 requiring service providers to describe their evidence and testing at each requirement.
Your SAQ type is not fixed. If you swap payment terminals, redesign your checkout flow, or start storing card data you didn’t store before, your eligible SAQ may change. PCI DSS v4.0 also added an annual scope confirmation exercise under Requirement 12.5.2, which forces you to document and validate your cardholder data environment every year rather than assume last year’s scope still applies.
Who Signs Off: QSAs and ISAs
Level 1 onsite assessments must be conducted by a Qualified Security Assessor. QSAs are individuals employed by security firms vetted and approved by the PCI Security Standards Council. Both the firm and the individual assessors must meet qualification requirements, including the Council’s training course and ongoing certification. The Council monitors QSA quality and can disqualify assessors whose work falls short.10PCI Security Standards Council. Become a Qualified Security Assessor
Professional fees for a Level 1 QSA audit typically range from $45,000 to $250,000 or more, depending on the complexity of your cardholder data environment. Larger organizations with multiple locations, diverse payment channels, and extensive infrastructure land at the higher end.
The Internal Security Assessor program offers an alternative for organizations that want in-house compliance expertise. ISAs are employees sponsored by their own company to perform internal PCI DSS assessments, manage interactions with external QSAs, and help close compliance gaps. Candidates need significant security audit experience, with the Council recommending at least five years, and must complete ISA training and certification.11PCI Security Standards Council. Internal Security Assessor Qualification
What PCI DSS 4.0 Changed
PCI DSS v3.2.1 was retired on March 31, 2024. The active versions are v4.0 and v4.0.1, the latter a limited June 2024 revision with clarifications. Of the 64 new requirements introduced in v4.0, 51 were treated as best practices until March 31, 2025, and became mandatory on that date.6PCI Security Standards Council. Now is the Time for Organizations to Adopt the Future-Dated Requirements of PCI DSS v4.x
Several changes affect daily operations at most levels:
- Longer passwords. The minimum length increased from seven to twelve characters. Systems that can’t support twelve must enforce at least eight.12PCI Security Standards Council. Summary of Changes from PCI DSS Version 3.2.1 to 4.0
- MFA for all CDE access. Multi-factor authentication was previously required only for remote access to the cardholder data environment. It now applies to all access, including local and in-person access by administrators and users.
- Payment page script monitoring. E-commerce merchants must inventory all scripts running on their payment pages and perform weekly scanning to detect unauthorized changes. This addresses digital skimming attacks that inject malicious code into checkout pages.13PCI Security Standards Council. How to Protect Your Ecommerce Transactions – An Overview of PCI DSS v4.0 Changes for Ecommerce Sites
- ASV scans for SAQ A merchants. Merchants that fully outsource cardholder data handling are no longer exempt from quarterly vulnerability scans.
- Annual scope confirmation. Every entity must formally document and validate its cardholder data environment scope each year.
Version 4.0 also introduced a customized approach to validation, which lets organizations design their own security controls as long as each meets the requirement’s stated objective and delivers at least equivalent protection.14PCI Security Standards Council. PCI DSS v4.0 Is the Customized Approach Right For Your Organization It demands a documented targeted risk analysis and more rigorous assessor scrutiny, so smaller merchants are generally better served by sticking with the defined approach.
Penalties for Falling Out of Compliance
Card brands don’t publish their fine schedules, which is why the financial exposure is often misunderstood. Fines are levied against your acquiring bank, which passes them along to you through your merchant agreement. Industry estimates put monthly non-compliance assessments between $5,000 and $100,000, escalating with the duration of the lapse and the severity of the gaps.
The worse outcome is losing your ability to process payments. Card brands can revoke that ability entirely, and a merchant terminated for compliance violations risks placement on the MATCH list, also known as the Terminated Merchant File. Placement lasts five years, during which virtually no payment processor will approve a new merchant account for the business.
A breach compounds everything. You’ll likely face mandatory forensic investigation by a PCI Forensic Investigator, liability for fraudulent transactions tied to the stolen data, notification costs, and potential lawsuits. The breach itself also triggers automatic Level 1 classification, so your next validation cycle requires a full QSA audit regardless of your transaction volume.
Reducing Your Level’s Burden
The most effective way to simplify compliance at any level is to shrink the number of systems that touch cardholder data. Two technologies do most of the work.
Tokenization replaces real card numbers with random substitute values at the point of entry. Systems that never see real card data fall outside your cardholder data environment, which means a shorter SAQ, fewer controls, and less surface area to defend. Merchants using tokenization effectively can often qualify for SAQ A instead of the comprehensive SAQ D.
Point-to-point encryption works similarly, encrypting card data at the terminal before it reaches your network. Merchants using a validated, PCI-listed P2PE solution can use SAQ P2PE, which is significantly shorter than SAQ D. The tradeoff is strict: PCI-approved terminals only, a maintained device inventory, regular inspection for tampering, and exact adherence to the P2PE Solution Provider’s instruction manual.8PCI Security Standards Council. PCI DSS v4.0 Self-Assessment Questionnaire P2PE
Scope reduction doesn’t eliminate your obligations. You still complete the appropriate SAQ annually, run quarterly ASV scans, and maintain an incident response plan. But the difference between completing SAQ A in a few days and grinding through SAQ D over several weeks is the difference between a manageable compliance program and one that dominates your calendar.