DFW Pay Pros logo
DFW Pay Pros
Merchant Services & Equipment
(817) 583-1169 info@dfwpaypros.com
Get My Free Savings Analysis
Compliance

PCI Compliance for Small Business: What You File and What You Pay

For a small business, PCI compliance usually means filling out one Self-Assessment Questionnaire a year online, through your processor’s portal. Most small businesses are Level 4 merchants, so they file SAQ A or SAQ B-IP, which are the short ones. Your processor bills a small monthly PCI fee either way, and a much bigger non-compliance fee if you never file.

People mix those two charges up. The first is a few dollars a month; the second is a penalty for skipping the paperwork, and on a lot of statements we review it’s been billing since the application was signed.

What is PCI compliance, in plain terms?

PCI DSS stands for the Payment Card Industry Data Security Standard. It’s written by the card brands through a body they jointly own, the PCI Security Standards Council, or PCI SSC. Congress had no hand in it, but it’s written into the contract you signed to accept cards, so it binds you about as tightly as a law would.

It covers how cardholder data gets stored, moved and protected: firewalls, patching, who has access to what, even the receipt that prints a card number. A big company handles that with auditors. A coffee shop answers a questionnaire honestly.

The party that cares is your acquirer. If your business leaks card data, the acquiring bank owes the networks money, so your merchant bank pushes validation down to you. Visa isn’t sending anyone to audit your quilt shop.

What counts as cardholder data, and what you must never store

Almost everything in PCI comes down to scope, meaning which parts of your business touch card data.

Cardholder data is the primary account number (the card number itself) plus the cardholder name, expiration date and service code. If you hold the number, the other three come into scope along with it.

Sensitive authentication data is a stricter category. It covers full stripe or chip track data, the CVV2, CVC2 or CID, and PINs, and none of it can be stored after a transaction is authorized, whether that’s in a spreadsheet, a booking note or a recording of a phone order. The version we run into most often is a card number and security code written on an order pad and left in a drawer for a year.

Fix that before anything else.

If you never store, process or transmit cardholder data in readable form, your scope shrinks to almost nothing, and your questionnaire shrinks with it.

Who has to comply, and which merchant level are you?

Every business that accepts credit cards has to comply. There’s no revenue floor and no small-business exemption. If you process transactions on the major card brands, the PCI standards come attached to your account.

What your size changes is how you prove it. The card brands sort merchants into four levels by transaction volume, counted per brand per year, and each level has its own documentation requirements. These are Visa’s merchant levels:

Level Rough volume per year How you validate
Level 1 Over 6 million, or by designation. Qualified Security Assessor on site, plus scans.
Level 2 1 million to 6 million. Annual self assessment, plus quarterly scans.
Level 3 20,000 to 1 million e-commerce. Annual self assessment, plus scans.
Level 4 Under 20,000 e-commerce, or 1 million total. Annual Self-Assessment Questionnaire, plus scans if needed.

Nearly every independent restaurant, shop and clinic falls in Level 4, which means a questionnaire rather than an auditor. Be aware that merchants can get bumped up a level after a data breach.

The 12 PCI DSS requirements, in small business terms

The PCI compliance requirements are twelve numbered items grouped under six objectives, and the current version is PCI DSS v4.0.1. Requirements 3 and 4 protect cardholder data directly.

Six payment security objectives, twelve requirements

  • 1. Install and maintain network security controls, meaning firewalls and segmentation.
  • 2. Apply secure configurations to all system components. Don’t use vendor-supplied defaults for system passwords and other security settings.
  • 3. Protect stored account data. The only fully compliant way to store a card number electronically is not to store it.
  • 4. Use strong cryptography when you send cardholder data across open, public networks. Your terminal takes care of this.
  • 5. Protect all systems and networks from malicious software.
  • 6. Develop and maintain secure systems and software. If you don’t write your own code, this mostly means keeping things patched.
  • 7. Restrict access to system components and cardholder data to people with a business need to know, and give them only the rights they need.
  • 8. Identify users and authenticate access, with named logins, strong passwords and multifactor authentication into the cardholder data environment.
  • 9. Restrict physical access to cardholder data, which for most shops means a locked back office.
  • 10. Log and monitor access to system components and cardholder data, so that if someone did get in, you’d know.
  • 11. Test your systems and networks regularly. For a small merchant that’s usually an external scan for known security vulnerabilities.
  • 12. Support payment security with policy: a written information security policy and staff training every year. A two-page policy counts. Having none doesn’t.

