PCI Compliance Levels
Uncover the four PCI compliance levels and their security requirements. Streamline your compliance management effortlessly with Controllo.ai—learn more now!
Controllo editorial team
Compliance operations / Product context

PCI compliance levels classify merchants based on payment card transaction volume and determine their required PCI DSS assessment requirements. They are widely used in the United States, United Kingdom, Canada, Australia, and India, particularly in retail, e-commerce, banking, and payment processing. These levels help businesses understand security requirements, plan compliance costs, and protect cardholder data.
Controllo.ai is back with a great informative article on PCI compliance levels. In this article, we’ll get to know about PCI merchant levels, explain the security requirements businesses need to understand, and outline how to approach compliance with greater confidence and much more.
Ashwin Chaudhary (opens in a new tab) is Founder & CEO of Accedere, a company working at the intersection of cybersecurity, governance, and technology-enabled compliance. Combining his experience as an author of Cybersecurity Leadership: Vedic and Western Wisdom Through Controllo.ai, a product launched in 2022 by Accedere, he applies this to structuring compliance controls, enhancing risk awareness, and facilitating audit readiness. With 20+ years of industry experience, over 20 frameworks and 6,000+ controls, the team has helped organizations get a more structured and organized approach to compliance.
Not sure what PCI compliance level fits your business? Wrong assessment and validation can result in excessive, redundant efforts and gaps in responsibilities. First, examine your payment environment, verify with your acquiring bank what you're required to do, and put together the documentation your team needs to get ready for your next audit. Learn how Controllo.ai can simplify compliance workflows.
The 4 PCI Compliance Levels Explained
The four PCI compliance levels generally classify merchants according to their annual payment transaction volume. The exact criteria and reporting obligations depend on the payment brand and acquiring bank, so the following thresholds are a general guide rather than universal rules.
| PCI compliance level | Typical merchant transaction volume | Common validation approach |
|---|---|---|
| Level 1 | More than 6 million transactions annually | Annual Report on Compliance (ROC) and other required validation activities |
| Level 2 | 1 million to 6 million transactions annually | Annual self-assessment or other validation, depending on applicable rules |
| Level 3 | Typically 20,000 to 1 million e-commerce transactions annually | Usually an annual Self-Assessment Questionnaire (SAQ) and applicable scans |
| Level 4 | Typically fewer than 20,000 e-commerce transactions, or other merchants below the relevant threshold | Validation requirements determined by the payment brand and acquiring bank |
Level 1
- Typical merchant transaction volume
- More than 6 million transactions annually
- Common validation approach
- Annual Report on Compliance (ROC) and other required validation activities
Level 2
- Typical merchant transaction volume
- 1 million to 6 million transactions annually
- Common validation approach
- Annual self-assessment or other validation, depending on applicable rules
Level 3
- Typical merchant transaction volume
- Typically 20,000 to 1 million e-commerce transactions annually
- Common validation approach
- Usually an annual Self-Assessment Questionnaire (SAQ) and applicable scans
Level 4
- Typical merchant transaction volume
- Typically fewer than 20,000 e-commerce transactions, or other merchants below the relevant threshold
- Common validation approach
- Validation requirements determined by the payment brand and acquiring bank
Important: These are commonly referenced Visa-style merchant categories. Other payment brands may use different thresholds or additional criteria. Confirm your assigned level and reporting requirements with your acquiring bank or payment brand.
What Is PCI and DSS Compliance?
Payment card industry data security known as PCI DSS is a standard of security requirements to protect payment account data, lower payments card fraud, and data breaches. Ensuring that your customer's payment card industry card information is safe is payment card compliance. This is achieved by fulfilling all the relevant pci dss requirements.
Do you Know? PCI DSS is designed for all merchants and service providers that handle, process or transmit payment account data. The PCI SSC (Security Standards Council) develops and manages the PCI DSS, but it's always best to double-check your validation responsibilities with your acquiring bank or relevant payment brand. These may differ depending on your payment channel.
Key PCI Data Security Requirements Businesses Should Know
Regardless of merchant level, organizations must understand the PCI data security requirements that apply to their environment. PCI DSS provides a baseline of technical and operational security controls to protect payment account data.
Important areas include:
- Network securityProtect systems and networks from unauthorized access.
- Account data protectionSafeguard stored payment data and protect data during transmission.
- Vulnerability managementMaintain secure systems, address vulnerabilities, and protect against malicious software.
- Access controlRestrict access to systems and sensitive information based on business needs.
- Monitoring and testingMonitor security activity and test controls regularly.
- Security policiesMaintain documented policies, procedures, and assigned responsibilities.
These areas summarize key themes within PCI DSS; they do not replace the full standard or its applicable requirements.
Why Payment Card Industry Compliance Matters
In 2026, benefits of payment card industry compliance Automating compliance processes with payment card data helps your business securely handle payment card data, minimize risks and ensure your organization complies with PCI DSS standards. Controllo.ai provides the best payment card industry compliance.Through Controllo.ai, we provide businesses an automated way to develop compliance workflows, organize audit evidence and increase visibility into security controls so they can do more with less.
How to Become PCI Compliant
If you are wondering how to become PCI compliant, start by identifying your payment environment and confirming your validation requirements. Follow these steps:
- Map payment flowsDetermine how your business accepts payments and whether payment account data enters your systems.
- Confirm your levelContact your acquiring bank or payment brand to verify your merchant category and validation obligations.
- Identify applicable requirementsDetermine which PCI DSS controls and assessment method apply to your environment.
- Assess security gapsReview your systems, access controls, policies, and evidence against the applicable requirements.
- Fix identified gapsAssign responsibilities and prioritize remediation activities.
- Complete validationSubmit the required SAQ, ROC, Attestation of Compliance, scans, or other documentation as applicable.
- Maintain complianceReview security controls regularly and reassess when your payment environment changes.
The appropriate process depends on your business and the validation rules that apply to it. PCI SSC provides official guidance on SAQs and recommends that merchants confirm eligibility with the organization receiving their compliance documentation
What Are the PCI Compliance Levels in the US?
PCI compliance levels classify merchants based mainly on the number of payment card transactions they process annually. In the US, the four merchant levels help determine the validation requirements businesses must follow to demonstrate compliance with the Payment Card Industry Data Security Standard (PCI DSS).
| PCI Compliance Level | Annual Transaction Volume | General Validation Requirements |
|---|---|---|
| Level 1 | More than 6 million transactions | Typically requires an annual Report on Compliance (ROC) by a Qualified Security Assessor (QSA) or eligible internal assessor, plus an Attestation of Compliance (AOC), as applicable. |
| Level 2 | 1 million to 6 million transactions | Typically requires an annual Self-Assessment Questionnaire (SAQ) or other validation specified by the payment brand or acquiring bank. |
| Level 3 | 20,000 to 1 million e-commerce transactions | Typically requires an applicable annual SAQ and may require quarterly vulnerability scans. |
| Level 4 | Fewer than 20,000 e-commerce transactions and other merchants processing up to 1 million transactions | Validation requirements are determined by the applicable payment brand and acquiring bank; an SAQ and vulnerability scans may be required. |
Level 1
- Annual Transaction Volume
- More than 6 million transactions
- General Validation Requirements
- Typically requires an annual Report on Compliance (ROC) by a Qualified Security Assessor (QSA) or eligible internal assessor, plus an Attestation of Compliance (AOC), as applicable.
Level 2
- Annual Transaction Volume
- 1 million to 6 million transactions
- General Validation Requirements
- Typically requires an annual Self-Assessment Questionnaire (SAQ) or other validation specified by the payment brand or acquiring bank.
Level 3
- Annual Transaction Volume
- 20,000 to 1 million e-commerce transactions
- General Validation Requirements
- Typically requires an applicable annual SAQ and may require quarterly vulnerability scans.
Level 4
- Annual Transaction Volume
- Fewer than 20,000 e-commerce transactions and other merchants processing up to 1 million transactions
- General Validation Requirements
- Validation requirements are determined by the applicable payment brand and acquiring bank; an SAQ and vulnerability scans may be required.
Frequently Asked Questions (FAQs)
How can US businesses determine their PCI compliance level?
Businesses should review their annual transaction volume, payment methods, and applicable payment brand requirements. Their acquiring bank or payment processor can help confirm the correct level and required validation method.
Do all PCI compliance levels require the same security assessments?
No. Validation requirements vary by merchant level, payment brand, and acquiring bank. Depending on the circumstances, businesses may need a Self-Assessment Questionnaire (SAQ), vulnerability scans, or a formal assessment by a Qualified Security Assessor (QSA).
Resource library
More compliance guidance
PCI Compliance
PCI DSS Compliance Software
Compare the best PCI DSS compliance software for 2026. Explore features, benefits, and audit tools. Simplify compliance with Controllo.ai today.
Read articlePCI Compliance
PCI Compliance Certification Cost
Explore PCI compliance certification costs uncover hidden expenses and simplify your compliance journey with Controllo.ai for smarter audit readiness and risk management
Read articlePCI Compliance
PCI DSS Compliance Services
Looking for PCI DSS compliance services? Compare 5 providers, explore their strengths, and simplify compliance workflows with Controllo.ai. Explore now!
Read article

