Compliance › PCI DSS › Levels and SAQ
PCI DSS levels and SAQ typesPCI DSS levels and SAQ types: find yours and what you must submit
Two questions decide your PCI workload: which merchant level you are, and which Self-Assessment Questionnaire fits how you take cards. This guide explains both, who confirms them, and the mistakes that send people to the wrong form.
Free for buyers · provider-funded introductions · Updated October 2026
How do I find my PCI DSS level and SAQ?
Your merchant level comes from how many card transactions you process, counted over a recent period, and the payment brands set the thresholds. Your SAQ comes from how you take cards: a fully outsourced payment page, a standalone terminal and a system that stores card data each point to a different questionnaire. Your acquirer confirms both, so ask for the answer in writing.
- The Council does not decide your level. Your acquirer and the brands do. See the PCI DSS hub.
- A hosted checkout can shrink your scope. It does not by itself decide your SAQ.
- Several channels can mean more than one SAQ, or a larger one. Confirm how your acquirer wants this reported.
The four PCI merchant levels
The thresholds below are from Mastercard’s program. Other brands publish their own.
| Level | Threshold in the Mastercard program | Validation |
|---|---|---|
| Level 1 | More than 6 million combined Mastercard and Maestro transactions a year, or the merchant meets Visa Level 1, or Mastercard decides | An annual PCI DSS assessment ending in a Report on Compliance (ROC) |
| Level 2 | More than 1 million and up to 6 million transactions, or the merchant meets Visa Level 2 | An annual Self-Assessment Questionnaire (SAQ) |
| Level 3 | More than 20,000 and up to 1 million e-commerce transactions, or the merchant meets Visa Level 3 | An annual SAQ |
| Level 4 | All other merchants | An annual SAQ |
Mastercard says merchants count transactions over the most recent 52 weeks and should contact their acquirer for help, and that it may place any merchant at Level 1 at its own discretion. Source: Mastercard Site Data Protection program. Visa and other brands use similar but not identical figures, so check each brand you accept.
Which SAQ fits how you take cards
Match the way card data reaches you, not the product name on your checkout.
| SAQ | Typically for | Key limit |
|---|---|---|
| SAQ A | Card-not-present merchants (e-commerce, mail or phone) that hand all card-data functions to compliant third parties | No card data on your own systems |
| SAQ A-EP | E-commerce merchants that outsource payment processing in part, but whose web servers can affect the security of the payment | May process or transmit card data, but not store it |
| SAQ B | Merchants using standalone dial-out terminals | No electronic card data storage, no connection to other systems |
| SAQ B-IP | Merchants using standalone approved terminals that connect over the internet | No electronic storage, isolated from other systems |
| SAQ C-VT | Merchants who key card details into a web-based virtual terminal | Typically one transaction at a time, from an isolated device |
| SAQ C | Merchants with payment applications connected to the internet | No electronic card data storage |
| SAQ P2PE | Merchants using an approved hardware point-to-point encryption solution | No access to the clear-text card data |
| SAQ D | Everything else, including merchants that store card data electronically, and service providers | The most comprehensive questionnaire |
Each SAQ has its own eligibility criteria, and the Council clarified the criteria for SAQ A, A-EP and C-VT in the v4.0.1 update. Read the criteria in the current SAQ and confirm the choice with your acquirer before you start.
SAQ, ROC and AoC: what you actually submit
| Document | Who completes it | What it is |
|---|---|---|
| SAQ | You, with help if you want it | A questionnaire that records how you meet the requirements for your SAQ type |
| ROC | A QSA | The assessor report after an on-site assessment, used where your acquirer or brand requires one |
| AoC | You, or the QSA with a ROC | The signed Attestation of Compliance that summarizes your result and is what you usually submit |
When you need a QSA, an ISA or an external scan
- A QSA is a company qualified by the Council to assess you and write the ROC. In the Mastercard program, Level 1 merchants need one, and Level 3 and 4 merchants may use one in place of a SAQ.
- An ISA is a staff member trained under the Council program. Mastercard says Level 2 merchants using SAQ A, A-EP or D must engage a QSA or a certified ISA.
- An ASV scan is an external vulnerability scan by an Approved Scanning Vendor. Where it applies, it runs at least every three months, and your SAQ says whether it does.
Rules differ by brand and acquirer, so treat this as a map and not a ruling. To choose among providers, see who does what in PCI DSS.
Common level and SAQ mistakes
- Assuming a hosted checkout means SAQ A: check the eligibility criteria against your actual page.
- Counting one brand only: each brand sets its own thresholds.
- Picking the shortest SAQ: choose by how card data flows, not by length.
- Ignoring a second channel: a terminal and a website can need different handling.
- Reusing an old SAQ version: the v4.0 SAQs retired on 31 December 2024.
- Assuming last year’s answers carry over: the v4.0.1 update added a requirement to SAQ A.
- Not asking the acquirer: the acquirer is who accepts the submission.
- Forgetting growth: volume or a new channel can change your level.
Related PCI DSS guides
PCI levels and SAQ questions buyers ask us
What are the PCI DSS merchant levels?
Who decides my PCI level?
What does a Level 1 merchant have to do?
What is a SAQ?
Which SAQ do I need?
Does using a hosted checkout mean I can use SAQ A?
What is SAQ D?
What if I take cards in several ways?
Can I use a QSA instead of a SAQ?
What is the difference between a SAQ, a ROC and an AoC?
How often do I have to revalidate?
Can my level or SAQ change?
Know your level and SAQ? Get matched with the right provider.
Free for buyers · provider-funded introductions · Reviewed October 2026 by the ZCyberSecurity compliance team