Skip to content

PCI Compliance Levels and SAQ Types: Which One Applies, and When You Need a Pentest

PCI compliance levels by card brand, what each level submits, the SAQ types and who qualifies, and which SAQs require ASV scans or a penetration test.

Omar KhandakerBy , Senior Security ConsultantWahid IqbalReviewed by Wahid Iqbal, Head of ComplianceUpdated 18 min read

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

Get my fixed price

PCI compliance levels decide how you prove compliance with PCI DSS, not whether you have to comply. Every business that stores, processes or transmits cardholder data must meet the standard. Your level, set by each card brand from your annual transaction count, decides the paperwork: a Report on Compliance from a formal assessment, or a Self-Assessment Questionnaire (SAQ) you complete yourself. Your SAQ type, set by how you take payments, decides which requirements you answer, including whether you need quarterly ASV scans and a penetration test.

Flow diagram in five steps showing how PCI levels and SAQ types combine. Annual transactions are counted per card brand, each brand sets the level thresholds and the acquirer applies them, and the level decides what is submitted: a Report on Compliance at Level 1 and a Self-Assessment Questionnaire for everyone else. The SAQ type is then chosen by payment channel, not by level, and the SAQ type or ROC scope sets the ASV scans and the Requirement 11.4 penetration tests. A closing note says the level decides how compliance is proven, not whether a business has to comply.

This guide covers both halves: the levels for each brand and what each must submit, then the SAQ types, who qualifies for each, and which ones pull in scanning and testing. We run the Requirement 11.4 penetration test. The ASV scans and, for organizations that validate with a Report on Compliance, the ROC assessment are delivered through our PCI partner, Sovereign Secure, a Qualified Security Assessor (QSA) company. Our PCI DSS penetration testing page covers that work; this page is about working out what applies to you.

Who sets PCI compliance levels

Not the PCI Security Standards Council. The Council writes the standard and the SAQs, but its founding payment brands (American Express, Discover, JCB, Mastercard and Visa) each run their own compliance program, and whether a small merchant has to validate “is determined by the individual payment brands” (PCI SSC merchant resources). In practice you deal with your acquirer, the bank or processor that handles your card payments, and it tells you your level and what to submit.

Three consequences follow:

  • You can have a different level with each brand. Levels are counted per brand, so a merchant can be Level 2 for Visa and Level 3 for American Express.
  • Brands can move you up. American Express, for example, reserves the right to assign Level 1 to any merchant at its discretion.
  • Older guides are out of date on Visa. Visa now publishes three merchant levels, not four; the former Level 4 has been folded into Level 3 (Visa security and compliance). Some regional Visa sites still state that “all merchants will fall into one of the four merchant levels” (Visa Trinidad and Tobago, checked November 2026), so if your acquirer still calls you Level 4, use its wording. What you submit is the same either way.

Each brand’s program has its own name, which is what you will see on acquirer paperwork: Mastercard’s is Site Data Protection (SDP) and American Express publishes its rules in the Data Security Operating Policy (DSOP).

Merchant levels by card brand

Counts are annual transactions with that brand over a 12-month period.

Level Visa Mastercard American Express
Level 1 Over 6 million Visa transactions across all channels, or a global merchant identified as Level 1 by any Visa region Over 6 million combined Mastercard and Maestro transactions, or any merchant that has had an account data compromise 2.5 million or more, or any merchant American Express assigns to Level 1
Level 2 1 million to 6 million across all channels Over 1 million and up to 6 million 50,000 to fewer than 2.5 million
Level 3 Everyone below Level 2; Visa describes it as fewer than 1 million e-commerce transactions across all channels Over 20,000 and up to 1 million combined e-commerce transactions 10,000 to fewer than 50,000
Level 4 No longer a separate Visa level All other merchants Fewer than 10,000

Visa counts the corporate entity’s total Visa volume (credit, debit and prepaid) in one country or with one acquirer; volume from independently owned and operated locations, such as franchisees, may be excluded if the corporate entity does not process it. American Express levels come from Table 2-1 of its Data Security Operating Policy (DSOP, October 2026 edition). Discover and JCB run their own programs; your acquirer confirms how they apply to you.

What each level has to submit

This is where the levels matter. Level 1 means a Report on Compliance; everyone else self-assesses, with extra conditions at Level 2.

Level Visa Mastercard American Express
Level 1 Annual Report on Compliance by a Qualified Security Assessor (QSA), or by an internal resource if signed by an officer of the company, plus an Attestation of Compliance (AOC) Annual onsite assessment resulting in a Report on Compliance ROC with its AOC, mandatory
Level 2 Annual SAQ Annual SAQ, with a QSA or a PCI-certified Internal Security Assessor (ISA) involved when the SAQ is A, A-EP or D; or a ROC SAQ with its AOC mandatory (unless a ROC is submitted), plus quarterly scans where the SAQ type requires them
Level 3 Annual SAQ Mastercard does not require validation to Mastercard; the acquirer must run a risk management program for these merchants SAQ optional unless American Express requires it
Level 4 Not applicable As Level 3 As Level 3

