Which PCI SAQ applies to your business
The PCI SAQ a small business fills out depends on how card numbers travel from the customer to the payment company. A checkout page that comes entirely from your processor points to SAQ A, a terminal on a phone line to SAQ B, a terminal with its own internet connection kept apart from your office computers to SAQ B-IP, card numbers typed into a payment company's website to SAQ C-VT, and a validated point-to-point encryption terminal to SAQ P2PE. A setup that misses any eligibility criterion of the shorter forms falls to SAQ D, which has more than eight times as many requirements as SAQ A. Your acquirer, the bank behind your merchant account, has the final say, so confirm the form with it or your processor before you start.
What a PCI SAQ is
PCI DSS, the Payment Card Industry Data Security Standard, is meant for every business that stores, processes or transmits cardholder data, or could affect its security, as each PCI SSC self-assessment questionnaire puts it. A self-assessment questionnaire, or SAQ, is the PCI Security Standards Council's form for checking your business against it, with an Attestation of Compliance that you sign. The Council's FAQ 1215 calls SAQs validation tools and says you must meet all of an SAQ's eligibility criteria to use it.
There are nine SAQs for merchants, each written for one kind of setup, so picking the right one decides whether you answer 21 requirements or 233. The full guide to PCI compliance for small businesses covers the standard itself. This post is about choosing the form.
Who decides which SAQ you file
The PCI Security Standards Council writes the SAQs but doesn't collect them. Every SAQ says to submit it to the organization that asked for it, such as an acquirer or a payment brand. FAQ 1215 tells merchants to check with that organization whether they have to submit an SAQ at all and which one fits, and the Council's October 2024 bulletin on the current SAQs says to do it before you start.
So the criteria below tell you which SAQ fits your setup, and your acquirer confirms it. If you signed up through a payment processor, ask its support line or portal.
Each SAQ's criteria are written "for this payment channel." If you take cards two ways, such as at the counter and online, ask whether you file one SAQ per channel or one for both.
How a small business picks its PCI SAQ
Find the row that matches how you take cards. The last two columns are our own count.
| How you take cards | SAQ | Requirements | Pages |
|---|---|---|---|
| Online checkout where the whole payment page comes from your processor, or mail and phone orders handled entirely by the processor | A | 27 | 38 |
| Online store whose own site delivers part of the payment page but never receives the card number | A-EP | 139 | 83 |
| Imprint machine or standalone terminal on a phone line | B | 27 | 34 |
| Standalone approved terminal that connects over the internet, kept apart from your other systems | B-IP | 50 | 48 |
| Card numbers typed one at a time into a payment company's virtual terminal on an isolated computer | C-VT | 54 | 46 |
| Point-of-sale software on an internet-connected computer, isolated, at one location | C | 123 | 77 |
| Terminals from a validated, PCI-listed point-to-point encryption solution | P2PE | 21 | 31 |
| Phone or tablet with a PIN-capable card reader from a validated SPoC solution | SPoC | 22 | 32 |
| Anything else, including a website that receives card numbers or card numbers stored electronically | D | 233 | 118 |
We counted these on October 15, 2026, from the current version of each merchant SAQ listed in the PCI SSC Document Library: SAQ A Revision 1 (January 2025) and the October 2024 editions of the other eight, all for PCI DSS v4.0.1. The count is the numbered PCI DSS requirements, such as 12.10.1, that Section 2 and its Appendix A ask you to answer, not counting section headings. We left out rows marked as additional requirements for service providers or card issuers, and SAQ D's row for the customized approach, which the SAQ says doesn't apply to anyone completing a self-assessment questionnaire. That leaves 233 in SAQ D for a merchant.
Two rows in that table show how much the setup matters. An online store goes from 27 requirements to 139 depending on whether every part of the payment page comes from the processor, which is a decision about how the checkout is built. A countertop terminal can go from 50 to 233 if it sits on the same network as the office computers with nothing separating them, because no shorter SAQ fits that setup as written.
The eligibility criteria for each SAQ
You have to meet every criterion of an SAQ to use it. Every SAQ except D also requires that you don't store card data electronically and that any card data you keep is on paper, such as printed receipts, and never arrives electronically.
SAQ A for checkout pages run by your processor
SAQ A is for card-not-present sales only: online, mail order and telephone order. It doesn't apply to face-to-face sales. A PCI DSS compliant processor handles all of the card data, and you have confirmed your providers are PCI DSS compliant for the services you use.
For online sales, every element of the payment page delivered to the customer's browser must come only and directly from the processor. Revision 1, published January 2025, added one more criterion: that your site is "not susceptible to attacks from scripts" that could affect your e-commerce systems. The Council's FAQ 1588 from February 2025 says this applies only when your page embeds the processor's payment form, for example in an iframe, and not when you send customers to the processor's own page. You can meet it with techniques like those in PCI DSS requirements 6.4.3 and 11.6.1, or by getting confirmation from the processor that its embedded form, set up as instructed, protects your page from script attacks.
A store using SAQ A still answers for its own website. The SAQ applies Requirements 2, 6, 8 and 11, including quarterly external scans, to the web server holding the page that redirects to the processor or embeds its form.
SAQ A-EP for sites that deliver part of the payment page
SAQ A-EP covers online sales only. Your website doesn't receive card data, but it controls how customers or their card data get to the processor. Each element of the payment page comes from either your website or a PCI DSS compliant provider. If someone else hosts your site, that host has to be PCI DSS compliant too. The SAQ applies its cardholder data environment requirements to your website, which is why it runs to 139.
SAQ B for imprint machines and dial-out terminals
SAQ B is for merchants who take cards only with a manual imprint machine or standalone terminals that dial out over a phone line to the processor. The terminals can't connect to any other system in your business or to the internet. It covers counter sales and mail and phone orders, not online sales.
A terminal that runs on cellular data isn't on a phone line, so it doesn't match SAQ B as written. The Council's FAQ 1313 says a PTS-approved terminal with a cellular or wireless connection may fit SAQ B-IP if you meet all of that SAQ's criteria.
SAQ B-IP for terminals with their own internet connection
SAQ B-IP is for merchants who take cards only on standalone terminals approved under the PCI PIN Transaction Security (PTS) program and listed on the PCI SSC list of approved devices, connected to the processor over IP. The terminal can't depend on a computer, phone or tablet to reach the processor, and the only card data it sends goes to the processor. Secure card readers, the small readers that pair with a phone or tablet, are excluded.
One criterion needs a close read. The terminals must be "not connected to any other systems within the merchant environment." The SAQ says network segmentation, meaning a separate network the terminals sit on, can achieve that, and a footnote allows several terminals to share a network as long as they're isolated from other kinds of systems. A terminal plugged into the same network as the office computers and the customer Wi-Fi, with nothing separating them, doesn't meet it as written. The Wi-Fi and network section of the small business IT guide covers keeping guests on a separate network, and the same router work can give the terminals a network of their own.
If your terminal's PTS approval has expired, the SAQ tells you to check with your acquirer or the payment brands before using it.
SAQ C-VT for a virtual terminal in a web browser
SAQ C-VT is for merchants whose only card processing is a virtual terminal, a payment company's website where staff type in one transaction at a time from the keyboard. The company that hosts it has to be PCI DSS compliant.
The computer used for it has to be isolated in a single location and not connected to other locations or systems, which the SAQ says a firewall or network segmentation can achieve. It can't have software that stores card data, such as batch or store-and-forward programs, or a card reader attached. A front desk PC on the same network as everyone else, with nothing in between, doesn't meet the isolation criterion. It isn't for online sales.
SAQ C for point-of-sale software on the internet
SAQ C is for merchants with a payment application, such as point-of-sale software, and an internet connection on the same device or local network. The payment system can't connect to other systems in your business, which segmentation can achieve. The location can't be connected to other premises, and any local network serves a single store. It isn't for online sales.
SAQ P2PE for validated point-to-point encryption
SAQ P2PE is for merchants who take every payment through a validated solution on the PCI SSC list of point-to-point encryption solutions. The solution's terminals have to be the only systems in your business that store, process or transmit card data, and you have to follow every control in the P2PE Instruction Manual the solution provider gives you. Mail and phone orders can qualify if staff key the card number straight into one of those terminals.
A terminal that encrypts cards qualifies only if its solution is on that list. If the solution's validation has expired, the SAQ sends you to your acquirer.
SAQ SPoC for a phone or tablet with a PIN reader
SAQ SPoC covers card-present sales taken on a phone or tablet with a secure card reader for PIN, as part of a validated Software-based PIN entry on COTS (SPoC) solution. It doesn't cover kiosks, self-checkout, mail and phone orders or online sales, and the payment setup can't connect to your other systems.
SAQ D for everyone else
SAQ D for Merchants is for merchants who can use an SAQ but don't meet the criteria of any other. Its own examples are an online store that accepts card data on its website, a business that stores card data electronically, and a business that fits another SAQ but has more PCI DSS requirements in play. A spreadsheet of card numbers is electronic storage, and card numbers that arrive by email break the paper-only criterion of every other SAQ.
What every SAQ asks for
Ten requirements appear in all nine merchant SAQs, including the 21-requirement SAQ P2PE. Requirement 3.1.1 asks that your processes for protecting stored card data are defined, and 9.4.1, 9.4.1.1 and 9.4.6 that paper with card data is kept secure and shredded. Requirements 12.8.1 to 12.8.5 ask you to keep a list of the providers that handle your card data, have written agreements with them, check their PCI DSS status and record which requirements each one handles. Requirement 12.10.1 asks for an incident response plan. The SAQ's own guidance says a small merchant's plan can be a simple document in the back office listing who to call, reviewed once a year.
Requirement 11.3.2, quarterly external vulnerability scans by a scanning company on the PCI SSC's Approved Scanning Vendor list, appears in SAQ A, A-EP, B-IP, C and D. They aren't in B, C-VT, P2PE or SPoC.
You mark each requirement In Place, In Place with CCW (met with a different safeguard, written up on the compensating controls worksheet), Not Applicable or Not in Place. Every Not Applicable needs a written explanation in Appendix C. Then you sign the attestation in Section 3 and send it, with any scan reports, to whoever asked for it.
Crashcart keeps the computer side of this in place for shops that take cards. It drafts the incident response plan, which says to tell your card processor right away, walks you through putting customer Wi-Fi on a guest network that can't reach your computers or card terminals, and logs each check and fix with the date and the PCI DSS requirement. You confirm the SAQ with your processor, fill it out and sign it. The page for shops and studios lists what it covers for each requirement.
Questions for your processor before you start
Copy these into an email or have them ready for the call:
- Which SAQ do you want from my business, and does it cover every way we take cards?
- When is it due, and do I submit it on your form or in your portal?
- Is my terminal model on the PCI PTS approved list, and is it part of a PCI-listed P2PE solution?
- Does every part of my online checkout page come from you? If I embed your payment form, will you confirm in writing that it protects my page from script attacks?
- Does my SAQ require quarterly scans by an Approved Scanning Vendor, and when is the first one due?
- Can you confirm you're PCI DSS compliant for the services I use, and tell me which PCI DSS requirements you handle for me?
This is general information, not legal advice. For your situation, ask your attorney.
More in this topic
Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.