PCI DSS for Small Merchants: Which Self-Assessment Questionnaire Applies?
Short answer: The Payment Card Industry Data Security Standard (PCI DSS) requires merchants that accept cards to validate their compliance, and most small merchants do this with a Self-Assessment Questionnaire (SAQ). The right SAQ depends on how you take card payments. A merchant that redirects customers to a payment provider's hosted page usually completes SAQ A. A merchant whose website controls the payment page but passes card data straight to a provider usually needs SAQ A-EP. Merchants that store, process or transmit card data on their own systems fall under the longer SAQ D. Choose the form that matches your setup, answer honestly, and keep the evidence on file.
Start with how cards are taken
The question is not how much you sell but where card data passes. Map the path for a single payment from the customer's keyboard to the bank. Write it down in four or five steps. Most mistakes happen because the owner assumes the payment provider takes all the responsibility, when the way the page is built decides who is in scope.
Consider a fictional florist called Petal and Post that sells bouquets through a website. The customer clicks Buy, is sent to a page hosted by the payment provider, pays, and returns to a thank-you page on the florist's site. The florist never sees the card number. That flow points toward SAQ A, but only if the florist meets the conditions listed in the questionnaire.
Which form for which setup
These are the three forms small merchants most often need:
| Setup | Likely form | What it means |
|---|---|---|
| Fully outsourced: the provider hosts the whole payment page or redirects you to it | SAQ A | Shortest form, the provider handles card data entirely |
| Partly outsourced: your site loads the payment fields, but the provider's script or iframe carries the card data | SAQ A-EP | Longer form, covers your web server and the scripts on the page |
| Your systems store, process or transmit card numbers | SAQ D | Full set of requirements for merchants with their own card data environment |
There are other forms for specific cases, such as payment terminals, so check the official list rather than assuming these three cover you.
Hosted checkout and SAQ A
To qualify for SAQ A, the card data must never touch your systems, and your website must not affect the payment page. The usual conditions include that you use a hosted page or an iframe that the provider controls, that you do not receive or store card numbers, and that your site has no scripts that could interfere with the payment fields.
Check the provider's documentation on how their page is delivered. A small change, such as adding a third-party script on the checkout page, can move you from SAQ A to a longer form.
Script integrity on payment pages
If your payment page loads any script from your own site or a third party, PCI DSS version 4.0 includes requirements about managing those scripts. Merchants are expected to know which scripts run on the payment page, to authorise them and to check that they have not been changed without notice. A practical step is to list every script on the checkout page, the owner of each script and the reason it is needed.
For example, a fictional bike shop called Spoke Works uses a chat widget and an analytics tag on checkout. The owner removed the chat widget from the checkout page, kept the analytics tag with a note of its purpose, and recorded the review date.
Steps to complete the questionnaire
- Confirm your merchant level and whether your provider or acquiring bank asks for a particular form or an attestation.
- Draw the card-data flow on one sheet of paper.
- Choose the SAQ that matches the flow, and read its eligibility criteria.
- Gather evidence: provider documents, screenshots of your checkout pages, your script list and any policies.
- Answer each question honestly. Mark any question that does not apply, with a short reason.
- Sign the attestation of compliance, if it is required for your form.
- Submit to your acquiring bank or provider as they request, and keep the completed form.
- Repeat the process each year, and whenever you change your checkout.
What to keep on file
Keep the completed SAQ, the attestation, your card-data flow diagram, the list of checkout scripts, copies of the provider's compliance documents, and a short log of any changes to the checkout. A password manager entry showing who can log in to the provider dashboard is also useful. Many banks ask for these documents when they review your account, so having them ready saves time.
Common mistakes
- Choosing SAQ A because the provider says it is "PCI compliant", without checking your own setup
- Adding a marketing tag to the checkout page and forgetting to update the questionnaire
- Storing card numbers in a spreadsheet, a support ticket or an email
- Using a payment link that the provider has not configured as hosted
- Failing to document why each checkout script is needed
A short checklist
- Card-data flow drawn and dated
- SAQ type chosen against its eligibility rules
- Checkout scripts listed with owner and reason
- Provider attestation saved
- Attestation signed if required
- Annual review date added to your calendar
- Changes to checkout logged
FAQ
Do I need to complete PCI DSS if I use PayPal or Stripe?
Probably, yes, because you still have a duty to validate, even when a provider handles most of the card data. The form depends on how your page is built.
Is a yearly scan required?
Some SAQs require quarterly external vulnerability scans, usually for SAQ types with more exposure. Check the requirements for your form and your acquirer, because the rules are not the same for every merchant.
Can I just ask the provider to fill in the form?
Your provider can explain the setup and send its own attestation, but the merchant is responsible for the answers about its own systems and pages.
What happens if I fail to complete it?
Your acquiring bank may charge fees or restrict card acceptance. Ask your bank what they expect and when, and keep proof of your submission.
If you would like help checking which scripts load on your checkout page and documenting your setup, reach out through our enquiry page.