Two points get lost in most summaries. First, “no validation required” never means “no compliance required”: the brands still expect Level 3 and Level 4 merchants to comply with PCI DSS, and your acquirer can ask for an SAQ at any time. Second, quarterly external scans by an Approved Scanning Vendor (ASV) are not set by your level. They come from Requirement 11.3.2 of the standard, so whether you need them depends on your SAQ type or ROC scope, covered below.

Once you know your level, the next question is usually budget. Our guide to PCI compliance cost by level and SAQ breaks that down.

PCI Level 1, Level 2, Level 3 and Level 4: what each requires

The two tables above, read one level at a time. Thresholds are per brand, so check every brand you accept.

PCI Level 1: what it requires

  • Who: over 6 million Visa or Mastercard transactions a year, 2.5 million or more with American Express, or any merchant a brand assigns to Level 1, including a Mastercard merchant that has had an account data compromise.
  • What to submit: an annual Report on Compliance with its Attestation of Compliance. A QSA performs the assessment; Visa also accepts an internal resource if an officer of the company signs.
  • Scanning and testing: a ROC covers the whole standard, so quarterly ASV scans, internal scans and the full Requirement 11.4 penetration test all apply to the systems in scope.

PCI Level 2: what it requires

  • Who: 1 million to 6 million Visa or Mastercard transactions a year, or 50,000 to fewer than 2.5 million with American Express.
  • What to submit: an annual SAQ with its AOC. Mastercard wants a QSA or a PCI-certified Internal Security Assessor (ISA) involved when the SAQ is A, A-EP or D, and accepts a ROC instead. American Express makes the SAQ AOC mandatory unless you submit a ROC.
  • Scanning and testing: set by the SAQ type, not the level. A Level 2 merchant on SAQ D has the same scans and penetration tests as a Level 1 merchant; one on SAQ A has ASV scans only.

PCI Level 3 and Level 4: what they require

  • Who: everyone below Level 2. Mastercard splits the two at 20,000 e-commerce transactions a year and American Express at 10,000 transactions; Visa now treats them as one level.
  • What to submit: an annual SAQ for Visa, and for the other brands whatever your acquirer asks for. Mastercard leaves validation to the acquirer’s risk program, and American Express makes the SAQ optional unless it requires one.
  • Scanning and testing: again set by the SAQ. A small e-commerce merchant on SAQ A-EP still needs ASV scans and an external penetration test, however few transactions it handles.

Service provider levels

If you store, process or transmit cardholder data on behalf of other businesses, such as a payment gateway, a hosting provider or a SaaS platform that touches card data, you are a service provider, and the levels are simpler.

Brand Level 1 Level 2
Visa VisaNet processors, or any service provider handling over 300,000 Visa transactions a year: annual onsite assessment, with an AOC signed by the service provider and the QSA Fewer than 300,000: SAQ D for Service Providers, or an AOC including a QSA signature. QSA validation is required to be listed on the Visa Global Registry of Service Providers
American Express 2.5 million transactions or more a year, or any provider American Express deems Level 1 Fewer than 2.5 million

SAQ D for Service Providers is the only SAQ a service provider can use. Service providers also carry a testing obligation merchants do not: where segmentation reduces PCI scope, it must be penetration tested at least every six months and after any change to segmentation controls (Requirement 11.4.6), not just once a year. Our network segmentation testing service covers both the annual test and that six-monthly re-test.

The SAQ types: which one fits your payment setup

The SAQ is chosen by payment channel, not by level. Each SAQ has eligibility criteria; if you cannot confirm every criterion for a channel, you drop to a broader SAQ, and SAQ D is the one that fits everyone else. A merchant with more than one channel may need more than one SAQ, or SAQ D for the whole environment.

The scanning and testing columns show which Requirement 11 items each SAQ includes, taken from the Council’s SAQ documents for PCI DSS v4.x. Always confirm against the revision your acquirer asks for.

