PCI Compliance for a Small Merchant: Questionnaire Types and What They Ask

A card terminal on a shop counter with a contactless card held near it.

A small merchant that takes cards is covered by the Payment Card Industry Data Security Standard whether the business processes ten transactions a week or ten thousand. The PCI Security Standards Council, the body that maintains the standard, states on its merchants page that the standard applies to all entities that process payments, whatever their size or transaction volume. What changes with size and setup is how compliance is proven. For most small merchants, proof takes the form of a self-assessment questionnaire, or SAQ, and there is more than one version.

Which PCI SAQ Do You Actually Need?, SecurityMetrics, Inc. on YouTube

Picking the wrong version is a common stumbling block, partly because the names are letters and partly because the right one depends on how card data physically travels through the business. This post sets out the merchant versions, what each is built for, and who actually decides which one gets filed. Everything here comes from PCI Council documents fetched on the date noted under Sources; where a document was an older edition, the text says so.

What an SAQ is and who decides which one applies

The Council’s own FAQ defines SAQs as “validation tools” used by eligible merchants and service providers to carry out and report a PCI DSS self-assessment. Each one targets a specific kind of environment, and an organization must meet every eligibility criterion of a given SAQ to use it. The FAQ states: “All the eligibility criteria for a particular SAQ must be met to use that SAQ.”

Whether a merchant has to submit anything at all is not the Council’s call. The merchants page says that whether a small merchant must validate compliance is determined by the individual payment brands, and advises asking the acquirer (the merchant bank) or the relevant brand about validation and reporting. A second FAQ, on why there are multiple SAQs, ties the choice to how a merchant stores, processes or transmits cardholder data, and points to the entity that receives the SAQ, usually the acquirer, as the one that can confirm which version applies.

In practice, then, three parties are involved: the merchant, which knows how its equipment is wired; the acquirer or processor, which knows what it requires; and the Council’s documents, which define the versions. The processor behind a counter system, such as the one described in the post on taking card payments with Square, is a natural first place to ask.

The merchant questionnaires, one setup at a time

The Council’s older guidance document, Understanding SAQs for PCI DSS v3, gives one-line descriptions of each type. The descriptions below draw on that document and on the eligibility sections of the PCI DSS v4.0 versions, each linked where it is discussed.

SAQ A. For card-not-present merchants (e-commerce or mail/telephone order) that have fully outsourced all cardholder data functions. The v4.0 SAQ A requires that all account data processing goes to a PCI DSS-compliant third-party service provider, that nothing is stored, processed or transmitted electronically on the merchant’s own systems, and that the merchant has reviewed each provider’s Attestation of Compliance. Any retained account data is on paper only. The document states: “This SAQ is not applicable to face-to-face channels.”

SAQ A-EP. For e-commerce merchants that outsource payment processing to validated third parties but whose own website can affect the security of the payment transaction, even without directly receiving card data. The description comes from the older v3 guidance document; the v4.0 A-EP text was not fetched.

SAQ B. For merchants using only imprint machines or standalone dial-out terminals. Under the v4.0 SAQ B, dial-out terminals connect by phone line, are not connected to the Internet or to any other system in the merchant environment, and no account data is kept in electronic form.

SAQ B-IP. For merchants using only standalone, PCI-listed payment terminals that connect to the processor over an IP connection. The v4.0 SAQ B-IP says the only transmission of account data is from the approved terminal to the processor, that the terminal must not rely on another device such as a computer, phone or tablet to reach the processor, and that merchants using secure card readers are not eligible.

SAQ C-VT. For merchants who key one transaction at a time into a virtual terminal hosted by a compliant third party. The v4.0 SAQ C-VT specifies an isolated computing device with no software installed that causes account data to be stored and no attached hardware used to capture or store account data.

SAQ C. For merchants whose point-of-sale or other payment application systems connect to the Internet without storing account data electronically. The v4.0 SAQ C requires that the payment application is not connected to any other systems in the merchant environment, and that any local network serves a single store only.

SAQ P2PE. For merchants that process account data only through a validated, PCI-listed point-to-point encryption solution. In the v4.0 SAQ P2PE, merchants have no access to clear-text account data on any computer system and have implemented all controls in the P2PE Instruction Manual supplied by the solution provider. It does not apply to e-commerce channels.

SAQ D. The catch-all. The v4.0 SAQ D for merchants applies to eligible merchants that do not meet the criteria for any other type, with examples that include e-commerce merchants that accept cardholder data on their own website and merchants that store cardholder data electronically. The merchant version is meant for what the other types cannot cover.

