Cybernion
← Insights

PCI DSS

PCI DSS Compliance Levels and SAQ Types Explained

3 July 2026 · Updated 3 July 2026

PCI DSS has four merchant levels, set by the card brands on annual transaction volume, and eight Self-Assessment Questionnaire (SAQ) types. The level decides whether it is a full assessment or a self-assessment. The SAQ type depends on exactly how a business accepts payments. Level 1 usually needs a QSA. The rest usually self-assess.

There are two factors that determine the amount of PCI DSS work a business needs to undertake. Transaction volume determines the merchant level, while the way card payments are accepted determines the applicable SAQ. The second is where we tend to see more confusion. Selecting the wrong SAQ can result in unnecessary work or, more importantly, parts of the payment environment not being assessed as they should be. In practice, we see SAQ mismatches far more often than issues with merchant level classification.

What are the four PCI DSS merchant levels?

PCI DSS defines four merchant levels, set by the card brands according to annual transaction volume. Level 1 is the highest volume tier and generally requires an annual on-site assessment by a Qualified Security Assessor (QSA) producing a Report on Compliance (ROC), plus quarterly scans by an Approved Scanning Vendor (ASV). Levels 2, 3 and 4 descend by volume and typically validate through a Self-Assessment Questionnaire (SAQ) and an Attestation of Compliance (AOC), with ASV scans where relevant. The detail that trips people up: the transaction thresholds are set by each individual card brand such as Visa and Mastercard, not by the PCI Security Standards Council, and they differ between brands. The numbers below are indicative, drawn from the common Visa and Mastercard structure. The actual level comes from the acquiring bank across the card brands a business accepts, so confirm it with them rather than assuming.

Level Indicative annual transaction volume Typical validation
Level 1 Over 6 million card transactions, or any merchant a card brand designates Level 1 Annual assessment by a QSA (ROC), quarterly ASV scans
Level 2 1 million to 6 million transactions Annual SAQ, quarterly ASV scans
Level 3 20,000 to 1 million e-commerce transactions Annual SAQ, quarterly ASV scans
Level 4 Under 20,000 e-commerce transactions, or up to 1 million total Annual SAQ, quarterly ASV scans where required

Treat these thresholds as indicative. A breach or card brand direction can push a merchant up a level regardless of volume.

What are the PCI DSS SAQ types?

There are eight Self-Assessment Questionnaire types under PCI DSS v4.0.1, each scoped to a specific way of handling card payments. The one to complete is the one that matches how a business accepts cards, not the shortest one. Picking the wrong SAQ is a common and serious error, because each carries a different set of applicable requirements. The eight are SAQ A, A-EP, B, B-IP, C, C-VT, D and P2PE. In v4.0.1 the Council clarified eligibility criteria in SAQs A, A-EP and C-VT, added a requirement to SAQ A, and removed a requirement from SAQ C. Before starting any SAQ, check the eligibility criteria in the Document Changes table at the front of that SAQ, and confirm eligibility with the entity it is submitted to, usually the acquirer. If none fit, it is SAQ D.

SAQ Who it is for
SAQ A E-commerce or mail/telephone merchants who fully outsource all card data functions to a PCI DSS compliant third party, with no card data on their systems (for example a full redirect or compliant hosted iframe)
SAQ A-EP E-commerce merchants who do not receive card data but can affect the security of the payment page, such as through scripts they control
SAQ B Merchants using only imprint machines or standalone dial-out terminals, with no electronic cardholder data storage
SAQ B-IP Merchants using only standalone, IP-connected payment terminals, with no electronic cardholder data storage
SAQ C Merchants with payment application systems connected to the internet, with no electronic cardholder data storage
SAQ C-VT Merchants who key single transactions into a virtual terminal on one isolated device, with no electronic cardholder data storage
SAQ D Merchants and service providers that fit none of the other types; the broadest requirement set
SAQ P2PE Merchants using only hardware terminals in a validated PCI-listed point-to-point encryption (P2PE) solution

Which SAQ do I need for an e-commerce site?

