Compliance Guide

PCI DSS 4.0.1 for small merchants

If you take credit cards at a register, a table, or a website, PCI DSS applies to you. Here’s how to figure out which questionnaire is yours, how to shrink your scope, and what changed in 2025.

Jump to the checklist

Last reviewed · For small retailers, restaurants, salons, service businesses, and other merchants that accept payment cards.

Not legal advice. This guide is general educational information from an IT provider, current to the best of our knowledge as of September 24, 2026. Regulations, standards, and official guidance change, and how they apply depends on your specific facts. Confirm your obligations with a qualified attorney, compliance professional, or the relevant regulator or standards body before relying on it. PinellasIT does not certify compliance.

The Payment Card Industry Data Security Standard (PCI DSS) is the security baseline every business that stores, processes, or transmits cardholder data is expected to meet. For a small shop or restaurant, the goal isn’t to build a bank-grade security program. It’s to keep card data out of as many of your systems as possible, so the part you have to secure is small and simple.

What PCI DSS is (and who enforces it)

PCI DSS is written by the PCI Security Standards Council, which was founded by the major card brands. It isn’t a government law. It’s a contractual obligation that comes through your merchant agreement with your acquirer (the bank behind your merchant account) or your payment processor. They decide how you validate compliance, usually through an annual Self-Assessment Questionnaire (SAQ) and, depending on your setup, quarterly external vulnerability scans by an Approved Scanning Vendor.

The current version is PCI DSS v4.0.1, a limited revision published in June 2024. Version 3.2.1 was retired in 2024, and v4.0 was retired at the end of 2024. Check the PCI SSC document library for the latest version of the standard and the SAQ forms, since they are revised from time to time. If you don’t validate, the usual consequences are monthly non-compliance fees from your processor and, after a breach, potential liability for fraud losses and investigation costs.

SAQ types in plain English

Your SAQ type depends on how you accept cards. Your acquirer or processor has the final say, so confirm with them. As a rough guide:

SAQTypical small-business setup
AE-commerce or mail/phone orders fully handed off to a PCI-compliant third party. Your site redirects to, or embeds, the processor’s payment page, and you never touch card numbers electronically.
A-EPE-commerce where your own website affects the payment page (for example, it serves the scripts or the form that sends card data straight to the processor), even though your server doesn’t store card data.
BOnly imprint machines or standalone terminals that dial out over a phone line. This is increasingly rare.
B-IPOnly standalone, PCI-approved terminals that connect to the processor over your internet connection and aren’t linked to other systems.
C-VTStaff key card numbers into a processor’s web-based virtual terminal on a dedicated, isolated computer.
CA point-of-sale system or payment application connected to the internet. This is common in restaurants and retail with integrated POS.
P2PEOnly hardware terminals that are part of a PCI-listed point-to-point encryption (P2PE) solution. This is usually the smallest scope available for in-person payments.
DEverything else, including businesses that store card data electronically. This is the full set of requirements, and you want to avoid it if you can.

If you accept cards more than one way, such as in-store terminals plus an online store, you may need to address more than one channel. The practical lesson is that the more you outsource card handling to validated solutions (P2PE terminals, hosted payment pages, tokenization), the shorter your questionnaire and the smaller your risk.

Segmenting your card terminals

PCI DSS scope includes the systems that handle card data and anything connected to them. If your card terminals or POS share a flat network with the office PC, the security cameras, the smart TV, and the guest Wi-Fi, all of that can be pulled into scope and exposed to the same attacks. Segmentation isn’t strictly required by the standard, but it’s the single most effective way for a small merchant to reduce scope and risk.

  • Put payment devices on their own network segment (a dedicated VLAN or physically separate network) with firewall rules that allow only the traffic they need to reach the processor.
  • Keep guest Wi-Fi completely separate from payment and business systems, not just behind a different password.
  • Keep IoT devices off the payment segment: cameras, thermostats, music systems, and vendor-managed kiosks.
  • Lock down vendor remote access. Several well-known retail breaches started with a third party’s remote connection. Require unique accounts and MFA, and turn access on only when it’s needed.
  • Document it with a simple network diagram showing where card data flows. If you rely on segmentation to reduce scope, your SAQ may require you to test that it actually works.

We cover the building blocks in VLANs explained and network segmentation for security.

What became mandatory March 31, 2025