Service providers are handled separately: the FAQ states that SAQ D for Service Providers is “the ONLY SAQ for SAQ-eligible service providers,” and that all other SAQs are for merchants only.

A desk with a laptop, blank checklist and pen.

What the eligibility criteria say about real counter setups

The criteria read like an inventory of equipment, which is the point. A few common arrangements map onto them in a rough way, though only the acquirer can confirm a match.

A shop with a standalone countertop terminal that talks to the processor over the network and to nothing else resembles the B-IP description. A restaurant whose point-of-sale software runs on a networked computer and also sends card transactions across the Internet resembles the C description, which assumes the payment application and Internet connection share a device or local network. A merchant whose terminals are part of a validated encryption program resembles P2PE, and the Council’s document ties that to having no clear-text account data on any system. An online store that sends buyers to a hosted payment page of a compliant provider sits closest to SAQ A.

Where setups drift out of a category. Criteria are strict about connections and software. A terminal that depends on a tablet to reach the processor falls outside B-IP, according to the document’s wording. A computer with software that stores card numbers falls outside C-VT. A POS that connects to other systems in the merchant environment, such as a back-office machine on the same network, falls outside C. When none fits, SAQ D is the default, and the effort rises accordingly.

Two conditions recur across nearly every version. Account data may be retained only on paper, such as printed reports or receipts, and not received electronically. And the questionnaires covering face-to-face and phone channels generally say they do not apply to e-commerce.

Default credentials also come up. The SAQ A document applies Requirement 2.2.2, concerning vendor default accounts, to e-commerce merchants’ web servers. Password handling in general is the subject of the post on password managers for a small business.

A router and switch in a back office with tidy Ethernet cables.

Online stores: the SAQ A script change

For online merchants, SAQ A changed in early 2025. The PCI Council’s blog post of 30 January 2025, Important Updates Announced for Merchants Validating to Self-Assessment Questionnaire A, reports that Requirements 6.4.3 and 11.6.1 (payment page security) and 12.3.1 (the targeted risk analysis supporting 11.6.1) were removed from SAQ A. In their place is a new eligibility criterion: merchants must confirm their site is “not susceptible to attacks from scripts that could affect the merchant’s e-commerce system(s).”

The post states the October 2024 SAQ A was retired on 31 March 2025, and that the changes affect how compliance is reported without removing or diminishing the underlying PCI DSS requirements.

A Council FAQ, How does an e-commerce merchant meet the SAQ A eligibility criteria for scripts?, narrows the scope. The script criterion applies only to merchants whose page includes a provider’s embedded payment page or form, such as an iframe, and not to merchants that redirect customers to the provider. A merchant can meet the criterion either with techniques like those in Requirements 6.4.3 and 11.6.1, or by obtaining confirmation from a compliant provider that its solution, implemented as instructed, protects the payment page from script attacks. The FAQ also says a provider of third-party scripts is not a payment service provider for SAQ A purposes if its only service is non-payment scripts that cannot affect cardholder or sensitive authentication data.

Website builders and hosted checkouts matter here, since the choice between redirect and embedded form determines which wording applies. The comparison in the post on free and paid website builders for a small shop is a starting point for that decision.

A hand entering a payment on a smartphone beside a parcel.

Versions, dates and where to get the current forms

The Council’s Document Library page lists PCI DSS v4.0.1 among its current standards. The versions of SAQs A, B, B-IP, C-VT, C, P2PE and D reviewed for this post are the v4.0 editions, each stamped as published in April 2022; the Council has issued later revisions, as the January 2025 SAQ A update shows. The v4.0.1 SAQ A PDF could not be fetched for this post, so the criteria quoted for it come from the v4.0 text plus the Council’s blog and FAQ about the update.

The practical conclusion is procedural. The current form comes from the Council’s Document Library, the right form is confirmed with the acquirer or payment brand, and eligibility is judged against the equipment and connections actually in use, not against what was installed years ago. After a change such as adding a tablet-based ordering app or moving to a new processor, the eligibility check starts over.

The question lists inside each SAQ run to many requirement items, mapped to the numbered sections of PCI DSS. Those item-by-item lists were not reproduced from the PDFs here, so what each version asks is summarized through its eligibility criteria and the specific requirements called out above, not question by question.

This post is general information about published standards and not a determination of which questionnaire applies to any particular business.

For informational purposes only — consult a licensed attorney, tax professional or financial advisor.

Sources

All pages fetched at the time of writing.