It depends on how the payment page is built, and this is where merchants most often get it wrong. If every card data function is outsourced to a PCI DSS compliant third party and the page never receives card data, for example a full redirect to the processor or a compliant hosted iframe that meets the eligibility criteria, SAQ A may apply. If the site does not receive card data but can still affect the security of the payment page, for instance because it serves scripts onto the page or controls its content, that falls to SAQ A-EP, which carries substantially more requirements. The distinction turned sharper under v4.0.1, which added a requirement to SAQ A and tightened its eligibility wording. Even SAQ A merchants now face client-side obligations they may not expect, covered in our guide to client-side payment page security. The full set of changes in v4.0.1 and the 31 March 2025 deadline are in PCI DSS 4.0.1 changes. A self-hosted payment page, or card data on a business’s own systems, is SAQ D territory.

How do merchant levels and SAQs fit together?

The level sets whether a business self-assesses or needs a QSA; the SAQ sets what it self-assesses against. A Level 4 merchant taking payments through a fully outsourced e-commerce provider might validate with SAQ A and an AOC. A Level 2 merchant running its own payment application would validate with the far heavier SAQ D. A Level 1 merchant does not use an SAQ at all in the usual case, because the card brand requires a full QSA assessment and a ROC. The two dimensions are independent: transaction volume does not change which SAQ describes a setup, and the payment setup does not change the level. Service providers follow a parallel structure with their own thresholds and their own SAQ D variant. Because the specific numbers and any level escalation come from the card brands and the acquirer, the safe move is to confirm both the level and the eligible SAQ with the acquiring bank before starting. Getting either wrong wastes effort or, worse, leaves real gaps unassessed. For the wider picture of how PCI DSS works, see what is PCI DSS. Where the cardholder data environment runs on a platform that also requires an IRAP assessment, we scope and run both programs together.

Frequently asked questions

What are the four PCI DSS merchant levels?

PCI DSS has four merchant levels set by the card brands based on annual transaction volume. Level 1 is the highest volume and requires an annual assessment by a Qualified Security Assessor. Levels 2, 3 and 4 descend by volume and generally validate through a Self-Assessment Questionnaire. The exact transaction thresholds are set by each card brand such as Visa and Mastercard, so confirm your level with your acquiring bank.

What are the PCI DSS SAQ types?

There are eight Self-Assessment Questionnaire types under PCI DSS v4.0.1, and they are SAQ A, A-EP, B, B-IP, C, C-VT, D and P2PE. Each is scoped to a specific way of accepting payments, from fully outsourced e-commerce (SAQ A) to a validated point-to-point encryption solution (SAQ P2PE), with SAQ D as the catch-all for merchants and service providers that fit none of the others.

Which SAQ do I need for an e-commerce site?

It depends on how your payment page works. SAQ A applies when all card data functions are outsourced to a compliant third party and your page does not receive card data, such as a full redirect or a hosted iframe meeting the eligibility criteria. SAQ A-EP applies when your site does not receive card data but can affect the security of the payment page, such as through scripts you control. Confirm eligibility with your acquirer.

What is the difference between SAQ A and SAQ A-EP?

SAQ A is for e-commerce merchants who fully outsource cardholder data handling to a PCI DSS compliant third party, with no card data touching or being influenced by their systems beyond a redirect or compliant iframe. SAQ A-EP is for e-commerce merchants who still do not receive card data but retain some control over the security of the payment page, so they carry more requirements including managing scripts and change and tamper detection.

Does a small business have to do a PCI DSS assessment?

Usually not a full assessment by a Qualified Security Assessor, but yes to validation. Most small businesses fall into Level 4 and validate through a Self-Assessment Questionnaire and an Attestation of Compliance, plus quarterly Approved Scanning Vendor scans where the SAQ type requires them. The obligation to meet PCI DSS applies regardless of size; only the validation method changes.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. PCI Security Standards Council Bulletin: SAQs for PCI DSS v4.0.1 Now Available, PCI Security Standards Council, 15 October 2024
  2. Now is the Time for Organizations to Adopt the Future-Dated Requirements of PCI DSS v4.x, PCI Security Standards Council blog, 20 August 2024
  3. PCI DSS v4.0 SAQ A, PCI Security Standards Council Document Library
  4. PCI SSC Document Library, PCI Security Standards Council

Last updated: 3 July, 2026

Talk to us about your engagement

A scoped proposal within one business day.