The future-dated v4 items stopped being optional on March 31, 2025. Even so, with one standalone terminal, most of the compliance requirements come back as not applicable.

Which SAQ do most small merchants file?

SAQ stands for Self-Assessment Questionnaire. Which one you file depends on how card payments get from your counter or website to your processor, not on your revenue or your industry.

SAQ type Who it fits Effort
SAQ A E-commerce or phone orders, fully outsourced. Short. You attest to what you don’t do.
SAQ A-EP Never receives card data but controls the payment page. Much longer.
SAQ B Dial-up or imprint terminal. No internet, no electronic storage. Short.
SAQ B-IP Standalone PTS-approved terminal on an IP connection. Short to moderate.
SAQ C-VT Virtual terminal, manually keyed. Moderate.
SAQ C Payment application online, not segmented. Network questions get real.
SAQ P2PE Terminal running validated point-to-point encryption. Short.
SAQ D Everyone else, including anyone storing cardholder data. Hundreds of requirements.

The form feels brutal mostly when bad answers to the scoping questions route you to SAQ D. Getting the right one is most of the work.

Validated P2PE shortens it a lot, since card data is encrypted at the tap and your systems never see it readable. That’s a reason to care which dual pricing terminal you’re on.

Every SAQ, the attestations and the other validation tools are free in the PCI SSC document library. You pay your processor for a portal and a scan.

Where SAQ A merchants get caught

The line between SAQ A and SAQ A-EP is the most misread boundary in PCI DSS compliance. If your site redirects to your gateway’s hosted payment page, you’re usually SAQ A. If you control the scripts on the page where customers type their card number, you’ve drifted toward SAQ A-EP, and version 4 added rules about monitoring those payment page scripts. In general, the more you customize the checkout, the more of the standard you take on.

Why does my processor charge a monthly PCI fee?

Because the processor is paying a vendor for the compliance platform and marking it up. Your acquirer contracts with a compliance company that hosts the questionnaire and runs the external scans, the vendor bills the processor, and the processor bills you.

Some of that fee is reasonable. The markup is the part to push back on, and it’s an easy line to check against what you’re really paying or run through the effective rate calculator. For example, $10 a month on $12,000 of volume works out to eight basis points. On $4,000 of volume, it’s twenty-five.

PCI fee vs PCI non-compliance fee

These two charges show up under confusingly similar names, and the second one is the expensive one.

PCI compliance fee PCI non-compliance fee
What triggers it Having a merchant account, validated or not. SAQ not on file, expired, or a failed scan.
Typical size Small monthly or annual line. Several times the compliance fee, monthly.
How you stop it Negotiate, or switch processors. Complete the questionnaire. It usually drops off next cycle.
Retroactive? n/a Ask. Some credit a recent month.

Processors say the non-compliance fee offsets the risk of an unvalidated merchant, and there’s some truth to that. It also makes them steady money off everyone who never opened the enrollment email.

How do I complete the questionnaire and get the fee removed?

It’s less painful than its reputation. You need the portal’s name (ask your rep or check your statement), your merchant ID, and a clear picture of how cards reach you: how your terminal connects, whether your POS stores anything, whether anyone writes card numbers down, and whether your website touches payment data.

Then you log in, answer the scoping questions, land on the right SAQ and attest. People usually get stuck on a failed scan, typically a port left open or a router on its original firmware.

The fee should come off your next statement or the one after. If it doesn’t, call. If the processor says it stays regardless of your compliance status, that tells you something.

Credit card security habits that matter more than the form

Setting the paperwork aside, these four habits do the most good:

  • Card numbers on paper are what gets people in trouble, whether it’s an order pad, a sticky note or the notes field in your booking software. Shred them.
  • Change the default passwords on the router, the POS admin account and anything else that shipped as admin/admin. Use strong passwords and give each person their own login.
  • Keep your payment device off the guest wifi network. Segmenting it takes an afternoon and shrinks your scope for good.
  • Train whoever works the counter. Staff who handle payment information properly and can recognize a phishing email from “your processor” do more for payment security than the questionnaire ever will.

None of this costs money. Most of it is one afternoon with the router manual open.

The mistakes that catch small businesses

