Which SAQ do I need?
Which SAQ do I need?
Most merchants are handed a questionnaire name and left to work out what it means. This page walks the same six questions our free Scope Check asks, in the same order, and gives you the likely answer at each branch. It takes about three minutes to read and it is not a substitute for the real thing — the Scope Check does the full version and gives you a written result.
One thing to know before you start: the answer is decided by how card data reaches you, not by how big you are or what you sell. Two shops on the same street can need different questionnaires.
Question 1
Do you handle card data for other businesses?
Not your own card sales. Other businesses' — because you process payments on their behalf, host their checkout, run their terminals, or manage their systems.
Yes → SAQ D (likely).
Service providers are usually placed on SAQ D by their acquirer, and the service-provider version is longer than the merchant one. Your processor's letter decides which level you are placed at; most service providers are placed at Level 1 or Level 2, and at Level 1 a QSA-led assessment is commonly required. CardComply does not do that work — we help you get ready for it and manage the compliance around it.
No → Question 2.
Question 2
Do you store card numbers yourself?
Be strict here. "Store" means the number or the full track data sits in your system: your database, your spreadsheets, a filing cabinet of paper slips, an email inbox, a photo on someone's phone.
Yes, we store it → SAQ D.
The full merchant questionnaire, not a subset. Storing card data yourself brings the whole requirement set into scope, including the ones most small businesses have never documented. This is also the case where the cheapest useful move is usually to stop storing it — moving to a hosted payment page can take you off SAQ D entirely.
No, a third party stores it for us → Question 3.
No, it only passes through our site → SAQ A-EP (clear), if you take payments online.
Skip ahead to the A-EP section below; it is the single most common misclassification we see.
Question 3
How do you actually take the card?
Pick the ones that apply. This is where most people go wrong, because they answer for their main channel and forget the second one.
Online checkout on your own site
the customer enters card details on a page you control, which then hands them to a payment provider.
Hosted checkout or payment page
Shopify, Stripe Checkout, Square Online, PayPal. The customer types into the provider's page, not yours.
In-person card terminal
a countertop or portable device.
Virtual terminal or keyed entry
someone types the number into a browser screen.
Phone or mail order
same idea, order taken by a person.
Mobile card reader
a reader plugged into a phone or tablet.
Question 4
Which branch are you on?
Only a hosted checkout, and the customer types into the provider's page — never yours → SAQ A.
The shortest questionnaire, roughly a dozen requirements. Most of it is about the hosted page and what the provider is responsible for. The gap we see most often at this level is simply having no written policy at all, which SAQ A does ask for.
Your own site takes the card details before passing them on → SAQ A-EP.
The website is in scope. Hosting the payment page elsewhere does not take you out of it. Expect written policies, a change process for your site, and evidence of how the checkout is built — your developer usually has to answer a handful of questions.
Online and in-person → likely two questionnaires.
Commonly SAQ A or A-EP for the website plus SAQ B-IP for the terminals. Filing one and assuming it covers both is a frequent finding.
Only a card terminal, no website payments → SAQ B-IP, or SAQ B if the terminals are dial-up.
Almost every current terminal is IP-connected, so expect B-IP. It covers network segmentation, device configuration, patching, and a written policy for the terminal estate. The usual finding: terminals sitting on the same network as everything else, with no documented separation.
Only keyed entry, no website, no terminal → SAQ C-VT, or SAQ C.
C-VT is for keying through a browser-based virtual terminal. If the keyed entries run through a payment application installed on a computer rather than a browser, the answer is SAQ C. The usual finding at this level is the computer used for keying also being used for email and browsing, and never patched.
Not sure → start with SAQ A as a provisional answer, then confirm it.
Guessing A when you are actually A-EP is the expensive mistake, so treat a guess as a question to settle, not an answer.
Question 5
How many card transactions a year?
This sets your merchant level, which is a different thing from your SAQ type. Your processor uses it to decide how much scrutiny you get.
- Under 20,000
- Level 4
- 20,000 to 1 million
- Level 3
- 1 to 6 million
- Level 2
- Over 6 million
- Level 1
Most small and mid-size merchants are Level 3 or Level 4 and self-assess. Your SAQ type comes from the questions above; the level comes from the volume.
Question 6
What does it actually take?
Realistic effort, from the merchants we have worked with. Project work is quoted from one published band — SAQ Done Right $1,500–$3,500, Readiness Review $2,500–$5,000 — and where your own case lands inside it is set by scope, not by which questionnaire you file. The retainer tier, by contrast, is fixed by your SAQ type and location count, so that one is exact:
SAQ A
a few hours of your time over a week or two, plus the policies. Retainer $500/mo.
SAQ A-EP
about a week of elapsed time with your developer involved. Retainer $1,000/mo.
SAQ B / B-IP
a few hours, plus a conversation with whoever manages your network for B-IP. Retainer $1,000/mo single location, $1,500/mo multiple locations.
SAQ C / C-VT
an hour or two for C-VT, half a day plus vendor documentation for C. Retainer $1,000/mo single location, $1,500/mo multiple locations.
SAQ D
a week or more, with input from whoever runs your systems. Retainer $1,500/mo.
What it costs to get this wrong
Stated plainly, because it is usually the reason someone finally calls:
- Your processor can charge non-compliance fees on top of your normal processing rate.
- Your acquirer can fine you as well, and the amount is set by your acquirer and by how long the gap runs — so the longer it sits, the more it costs.
- If there is a breach, you carry the liability: card replacement, forensic investigation, and the assessments that follow. For a small business, that number is usually larger than years of compliance work.
None of that is a threat. It is the schedule your bank is working from.
Six questions, one written answer.
The free PCI Scope Check asks the full version of what is above — payment channels, who touches the card data, locations, volume — and gives you your likely SAQ type, your merchant level, what the questionnaire asks for, and the retainer tier that matches, with the price. Twenty minutes on the phone if you want to talk it through. No charge, ever.
CardComply provides consulting, readiness, and compliance-management services. CardComply is not a QSA company and does not perform PCI DSS assessments or issue Reports on Compliance or certifications. CardComply never collects or stores cardholder data.
