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 checklistThe 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.
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.
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:
| SAQ | Typical small-business setup |
|---|---|
| A | E-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-EP | E-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. |
| B | Only imprint machines or standalone terminals that dial out over a phone line. This is increasingly rare. |
| B-IP | Only standalone, PCI-approved terminals that connect to the processor over your internet connection and aren’t linked to other systems. |
| C-VT | Staff key card numbers into a processor’s web-based virtual terminal on a dedicated, isolated computer. |
| C | A point-of-sale system or payment application connected to the internet. This is common in restaurants and retail with integrated POS. |
| P2PE | Only 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. |
| D | Everything 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.
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.
We cover the building blocks in VLANs explained and network segmentation for security.
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:
These patterns show up repeatedly in retail breaches. See our write-ups on the Target POS breach and Home Depot breach.
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.
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.
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.
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.
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.
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.
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.
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.
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.