If you accept credit or debit cards, PCI DSS applies to you. For most small businesses the practical goal is to keep card data off your own systems, separate payment devices from the rest of your network, and complete the self-assessment your processor asks for.
PCI DSS stands for Payment Card Industry Data Security Standard. It is the set of security rules the card brands expect every business that handles card payments to follow.
The full standard is long and technical. Most small businesses only deal with a slice of it, and smart choices about how you take payments can shrink that slice a great deal. This guide is general information, not legal advice. Your card processor decides what you must do and is the right place to confirm specifics.
Any business that accepts, processes, stores or transmits payment card data. A clinic taking copays, a restaurant, a dental office, a nonprofit accepting donations and an online store are all included. There is no exemption for being small.
PCI DSS is not a law. It is an industry standard that reaches you through your contract with your payment processor or bank. That contract is what gives it teeth. A business that suffers a card breach and was not following the standard can face costs passed down from the card brands and can lose the ability to accept cards.
Large merchants are audited by outside assessors. Most small businesses validate with a Self-Assessment Questionnaire (SAQ) instead. It is a form in which you attest, usually once a year, that you meet the requirements that apply to you.
There are several versions of the SAQ. Which one you complete depends on how you take cards. A business that only uses a standalone terminal answers far fewer questions than one that stores card numbers or runs payments through its own computers. A business that sends online customers to a payment page hosted by its processor has a shorter form than one that collects card details on its own website.
Your processor tells you which SAQ applies and whether you also need regular external vulnerability scans from an approved scanning vendor. Do not pick a version yourself because it looks shorter. Answer it honestly. It is an attestation, and a wrong answer can hurt you after a breach.
The simplest way to reduce your PCI burden is to never keep card data in the first place. If your systems do not hold it, there is much less to protect and much less to steal.
PCI DSS applies to the systems that handle card data and to anything connected to them. That set of systems is called your scope. If your card terminals share one flat network with every office computer, the guest Wi-Fi and the smart TV in the lobby, all of it may be in scope.
Segmentation means putting payment devices on their own separated network, with a firewall controlling what can talk to them. Done properly, it keeps the rest of your office out of scope and keeps an infected front desk computer from reaching the terminals. Guest Wi-Fi should always be separated from business systems, whether or not you take cards.
Also ask your processor about terminals that encrypt the card the moment it is read. With a validated solution of that kind, card data passes through your network in a form you cannot read, which can shorten your SAQ further.
Your processor or merchant bank is your main contact for PCI. They can tell you your merchant level, which SAQ applies, whether scans are required, and how and when to submit your attestation. Many provide an online portal for it.
Ask them which of their products reduce your scope. Keep terminals and payment software up to date, and replace terminals the maker no longer supports. Check terminals now and then for tampering. If you use a point-of-sale or practice management vendor, ask for their PCI documentation and get it in writing which duties are theirs and which are yours.
Keep your completed SAQ and attestation, any scan reports, a simple diagram of how payments flow through your business, a list of payment devices and where they are, your written policies, and your vendors' PCI documents.
Common gaps are familiar ones. Terminals on the same network as everything else. Default passwords on a router or point-of-sale system. Remote access to the payment system for a vendor with no multi-factor authentication. Card numbers in paper files or old email. An SAQ filled out years ago by someone who has since left. A payment computer also used for web browsing and email.
An IT provider can map where card data travels, segment the network, configure the firewall, secure remote access, keep systems patched, arrange required scans and explain the technical SAQ questions in plain terms.
The attestation is still yours. You sign it, you choose how you take payments, you train staff on handling cards, and you manage the relationship with your processor. No IT provider can make a business PCI compliant by itself.
We only use a terminal from our processor. Does PCI still apply? Yes, but your part is usually much smaller. You will likely complete one of the shorter questionnaires. You still need to protect the terminal, keep it separated from other systems where you can, and avoid writing card numbers down.
Is PCI DSS a law? No. It is an industry standard enforced through your agreement with your processor or bank. Ask your processor what it requires of you.
Does using a compliant processor make us compliant? No. A compliant processor covers its own systems and can reduce your scope. You are still responsible for your devices, your network, your staff practices and your own attestation.
How often do we complete the SAQ? Validation is generally an annual exercise, and some businesses also need periodic scans. Your processor sets the schedule, so confirm it with them.
A security assessment shows where card data touches your network and what it would take to separate it. You get a plain-English list of findings, ranked by risk and effort.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas
Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support