SAQ Who it is for ASV scans (11.3.2) Penetration testing (11.4)
A Card-not-present merchants (e-commerce or mail and telephone order) that fully outsource all account data handling; every element of the payment page comes only and directly from a PCI DSS compliant provider, for example a full redirect to the provider’s page or the provider’s embedded form Yes No
A-EP E-commerce merchants that outsource processing but whose own website delivers part of the payment page or controls how card data reaches the provider, for example a form on the merchant’s page that posts card data directly to the provider Yes Yes: methodology, external test, retest and segmentation (11.4.1, 11.4.3, 11.4.4, 11.4.5); not the internal test
B Merchants using only imprint machines or standalone dial-out terminals, not connected to the internet or other systems No No
B-IP Merchants using only standalone, PCI-approved payment terminals connected over IP to the processor, isolated from other systems Yes Segmentation test only (11.4.5), if segmentation isolates the terminals
C-VT Merchants keying transactions one at a time into a provider-hosted virtual terminal, on an isolated computer with no card readers attached No No
C Merchants with a payment application system and internet connection on the same device or single-store network, isolated from other systems, with no electronic card data storage Yes, plus internal scans (11.3.1) Segmentation test only (11.4.5), if segmentation is used
P2PE Merchants using only the terminals of a validated, PCI-listed point-to-point encryption solution No No
SPoC Merchants accepting card-present payments with PIN entry on a commercial phone or tablet, through a validated software-based solution and secure card reader Confirm in the SAQ Confirm in the SAQ
D for Merchants Every merchant that does not meet another SAQ’s criteria, including e-commerce sites that receive card data and merchants that store it electronically Yes, plus internal scans Yes, in full
D for Service Providers Every service provider eligible to self-assess Yes, plus internal scans Yes, in full, including six-monthly segmentation testing (11.4.6)

The most common mistake in this table is between A and A-EP. If your checkout is a full redirect or the provider’s embedded form, and every element of the payment page comes from your payment provider, you are usually SAQ A. If your own site serves any element of the payment page, or posts card data to the provider directly from your page, you are usually A-EP, and A-EP brings in an external penetration test and, in practice, a web application test of the checkout.

SAQ C and both SAQ D versions also include internal vulnerability scans under Requirement 11.3.1. We run those as validated internal vulnerability scans; the external ASV scans in the same column are delivered through our PCI partner, Sovereign Secure.

SAQ A changed in 2025

The Council revised SAQ A in January 2025, effective 31 March 2025. The revision removed the payment-page script requirements, 6.4.3 and 11.6.1, and the related targeted risk analysis in 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 on the SAQ A update). The underlying requirements still exist in PCI DSS; they simply no longer appear on SAQ A. Our PCI compliance checklist covers how 6.4.3 and 11.6.1 work for everyone else.

Which levels and SAQs need a penetration test

Your level alone never answers this. The validation document does:

  • Report on Compliance (every Level 1, and anyone who chooses a ROC): the full Requirement 11.4: internal and external tests at least every 12 months and after significant change, segmentation testing where segmentation reduces scope, and a retest of exploitable findings.
  • SAQ D, merchant or service provider: the full Requirement 11.4, the same as a ROC.
  • SAQ A-EP: an external test, segmentation testing if used, a documented methodology and a retest. No internal test.
  • SAQ B-IP and SAQ C: segmentation testing only, and only if segmentation is what keeps the rest of your network out of scope.
  • SAQ A, B, C-VT and P2PE: no penetration test on the SAQ, though an acquirer or a large customer can still ask for one.

For an SAQ A-EP storefront, the test usually means an external network penetration test from $4,200 and a web application penetration test of the checkout from $5,200. For SAQ D and ROC scopes, our breakdown of PCI penetration testing cost prices each component, including internal and segmentation testing, and every test includes a free retest. The detail of each sub-requirement, including what the assessor checks in the report, is in our guide to PCI DSS penetration testing requirements.

For what the checkout test covers on a storefront, from the cart to the payment handoff, see our guide to e-commerce penetration testing.

Scans and tests are separate requirements with separate evidence: a clean ASV scan does not satisfy 11.4, and a penetration test does not replace the quarterly scan. Our comparison of an ASV scan vs a penetration test explains why.

If you are still choosing a tester, our list of PCI penetration testing vendors compares the firms that do this work.

Worked examples

These illustrative scenarios show how level and SAQ combine. Your acquirer makes the final call.

Business Level SAQ Scanning and testing
Online store, 60,000 Visa e-commerce transactions a year, checkout in the payment provider’s embedded form Visa Level 3 A Quarterly ASV scans; no penetration test on the SAQ
The same store after moving to a checkout form on its own page that posts card data directly to the provider Visa Level 3 A-EP Quarterly ASV scans, an annual external test and a checkout web application test
Restaurant group, 1.5 million Visa transactions a year, integrated POS across 12 connected locations Visa Level 2 D (SAQ C is limited to a single location) Quarterly internal and ASV scans, annual internal and external tests, and segmentation testing if segmentation keeps the rest of the network out of scope
SaaS platform processing 400,000 Visa transactions a year for its customers Visa service provider Level 1 ROC Full 11.4, with segmentation tested every six months if segmentation is used

