The PCI DSS Self-Assessment Questionnaire (SAQ) you complete depends on how you accept payment cards and whether you store cardholder data. If every payment function is outsourced to a validated third party, you are probably SAQ A. If your own website affects the payment page, SAQ A-EP. If you store cardholder data electronically, SAQ D. Your merchant level is a separate question, and it depends on how many transactions you process a year.

Both answers come from scoping: working out which people, processes, and systems touch cardholder data or could affect its security. If the scope is wrong, the questionnaire you chose does not describe your real environment.

Step 1: scope the cardholder data environment

PCI DSS applies to every entity that stores, processes, or transmits cardholder data. The cardholder data environment (CDE) is the set of system components, people, and processes that do one of those three things. Scope reaches beyond the CDE in two directions:

  • Connected-to systems: anything with network connectivity to the CDE, such as an administrator workstation or a jump host.
  • Security-impacting systems: anything that could affect the security of the CDE without touching card data, such as authentication servers, logging, patching, and anti-malware management.

Network segmentation is not a PCI DSS requirement, but it is the main way to reduce scope. A system is out of scope only if it is properly segmented from the CDE and that isolation has been verified. PCI DSS requires segmentation controls to be tested, so a flat network with a firewall rule nobody has checked does not take anything out of scope.

Step 2: determine your merchant level

Merchant levels are set by the card brands, not by the PCI Security Standards Council, and your acquiring bank makes the final call. The thresholds most often cited are Visa’s:

Visa merchant levels by annual transaction volume
LevelAnnual Visa transactionsTypical validation
1More than 6 millionAnnual Report on Compliance by a Qualified Security Assessor, plus quarterly ASV scans
21 million to 6 millionAnnual SAQ, Attestation of Compliance, and quarterly ASV scans
320,000 to 1 million e-commerce transactionsAnnual SAQ, Attestation of Compliance, and quarterly ASV scans
4Fewer than 20,000 e-commerce transactions, or up to 1 million in totalAnnual SAQ and quarterly ASV scans, as the acquirer requires

The level tells you how you validate. It does not change the requirements themselves, so a Level 4 merchant that stores cardholder data has the same obligations to protect it as a Level 1 merchant. Other brands set their own thresholds and rules, so confirm yours with your acquirer.

Step 3: choose the SAQ

PCI DSS Self-Assessment Questionnaire types and who each is for
SAQWho it is for
ACard-not-present merchants (e-commerce or mail and telephone order) that have fully outsourced all cardholder data functions to validated third parties. No electronic storage, processing, or transmission of cardholder data on the merchant’s systems.
A-EPE-commerce merchants that outsource payment processing but run a website that can affect the security of the payment transaction. The site does not receive cardholder data itself.
BMerchants using only imprint machines or standalone dial-out terminals, with no electronic cardholder data storage.
B-IPMerchants using only standalone, PTS-approved payment terminals with an IP connection to the processor, and no electronic storage.
C-VTMerchants that manually enter one transaction at a time into a web-based virtual terminal from an isolated computer, with no electronic storage.
CMerchants with payment application systems connected to the internet, and no electronic cardholder data storage.
P2PEMerchants using only hardware terminals within a validated, PCI-listed point-to-point encryption solution, with no electronic storage.
D (Merchants)Every merchant that does not fit the types above, including any merchant that stores cardholder data electronically.
D (Service Providers)Service providers that a card brand has defined as eligible to complete an SAQ.

Work through the list in order and rule each type out with a reason. The question that settles most cases is whether you store cardholder data electronically. If you do, every narrower SAQ is off the table and you are completing SAQ D.

Common scoping mistakes

  • Assuming a PCI-certified cloud provider makes you compliant. Hosting on a compliant provider covers the infrastructure the provider runs. It does not cover your website, your shopping cart, your stored data, or your connected systems.
  • Claiming SAQ A while your site still controls how the payment page is delivered. If your server’s code can affect the transaction, you are A-EP.
  • Leaving security-impacting systems off the list. The patch server, the logging platform, and the directory service are in scope if they can affect the CDE.
  • Treating an untested segment as out of scope.
  • Storing data you do not need. The most effective way to reduce scope is to stop storing cardholder data at all.

A worked example

In a collaborative course project, my team assessed an online retailer processing about 1.2 million card transactions a year, with credit cards stored in an AWS-hosted WordPress storefront. The transaction volume made it a Level 2 merchant: above 1 million, below 6 million. Because it stored cardholder data, we ruled out SAQ A, A-EP, and C one by one, and SAQ D was the only fit.

Two other details mattered. The physical stores used bank-provided terminals that did not store customer information, so they did not need a separate SAQ. And AWS being a PCI DSS Level 1 service provider did not move the website, the shopping cart, or the stored data out of the retailer’s own scope.

Frequently asked questions

Which PCI SAQ do I need if I store credit card numbers?
SAQ D for Merchants. Every narrower SAQ requires that you do not store cardholder data electronically, so storing it puts you in SAQ D regardless of how you accept payments.
What is the difference between SAQ A and SAQ A-EP?
Both are for e-commerce merchants that outsource payment processing. SAQ A applies when every element of the payment page comes directly from the validated third party. SAQ A-EP applies when your own website can affect the security of the payment transaction, even though it never receives the card data.
Does using AWS make me PCI compliant?
No. AWS is a PCI DSS Level 1 service provider, which covers the infrastructure it operates. You remain responsible for everything you build and store on it, including your website, payment pages, stored cardholder data, and connected systems.
Is network segmentation required by PCI DSS?
No, but without it your entire network is in scope. Segmentation reduces scope only when it effectively isolates the cardholder data environment and that isolation has been tested.
Who decides my PCI merchant level?
The payment card brands define the levels, and your acquiring bank determines which one applies to you, based mainly on annual transaction volume.

Sources