The first is underestimating scope. Merchants assume the terminal is the whole story, then remember the tablet that takes phone orders. Anything touching credit card information is in.

The second is forgetting third parties. If your web developer or IT contractor can reach your payment environment, their security is your problem. Payment processors and service providers have to confirm their own compliance status, so ask.

The third is treating it as a one-time event. An attestation is a snapshot of one day, so staying PCI compliant means keeping up with a new employee, a replaced router or a plugin added to the checkout.

The worst is remote access to your POS or gateway with only a password. That’s a failed requirement and the likeliest way you get hit.

Does a dual pricing or cash discount program change my PCI obligations?

No. Pricing and data security are separate issues. A cash discount program at a 4% differential doesn’t change your SAQ, because you still take cards and still have to validate.

What changes your SAQ is how payments flow. Swapping a virtual terminal on a shared office PC for a standalone PTS-approved device can move you from SAQ C-VT to SAQ B-IP and cut the form way down. That swap often happens during a pricing change, so merchants credit the program for the shorter questionnaire when the device did it.

For the pricing side, cash discount vs surcharge explains the models and Visa’s cash discount rules covers the card brand requirements. Your signage doesn’t decide whether a program counts as a surcharge or a cash discount; the POS configuration does. Visa checks compliance through a mystery-shopper program, and acquirers can fine or close merchants who break the surcharge rules.

What happens if there’s a breach and I was never compliant?

Processors stay vague here, so plainly: a validated SAQ is what you claimed on one day, and it won’t shield you. If card data leaves your business, the forensic investigation looks at what was really going on.

A confirmed compromise can bring forensic investigator costs, card reissuance, fraud losses, legal fees, network fines assessed through your acquiring bank, and reputational damage that outlasts all of it. Merchants generally carry the costs of a breach in their own environment, and non-compliance makes it worse, because you’ve broken your merchant agreement too.

With one terminal, no card storage and low odds, the questionnaire really is just paperwork. If you run an e-commerce cart or networked POS, or store card data for recurring billing, it deserves real attention.

What it does for customer data

Customers won’t ask whether you’re PCI DSS compliant. What they notice is a letter saying their data was stolen, and a business that never sends one keeps the trust it had. The standard exists to cut the odds of that happening.

Common questions about PCI

Do I have to redo it every year? Yes. The attestation expires every year, and the non-compliance fee comes back if you let it lapse. If nothing has changed, re-attesting doesn’t take long.

Can I do this myself, or do I need to hire someone? A Level 4 merchant on a short SAQ can handle it alone, since the self assessment is designed for you to answer about your own setup. Get help if you’re on SAQ D or A-EP.

Can I get PCI compliance for free? The questionnaires and validation tools are free from PCI SSC, and most of the security work doesn’t cost anything. Your processor’s portal fee usually isn’t free, though some processors don’t charge one.

How do I know if I’m compliant right now? Log into the portal and look for a current attestation, then check your statement for a non-compliance fee. Those two things will tell you.

My POS company says they’re PCI compliant, so am I covered? No. Their validation may narrow your scope, but your merchant account still needs its own attestation.

I use Square, do I need to do this? Aggregators handle validation differently and generally don’t charge a separate PCI fee. That’s part of the appeal, and part of why the costs diverge at volume. More in Square vs a merchant account.

Where DFW Pay Pros sits on this

DFW Pay Pros is an independent sales organization. We sell merchant services on behalf of larger nationwide processors, in all 50 states.

Our fee policy is simple: no monthly fees and no contract. The only other charges you might see are software fees, if you need the software, and in some cases an annual fee. You’re month to month, there’s no early termination fee, and you can cancel any time at no cost. The first terminal is free for most businesses, and hardware ranges from the Valor VL550 to the Clover Station, Mini, Compact and Flex, along with PIN pads, printers, scanners and cash drawers.

We’ll point you to the right portal and help you land on the right SAQ, since scoping it correctly is what separates a short form from a long one.

Send us a recent statement and we’ll tell you which PCI charge you’re paying and which one you shouldn’t be. With three months of statements, approval can take as little as 24 hours. If you’re thinking about moving, the switching process is a lot less dramatic than most people expect.

Have us check your PCI fees

Send a recent statement and we’ll tell you what you’re being charged and why.

← All payments guides
Call Us Text Us