The restaurant group is the most common multi-location case. Our page on hotel and restaurant PCI compliance covers how those networks are scoped and tested.

When one merchant needs two SAQs

SAQs follow payment channels, so one merchant can need two. A retailer with P2PE terminals in its stores and a fully outsourced online checkout can complete SAQ P2PE for the stores and SAQ A for the website, as long as the two channels are kept separate. If the channels share systems, or one of them fails its SAQ’s eligibility criteria, the usual outcome is a single SAQ D for the whole environment. Your acquirer decides whether it accepts several SAQs or wants one.

When your level changes

Levels are recounted on each brand’s 12-month volume. If growth, a merger or a new sales channel takes you over a threshold, your acquirer tells you the new level and when the first validation at that level is due. A breach can move you without any change in volume: Mastercard treats any merchant that has had an account data compromise as Level 1, and American Express can assign Level 1 at its discretion.

How to work out your level and SAQ

  1. Count transactions per brand over the last 12 months, by channel: e-commerce, card-present, mail and telephone order.
  2. Check each brand’s thresholds in the table above, then confirm your level with your acquirer.
  3. List every payment channel and how card data moves in each one, including who serves each element of the payment page.
  4. Match each channel to an SAQ by its eligibility criteria. If any criterion fails, move to the broader SAQ.
  5. Read the SAQ’s Requirement 11 rows to see which scans and tests apply, then schedule them before the attestation is due, with time to fix findings and retest.

Frequently asked questions

What are the 4 levels of PCI compliance? Mastercard and American Express each have four merchant levels, based on annual transactions with that brand. Visa now has three: Level 1 above 6 million transactions, Level 2 from 1 million to 6 million, and Level 3 below that, with the former Level 4 folded into Level 3.

Is PCI compliance required for Level 4 merchants? Yes. Every merchant that accepts card payments must comply with PCI DSS. Level 4 only changes how, or whether, you report compliance, and your acquirer decides what you submit.

Who decides my merchant level? Each card brand sets the thresholds and your acquirer applies them. If you have processed a large one-off volume or merged with another business, ask the acquirer to confirm your level rather than assuming it.

What is the difference between SAQ A and SAQ A-EP? Who delivers the payment page. Under SAQ A every element of it comes only and directly from your PCI compliant provider. Under A-EP your own website delivers part of it or controls how card data reaches the provider, so your site’s security affects the transaction, and the SAQ adds requirements including an external penetration test.

Does SAQ D require a penetration test? Yes. SAQ D for Merchants and SAQ D for Service Providers both include Requirement 11.4 in full: internal and external tests at least annually and after significant change, segmentation testing where used, and a retest of exploitable findings.

Can a Level 1 merchant self-assess? Not with an SAQ. Visa allows the Level 1 Report on Compliance to be completed by an internal resource if an officer of the company signs it; otherwise a QSA performs it.

What does a PCI Level 2 merchant need to do? Complete an annual SAQ with its Attestation of Compliance, or a Report on Compliance if you prefer or your acquirer asks for one. Mastercard requires a QSA or a PCI-certified Internal Security Assessor to be involved when the SAQ is A, A-EP or D. The scans and penetration tests come from the SAQ type, so a Level 2 merchant on SAQ D needs quarterly scans and the full Requirement 11.4 test.

Can I fall into two different PCI SAQs? Yes. A merchant with separate payment channels can complete one SAQ per channel if each channel meets that SAQ’s eligibility criteria on its own. If the channels share systems, expect SAQ D for the whole environment. Confirm the approach with your acquirer first.

When is my SAQ or ROC due each year? Validation is annual, and the date is set by your acquirer or the card brand, usually the anniversary of your last Attestation of Compliance. American Express, for example, tells merchants in its program to validate “annually and every 90 days”, the 90 days being the quarterly scan (DSOP). Ask your acquirer for the date in writing and work back from it.

Does my PCI level change after a data breach? It can. Mastercard classes any merchant that has had an account data compromise as Level 1, and American Express can assign Level 1 to any merchant at its discretion. A higher level means a Report on Compliance instead of an SAQ.

Can Invadel handle the scans and the assessment as well as the test? Yes. We run the Requirement 11.4 penetration test. The quarterly ASV scans and, where you validate with a ROC, the ROC assessment are delivered through our PCI partner, Sovereign Secure, a Qualified Security Assessor (QSA) company, all on one calendar. The penetration test is still scoped and reported on its own, at a fixed price with a free retest.

Not sure which SAQ your checkout puts you in? Send us your payment setup and we will map it to the SAQ and the testing it requires before you commit to anything.

Omar Khandaker

Written by

Omar Khandaker, Senior Security Consultant

11+ years in the field. Focus: PCI DSS, ISO 27001, ISO 9001 & CMA. 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