PCI compliance for small business comes down to two jobs. Follow the card industry's security rules, called PCI DSS (version 4.0.1 is current as of October 2026). Then prove it once a year, usually with a Self-Assessment Questionnaire (SAQ) in your processor's online portal. Which SAQ you file depends on how you take cards, and the table below shows which one fits.
Skip the yearly form and your processor will usually start adding a PCI non-compliance fee to your statement. That fee is how a lot of small businesses first learn PCI exists.
Who sets the rules, and who checks them
Three groups are involved, and it helps to know which is which.
- The PCI Security Standards Council writes the standard and the SAQ forms. Its document library lists PCI DSS v4.0.1 as the current version. The older v4.0 was retired on December 31, 2024.
- The card brands (Visa, Mastercard, and the rest) decide how merchants must prove compliance, based on how many transactions they run.
- Your processor and its bank enforce it. They ask for your SAQ, and they charge the fees.
PCI DSS is not a federal law. It reaches you through the merchant agreement you signed with your processor.
Which merchant level are you?
Your level is set by your yearly transaction count with each card brand. Here are the Mastercard levels, from its Site Data Protection program page. Visa uses similar cutoffs.
| Level | Yearly Mastercard transactions | How you prove it |
|---|---|---|
| 1 | More than 6 million | Annual Report on Compliance |
| 2 | 1 million to 6 million | Annual SAQ |
| 3 | More than 20,000 online, up to 1 million total | Annual SAQ |
| 4 | Everyone else | Set by your processor, usually an annual SAQ |
Almost every small business is Level 4. At that level the card brands leave the proof up to your processor. In practice, most processors ask for a yearly SAQ, plus quarterly network scans if your SAQ type calls for them.
Which SAQ fits your setup?
This is the part most PCI guides skip. Find the row that matches how you take cards. If you take cards more than one way (say, a counter terminal and an online store), each way can need its own SAQ.
| How you take cards | Usual SAQ | Quarterly scans? |
|---|---|---|
| Card imprint machine, or a standalone terminal that dials out over a phone line and never touches the internet | SAQ B | No |
| Standalone, PCI-approved terminal connected over the internet, not linked to any other system in your business | SAQ B-IP | Yes |
| Terminals from a validated point-to-point encryption (P2PE) solution on the PCI Council's list, and nothing else in your business handles card data | SAQ P2PE | No |
| POS system (register or tablet with a card reader) on an internet-connected network | SAQ C | Yes |
| Typing cards into a virtual terminal website, one at a time, on a computer with no card reader attached | SAQ C-VT | No |
| Online store where the whole payment page comes from your processor (a redirect or an embedded payment frame) | SAQ A | Yes, for your website |
| Online store where your own site builds the payment form, but card data goes straight to the processor | SAQ A-EP | Yes |
| Anything else, including storing card numbers on your own computers | SAQ D | Yes |
Based on the eligibility rules and requirement lists in each PCI DSS SAQ form, checked October 2026. Your processor has the final word on which SAQ you file, so confirm your row with them.
The SAQ A mistake to avoid
SAQ A is the shortest form, so a lot of merchants pick it by default. Its rules are strict. The PCI Council's v4.0.1 SAQ A says it is for card-not-present payments only (online, mail, or phone orders) and does not apply to face-to-face sales. You also can't store, process, or send card data on your own systems. Every part of the payment page has to come from a PCI-compliant processor.
So a store with a counter terminal can't file SAQ A for that terminal. A phone order you type into a virtual terminal on your own computer is SAQ C-VT, not SAQ A.
One more rule took effect in 2025. If your website embeds your processor's payment form (an iframe, for example), you must confirm your site is not open to script attacks that could affect that page. The PCI Council's FAQ on this rule gives two ways to meet it. Put script protections on your own page, or get written confirmation from your processor that its embedded form protects against these attacks when you set it up their way. If your site sends shoppers to the processor's own page (a full redirect), this rule does not apply.
Why P2PE is the easy route for counter sales
PCI DSS has 12 requirements, but each SAQ includes only the ones that apply to that setup. SAQ P2PE covers parts of just three (Requirements 3, 9, and 12) and needs no quarterly scans. If you take cards in person, ask your processor whether your terminals are part of a validated P2PE solution. If they are, your yearly job gets much smaller.
What a PCI non-compliance fee is (and who charges it)
A PCI non-compliance fee is your processor's own fee. It shows up when the processor has no current SAQ on file for you, or is missing scan results your SAQ needs. It is usually charged every month until you catch up.
It is not a card brand fine, even when it is worded to sound like one. The card brands deal with your processor's bank, not with you. Visa's account information security page says it may charge non-compliance assessments to acquirers (the bank side of your processor). The amount on your statement comes from your processor's fee schedule, which is part of your merchant agreement.
You may see up to three PCI lines on a statement:
- PCI compliance or program fee. A yearly or monthly charge for portal access and scans. Some processors charge it, some do not. Ask what it covers.
- PCI non-compliance fee. The penalty for a missing SAQ. Usually larger, and monthly.
- Breach protection or data security fee. An add-on that may cover some costs after a breach. Ask for the coverage terms in writing before you keep paying it.
Worked example (illustrative numbers)
These figures are made up to show the math. Your fee schedule will have its own numbers.
Say your agreement lists a $99 yearly PCI program fee and a $39.95 monthly non-compliance fee. Your SAQ came due in March, nobody told you, and you filed in September. That is six months of the penalty, or $239.70, on top of the $99 you already paid for the portal where the form lives.
How to make the fee stop
- Ask your processor which portal you use and when your SAQ is due.
- Log in and complete the SAQ that fits your setup.
- Run your quarterly scan through the portal if your SAQ needs one.
- Ask in writing for the date the fee will stop, and ask whether any months charged after you filed can be credited back.
- Check your next two statements. If the line is still there, call and point to the date you filed.
PCI compliance checklist for small business
Work through this once a year. After the first year, it goes fast.
- Ask your processor which SAQ you file, and the due date.
- List every way you take cards: counter, phone, online, mobile.
- Never keep card numbers in email, spreadsheets, or notebooks. If you must write one down, lock it up and shred it when you are done.
- Change the default passwords on terminals, routers, and POS accounts.
- Keep a list of your card terminals and check them for tampering or swapped devices.
- Give each employee their own login. No shared passwords.
- Install software and security updates on anything that handles payments.
- Run quarterly network scans if your SAQ requires them.
- Get proof that your payment companies (processor, gateway, POS) are PCI compliant for the services you use.
- Write a short security policy and a plan for what you will do if card data is exposed. Most portals have a template.
- Sign the Attestation of Compliance, save a copy, and put next year's due date on your calendar.
PCI rules get updated. The form in your processor's portal is the current one, so use it over any older copy you have saved.
Frequently asked questions
Is PCI compliance required for small businesses?
Yes. Any business that accepts card payments has to follow PCI DSS, no matter how small. It is not a federal law. It reaches you through your merchant agreement, and your processor decides how you prove it, which for most small businesses means a yearly Self-Assessment Questionnaire.
Which SAQ do I need?
It depends on how you take cards. A standalone internet-connected terminal is usually SAQ B-IP, a POS system on your network is usually SAQ C, typing cards into a virtual terminal is SAQ C-VT, and an online store that fully outsources its payment page is usually SAQ A. Your processor confirms which one applies.
What is a PCI non-compliance fee?
It is a fee your processor charges, usually every month, when it has no current SAQ (and scan results, if your SAQ needs them) on file for you. The amount comes from your processor's fee schedule, not from the card brands. It normally stops once you complete your SAQ.
Can I use SAQ A if I have a store?
Not for the store. SAQ A covers only card-not-present payments, meaning online, mail, or phone orders where all card handling is outsourced. The PCI Council's own form says it does not apply to face-to-face channels. Your in-person payments need their own SAQ.
Not sure what the PCI lines on your statement are for? Send it through our free rate review. You get a one-page review showing your real effective rate and the fees behind it, PCI lines included. For the rest of the statement, see the hidden processing fees guide and how to read your merchant statement.