Which PCI SAQ Do You Need? Find Out Before You Sign
Answer a few questions about how you take cards and where card data ends up. See your likely Self-Assessment Questionnaire for each channel, your merchant level, what that SAQ requires, and the items most often missed. Built for PCI DSS v4.0.1 and the 2025 SAQ A change.
The right SAQ is the shortest one you actually qualify for
A Self-Assessment Questionnaire lists only the PCI DSS requirements that apply to one way of taking cards. Qualify for a short one and you answer a fraction of the standard. File one you do not qualify for, and your Attestation of Compliance does not hold up when your acquirer or an investigator looks.
Two things decide the SAQ: how card data reaches your payment provider in each channel, and whether it lands anywhere on your systems. A hosted payment page keeps your site out of scope. A form your own page builds puts it back in. Card numbers in an inbox or a call recording rule out every short SAQ.
How the finder works: answer for each channel you use. The result shows the likely SAQ for each channel, the most demanding one overall, your merchant level by card brand thresholds, the testing it requires and the items most often missed. Answering Not sure makes the result provisional and tells you what to check.
Your answers stay in your browser. If you ask for the summary, it arrives as a short Word document you can take to your acquirer or QSA. This is a guide to the likely SAQ, not an assessment.
Every PCI SAQ type at a glance
PCI DSS v4.0.1 has ten Self-Assessment Questionnaires. Each one covers only the requirements that apply to one way of taking cards, which is why the right one can be a few pages and the wrong one can be most of the standard. The counts below are the requirement rows in each current SAQ. Many rows have several bullets, so the work is larger than the number suggests.
Only SAQ A, B, P2PE and SPoC stay under about 30 requirements. If your result is A-EP, C or D, the scope work usually pays for itself, because changing how one channel takes cards can drop you to a much shorter SAQ.
SAQ A vs SAQ A-EP vs SAQ D
For online checkout, three SAQs cover almost every merchant. The question that separates them is simple: where does the payment form come from, and does card data ever touch your systems?
SAQ A: the provider supplies the whole payment form
Every element of the payment page that reaches the shopper's browser comes directly from your PCI DSS compliant provider. Your site either redirects the shopper to the provider's hosted payment page, or shows the provider's form inside an embedded frame. Your servers never see a card number.
Example: a professional services firm adds a "Pay invoice" button to its client portal. The button sends the client to the processor's hosted payment page, and the client comes back to a thank-you page. That is SAQ A, at 27 requirements, including quarterly ASV scans of the page with the button.
SAQ A-EP: your site builds or controls the payment form
Card data still goes straight from the shopper's browser to the provider, but your website creates the payment form or runs scripts that shape it. PCI SSC gives two typical cases: a form your site builds that posts card data directly to the processor ("direct post"), and a page where your site loads JavaScript that builds the payment form or controls how card data is sent. Because a compromised page can skim cards before they reach the provider, your web server and everything that can change it comes into scope.
Example: an online retailer wants checkout to match its brand, so its own page renders the card fields and posts them to the processor. That is SAQ A-EP, at about 140 requirements, including an external penetration test and payment page script controls.
SAQ D: card data touches your systems
If card numbers pass through your servers, are stored anywhere in electronic form, or reach staff in ways no shorter SAQ allows, you are on SAQ D. It covers nearly the whole standard.
Example: a distributor takes card numbers by phone, types them into its own order system, and keeps them on file for repeat orders. That is SAQ D. So is a website where card data posts to the merchant's own server before going to the processor.
Moving down is usually a design decision, not a compliance project. Switching checkout to a hosted page or provider-supplied form, replacing stored card numbers with the processor's tokens, and moving phone orders to a provider's virtual terminal or payment link are the common routes. Confirm the new setup with your acquirer before you file, and see PCI DSS compliance consulting if you want the scope checked first.
The 2025 SAQ A eligibility change
On January 30, 2025, the PCI Security Standards Council published a revised SAQ A (v4.0.1 revision 1). The earlier v4.0.1 version of SAQ A was retired on March 31, 2025, the same day the future-dated PCI DSS requirements became mandatory.
What was removed
Requirement 6.4.3: managing every script on the payment page, with an inventory, a reason for each script and a way to confirm its integrity.
Requirement 11.6.1: a change and tamper detection mechanism that alerts on unauthorized changes to the payment page.
Requirement 12.3.1: the targeted risk analysis that supported how often 11.6.1 runs.
What was added
A new eligibility criterion for e-commerce channels. The merchant confirms that its "site is not susceptible to attacks from scripts that could affect the merchant's e-commerce system(s)."
Who the criterion applies to
PCI SSC FAQ 1588, issued in February 2025, says the criterion applies to merchants whose webpage includes the provider's embedded payment form, such as an iframe. It does not apply to merchants that redirect shoppers to the provider's page, or that fully outsource payment, for example by emailing customers a link to pay on the provider's site.
The FAQ gives two ways to meet it:
Use techniques such as those in Requirements 6.4.3 and 11.6.1 to protect your webpage from scripts that target card data, either yourself or through a third party.
Get confirmation from your PCI DSS compliant payment provider that its solution, when implemented according to its instructions, includes techniques that protect your payment page from script attacks.
The FAQ also says that a company whose only service is providing scripts unrelated to payment, which cannot affect the security of card data, is not treated as a service provider for SAQ A.
What did not change
The underlying requirements. PCI SSC stated that the update does not remove or diminish the underlying requirements in PCI DSS. Payment page skimming is still the attack this criterion is about.
Quarterly ASV scans. Requirements 11.3.2 and 11.3.2.1 stay in SAQ A for the page that redirects or embeds the payment form.
Report on Compliance merchants. In August 2026, PCI SSC updated FAQ 1331 to say SAQ eligibility criteria should not be used to decide which requirements apply in a Report on Compliance unless the merchant's acquirer or card brand has reviewed and agreed to it. A Level 1 merchant cannot assume the SAQ A relief carries over.
What to do now
If your checkout uses an embedded payment form, get the provider's written confirmation or put script protection in place before you sign your next attestation. Keep the evidence with your SAQ. If you cannot confirm the criterion, SAQ A-EP is the likely fit, and that is a different questionnaire with roughly five times the requirements. Run the finder above and answer the script question honestly; a provisional result tells you what to check.
PCI SAQ questions, answered
Acquirers and assessors ask for evidence, not policies. We scope PCI environments, test the controls in your actual systems and show what holds up.
Since May 1, 2026, our forensic audits have prevented $2.2M in wire fraud, none of it flagged first by the client's IT team, managed service provider, bank or security tools.