Version 4.0 introduced dozens of new requirements that were “best practice” until March 31, 2025, when they became mandatory. Which ones apply to you depends on your SAQ. In general terms, the themes are:

  • Stronger authentication: MFA for all access into the cardholder data environment, not just remote access, plus longer minimum passwords (generally 12 characters where supported).
  • E-commerce payment page protection: controls to manage and monitor scripts on payment pages and detect unauthorized changes, aimed at card-skimming attacks. The SAQ A form was revised in early 2025 to adjust how these apply to fully outsourced sites, so review the current version and its eligibility criteria.
  • Anti-phishing protections and technical controls to detect and protect against phishing.
  • Targeted risk analyses: documented reasoning for how often you perform certain activities, such as reviews and scans, where the standard lets you choose.
  • Better logging and review, including automated mechanisms to review audit logs for the larger SAQs.
  • Tighter scope confirmation and inventories: keeping track of payment devices, software, and where card data flows.

Where small merchants usually slip

  • Filling out the wrong SAQ, or checking “yes” to everything without understanding the questions.
  • Default passwords left on POS systems, routers, or terminals, or one shared login for every cashier.
  • Card terminals and POS on the same network as guest Wi-Fi.
  • Card numbers written on paper or typed into email, spreadsheets, or reservation notes.
  • Terminals not inspected for tampering or skimming overlays.
  • Unsupported Windows versions still running a back-office or POS PC.

These patterns show up repeatedly in retail breaches. See our write-ups on the Target POS breach and Home Depot breach.

Practical PCI DSS checklist for small merchants

  • Confirm with your processor which SAQ type(s) apply to each way you accept cards.
  • Prefer P2PE-validated terminals and hosted payment pages to shrink your scope.
  • Never store full card numbers, CVV codes, or track data on paper, email, spreadsheets, or POS notes.
  • Put card terminals and POS on a dedicated network segment, with firewall rules limiting what they can reach.
  • Keep guest Wi-Fi and IoT devices (cameras, TVs, music systems) off the payment network.
  • Change every default password; give each employee a unique login; use MFA for admin and remote access.
  • Require MFA and on-demand-only access for POS vendor remote support.
  • Keep POS, payment PCs, firewall, and router firmware patched and on supported versions.
  • Run required quarterly external scans (if your SAQ calls for them) and fix failures promptly.
  • Inspect terminals for tampering and skimmers on a schedule, and train staff on what to look for.
  • For e-commerce, know every script on your payment page, or confirm your hosted page meets the current SAQ A criteria.
  • Keep a device inventory and simple network diagram showing where card data flows.
  • Complete and submit your SAQ and Attestation of Compliance annually, and keep copies.
  • Have a written plan for a suspected card breach: who to call, starting with your processor.

How PinellasIT helps

We don’t fill out your SAQ for you or certify compliance. That attestation belongs to your business. We build and maintain the network and security controls behind your answers, so you can answer them honestly.

  • Free security assessment — find the flat networks, default passwords, and exposed services that pull extra systems into scope.
  • Cybersecurity — firewalls, segmentation, MFA, endpoint protection, and phishing defenses.
  • Managed IT services — patching, device inventory, and user account management for your back office and POS PCs.
  • Server administration — hardening and log management for on-premises POS and back-office servers.

We're a locally owned managed IT provider serving Pinellas and Pasco County businesses since 2010. We handle the technical safeguards and the documentation that shows they're in place; your attorney, auditor, or compliance advisor handles the legal judgment calls. See all of our compliance guides.

Frequently asked questions

Is PCI DSS a law?

No. It’s an industry standard enforced through your merchant agreement with your acquiring bank or payment processor. Some state laws reference it, and it matters a great deal after a breach, but the obligation mainly comes from your contracts.

We use Square, Stripe, Clover, or Toast. Are we automatically compliant?

Not automatically. A good provider can dramatically reduce your scope, but you’re still responsible for validating compliance (often a short SAQ), protecting your own network and devices, and following safe practices such as never writing down card numbers. Check what your provider requires of you.

Which SAQ do I fill out?

It depends on how you accept cards: hosted e-commerce, standalone terminals, integrated POS, virtual terminal, and so on. Your acquirer or processor decides, so ask them to confirm. The table above is a plain-English starting point.

What happened on March 31, 2025?

The requirements introduced in PCI DSS v4.0 as “future-dated” best practices became mandatory. They include broader MFA, payment-page script controls for e-commerce, phishing protections, and targeted risk analyses. Which apply to you depends on your SAQ.

Do I need network segmentation?

The standard doesn’t strictly require it, but without it, every device on the same network as your payment systems can fall into scope. For most small merchants, putting terminals on their own segment is the simplest way to reduce both risk and paperwork.

Can I store card numbers for repeat customers?

Avoid storing them yourself. Use your processor’s tokenization or card-on-file feature, so the processor holds the card data and you keep only a token. Storing card data yourself greatly expands your obligations. Sensitive authentication data such as CVV codes must never be stored after authorization.

Want a second set of eyes on your safeguards?

Our free security assessment reviews the technical controls this guide covers and gives you a plain-English list of gaps, in priority order. No obligation and no sales pressure.

Prefer email? Reach us at info@pinellasit.com.