PCI DSS Compliance for Small Business (v4.0.1): Which SAQ Do I Need?
Last updated: 2026-10-07
Short answer: every business that takes card payments must follow PCI DSS — it's required by the card brands through your merchant agreement, not by law. Most small merchants prove it with an annual Self-Assessment Questionnaire (SAQ). Which one depends on how card data reaches your processor: a hosted checkout means SAQ A (27 requirements); storing card numbers yourself means SAQ D (250). Use the selector below, then download the official SAQ from the PCI SSC.
PCI DSS status
Stableas of Oct 7, 2026- Jun 11, 2024PCI DSS v4.0.1 published (a limited revision of v4.0). source
- Dec 31, 2024PCI DSS v4.0 retired — v4.0.1 is the only active version. source
- Jan 30, 2025SAQ A Revision 1: Requirements 6.4.3, 11.6.1 and 12.3.1 removed; new eligibility criterion that the merchant's site is not susceptible to script attacks. source
- Mar 31, 2025All 51 future-dated v4.0 requirements became mandatory (script management 6.4.3, MFA for all CDE access 8.4.2, 12-character passwords 8.3.6, authenticated internal scans 11.3.1.2, and others). source
- Jun 3, 2026PCI SSC opened a Request for Comments (to Jul 20, 2026) on v4.0.1 for 'the next iteration' — no new version or date has been announced. source
Which SAQ do I need? (free selector)
All PCI DSS v4.0.1 SAQ types compared
| SAQ | Who it's for | Requirements | Quarterly ASV scans | Pen test |
|---|---|---|---|---|
| SAQ A | Card-not-present merchants that fully outsource all account-data handling to a PCI DSS compliant processor | 27 | Yes | No |
| SAQ A-EP | E-commerce merchants whose own website controls or affects the payment page but never receives card data | 139 | Yes | Yes |
| SAQ B | Merchants using only imprint machines or standalone dial-out terminals (no internet) | 28 | No | No |
| SAQ B-IP | Merchants using only standalone, PCI-approved IP-connected payment terminals | 50 | Yes | No |
| SAQ C-VT | Merchants that key one transaction at a time into a processor's web-based virtual terminal on an isolated computer | 54 | No | No |
| SAQ C | Merchants with an internet-connected POS system or payment application on a single-store network, no electronic storage | 122 | Yes | No |
| SAQ P2PE | Merchants that take cards only through terminals from a PCI-listed, validated point-to-point encryption (P2PE) solution | 22 | No | No |
| SAQ SPoC | Card-present merchants using a phone/tablet with a secure card reader that is part of a PCI-listed SPoC solution | 23 | No | No |
| SAQ D for Merchants | Every merchant that doesn't meet another SAQ's criteria — including anyone storing card data electronically | 250 | Yes | Yes |
Requirement counts are the numbered PCI DSS requirements in Section 2 of each SAQ, counted by us from SAQ A r1 (January 2025) and the October 2024 v4.0.1 SAQs; Appendix A2.1.1 (SSL/early TLS terminals) appears additionally in B-IP, C and D. Some requirements apply only to parts of your environment (e.g., paper records). Service providers use SAQ D for Service Providers. PCI SSC library
Merchant levels: Visa (3) and Mastercard (4)
| Visa level | Annual Visa transactions |
|---|---|
| Level 1 | More than 6,000,000 Visa transactions |
| Level 2 | 1,000,001 – 6,000,000 |
| Level 3 | 1 – 1,000,000 (Levels 3 and 4 were consolidated on Apr 25, 2024) |
| Mastercard level | Criteria → validation |
|---|---|
| Level 1 | More than 6 million total combined Mastercard and Maestro transactions a year, or meets Visa's Level 1 criteria, or designated by Mastercard. Annual Report on Compliance (ROC) signed by a QSA, an ISA, or (unless prohibited) an executive officer. |
| Level 2 | More than 1 million and up to 6 million total combined Mastercard and Maestro transactions, or meets Visa's Level 2 criteria. Annual SAQ — and if it's SAQ A, A-EP or D, it must also be validated by a QSA or PCI-certified ISA (or do a ROC). |
| Level 3 | More than 20,000 and up to 1 million combined Mastercard and Maestro e-commerce transactions, or meets Visa's Level 3 criteria. Annual SAQ. |
| Level 4 | All other merchants. Annual SAQ; validation to Mastercard is not required unless law requires it — but your acquirer may require it. |
Sources: Visa What To Do If Compromised (Jun 2026) · Mastercard SDP program. Any merchant with a confirmed compromise can be moved to Level 1. Your acquirer sets your actual validation requirements.
The 12 PCI DSS requirements in plain English
| # | Requirement | What it means for a small merchant |
|---|---|---|
| 1 | Install and maintain network security controls | Firewalls/security groups between your payment systems and everything else. |
| 2 | Apply secure configurations to all system components | Change vendor-default passwords; turn off what you don't need. |
| 3 | Protect stored account data | Don't keep card data you don't need; never keep CVV/track data after authorization. |
| 4 | Protect cardholder data with strong cryptography during transmission | TLS everywhere; never send card numbers by email or chat. |
| 5 | Protect all systems and networks from malicious software | Anti-malware kept current; anti-phishing measures (5.4.1). |
| 6 | Develop and maintain secure systems and software | Patch promptly; for payment pages, inventory and authorize every script (6.4.3). |
| 7 | Restrict access by business need to know | Only the people who need card data get it. |
| 8 | Identify users and authenticate access | Unique IDs, 12-character passwords (8.3.6), MFA into the cardholder data environment (8.4.2). |
| 9 | Restrict physical access to cardholder data | Lock up paper records; inspect terminals for skimmers (9.5.1). |
| 10 | Log and monitor all access | Keep and review logs; automated log review (10.4.1.1). |
| 11 | Test security regularly | Quarterly ASV scans; pen tests and payment-page tamper detection where your SAQ requires them. |
| 12 | Support information security with policies and programs | Policies, training, vendor list with PCI status, incident response plan. |
How to get compliant, step by step
- Shrink your scope first. Use a hosted checkout or payment links online, validated P2PE terminals in person, and never keep card numbers in email, spreadsheets or notes. Fewer systems touching card data means a shorter SAQ.
- Pick your SAQ with the selector above and confirm every eligibility statement — if one doesn't fit, that SAQ doesn't either. Ask your acquirer or processor if unsure; many processors tell you which SAQ their product supports.
- Close the gaps the SAQ lists (passwords and MFA, patching, policies, vendor list, incident response plan). Use the Excel plan for owners and dates.
- Run quarterly ASV scans if your SAQ includes 11.3.2, using a vendor from the PCI SSC ASV list. Rescan until each quarter passes.
- Complete the SAQ and sign the Attestation of Compliance (AOC) every year; submit them (and scan reports) the way your acquirer asks.
If you have a breach: Visa's published rules
- Report a suspected or confirmed compromise within three calendar days — Visa can assess up to $100,000 per incident for missing it.
- For Level 3 merchants, Visa's non-compliance assessments under these rules start at $5,000 (up to 100,000 transactions), $10,000 (100,000–500,000) or $25,000 (500,000–1,000,000), and can rise to $100,000.
- Expect to hire a PCI Forensic Investigator; investigations of Level 3 merchants still open after four full months carry a one-time $3,000 fee.
These are assessed on your acquirer (the Visa member) and passed through under your merchant agreement. Visa WTDIC, effective Jun 25, 2026
Frequently Asked Questions
›Does PCI DSS apply to my small business?
Yes, if you accept, process, store or transmit payment card data — or can affect its security. PCI DSS isn't a law; it's required by the card brands through your merchant agreement with your acquirer or processor. Size doesn't exempt you; it changes how you prove compliance (usually an annual Self-Assessment Questionnaire).
›Which PCI SAQ do I need?
It depends on how each payment channel collects card data. Hosted checkout pages or payment links: SAQ A (27 requirements). Embedded iframe forms: SAQ A if you can confirm your page isn't susceptible to script attacks (FAQ 1588), otherwise SAQ A-EP (139). Your page builds the form or posts card data: A-EP. Dial-up terminals: SAQ B (28). Standalone IP terminals: B-IP (50). Web virtual terminal on an isolated computer: C-VT (54). Segmented single-store POS: C (122). Validated P2PE terminals: P2PE (22). PCI-listed phone/tablet SPoC solution: SPoC (23). Anyone storing card data electronically or not fitting another SAQ: D (250).
›What changed for SAQ A in 2025?
PCI SSC's January 2025 revision (SAQ A r1) removed Requirements 6.4.3 and 11.6.1 (payment-page script controls) and 12.3.1 from SAQ A and added an eligibility criterion: merchants that embed a processor's payment form must confirm their site isn't susceptible to script attacks. FAQ 1588 says you can confirm that either with your own script-protection techniques or with written confirmation from your processor that its embedded form protects your page when implemented as instructed. The criterion doesn't apply to redirects or payment links.
›Do SAQ A merchants need quarterly ASV scans?
E-commerce SAQ A merchants generally do: in PCI DSS v4.0.1, SAQ A includes Requirement 11.3.2 (quarterly external scans by an Approved Scanning Vendor) for the merchant web server that hosts the redirect or the embedded payment form. Mail/phone-only SAQ A merchants with no such web page don't have that server in scope.
›What are the PCI merchant levels now?
Visa uses three levels since it merged Levels 3 and 4 on April 25, 2024: Level 1 (over 6 million Visa transactions a year), Level 2 (1,000,001–6,000,000) and Level 3 (up to 1,000,000). Mastercard still uses four: Level 1 (over 6 million), Level 2 (over 1 million to 6 million), Level 3 (over 20,000 to 1 million e-commerce) and Level 4 (everyone else). Your acquirer decides how you validate.
›What happens if I'm not compliant or have a breach?
Card brands assess your acquirer, which passes costs to you under your merchant agreement, and can raise fees or terminate your account. Visa's published breach rules (What To Do If Compromised, June 2026) let it assess up to $100,000 per incident for failing to report a suspected compromise within three calendar days, set non-compliance assessments for Level 3 merchants starting at $5,000–$25,000 depending on volume, and require a PCI Forensic Investigator in many cases.
›Is there a new PCI DSS version coming?
Not yet announced. PCI DSS v4.0.1 is the only active version (v4.0 retired December 31, 2024, and all future-dated requirements became mandatory March 31, 2025). PCI SSC ran a Request for Comments on v4.0.1 from June 3 to July 20, 2026 to shape 'the next iteration', without naming a version or date.
›How much does PCI compliance cost a small merchant?
There's no official price list. For SAQ A or B merchants the main costs are your time and, if your SAQ requires them, quarterly ASV scans; for SAQ A-EP, C or D add tooling, penetration testing and possibly consultants. ASVs, QSAs and pen testers quote per engagement — get quotes from firms on the PCI SSC lists. The cheapest path is reducing scope: hosted checkout, P2PE terminals, and never storing card numbers.
Related tools & guides
Which framework do I need?
PCI, HIPAA, CMMC, SOC 2, FTC Safeguards — based on your facts, with the rule for each.
Vanta vs Drata (published prices)
List prices the vendors post on AWS Marketplace, frameworks and integrations.
Sales tax by state
Selling online? Check economic nexus and rates in every state.
Official Sources
Figures checked against these sources on 2026-10-07- PCI SSC Document Library (PCI DSS v4.0.1, SAQs) — SAQ A r1 (Jan 2025); other v4.0.1 SAQs Oct 2024
- PCI SSC: Important updates for merchants validating to SAQ A — 6.4.3, 11.6.1, 12.3.1 removed from SAQ A; new script-attack eligibility criterion
- PCI SSC: FAQ 1588 clarifies SAQ A eligibility (Feb 28, 2025)
- PCI SSC: Request for Comments on PCI DSS v4.0.1 (Jun 3–Jul 20, 2026) — feedback for the next iteration; no new version announced
- PCI SSC list of Approved Scanning Vendors
- PCI SSC: Merchant resources
- Visa: What To Do If Compromised (effective Jun 25, 2026) — merchant levels; Levels 3 and 4 consolidated Apr 25, 2024
- Mastercard Site Data Protection (SDP) program — Mastercard merchant Levels 1–4 and validation requirements
Related Resources on This Site
Related by industry
Helpful guides
- Employment Lawemployee vs independent contractor
- Sick Leavepaid sick leave requirements by state
- Required Benefitsrequired employee benefits by state
- Benefitsworkers comp as an employee benefit
General information, not legal or security advice. PCI DSS validation requirements are set by the card brands and your acquirer; confirm your SAQ with them. SAQ summaries paraphrase PCI SSC documents — rely on the official SAQ text. SmallBizHandbook has no affiliation with any vendor named here. See also all security & compliance guides.