How Much Does PCI Compliance Cost? Fees, Scans and Tools
See what PCI compliance cost really covers for a small business, from processor fees to scans, and the setup choices that shrink your scope and bill.
On this page 6 sections
Key takeaways
- The PCI fee on your statement is your processor's own charge. Paying it does not make you compliant. Meeting the requirements does, and you prove it by filing your questionnaire and passing any required scans.
- The non-compliance fee is the most avoidable PCI cost because it usually stops once you validate.
- Scope drives the bill. Encrypting terminals and a hosted checkout page can move you to a shorter questionnaire with fewer scans.
- Card numbers written on paper and guest Wi-Fi shared with the POS are two common ways stores and restaurants enlarge their own scope.
For most small businesses, PCI compliance cost comes down to a program fee from your processor plus a few hours of your own time on a yearly self-assessment questionnaire. Some setups also need quarterly vulnerability scans from an outside vendor. Large merchants pay far more because network rules generally require outside assessors at higher transaction volumes. At any size, the bill follows scope, meaning the number of your systems that ever handle a card number. When you shrink that, the paperwork and the risk both shrink with it.
What You're Paying for in PCI Compliance
PCI DSS, the Payment Card Industry Data Security Standard, is a set of security requirements maintained by the PCI Security Standards Council, an organization the major card brands founded. It is not a federal law. You agree to follow it when you sign your merchant agreement. The card networks enforce it through rules that bind your acquiring bank, and the bank passes the obligation to you. That chain explains where each charge on your bill comes from:
- Network rules decide which merchants must validate compliance and whether they do it by self-assessment or by outside audit.
- Your processor's pricing sets what you pay for the program that tracks your status, and what you pay if you don't validate.
- Outside vendors charge for scanning and testing work when your setup calls for it.
- Your own time goes into the questionnaire plus any network or software fixes it exposes.
State data breach notification laws sit on top of all this. They vary by state, and they apply after a breach whether you were PCI compliant or not. Treat this article as general information, and take legal questions to a qualified professional.
The PCI Compliance Fee on Your Statement vs. the Non-Compliance Fee
The PCI compliance fee is one of the most misunderstood lines on a merchant statement. It isn't a card network charge, and it doesn't go to the PCI Council. Your processor sets it and keeps it, whether it bills monthly or once a year. In most cases it pays for access to a compliance portal where you complete your questionnaire. Some processors also bundle in vulnerability scanning or a breach-coverage product.
Paying that fee doesn't make you compliant. Meeting the requirements does, and you prove it by validating. That means filing your questionnaire and passing any scans it requires. Coverage varies widely between processors, so read the fee schedule in your agreement before you assume anything is included.
A non-compliance fee is a separate charge. Many processors add it for every month your annual validation is overdue, and it keeps billing until you file. This is also processor pricing, not a network fine, so it's the easiest PCI cost to eliminate. Once you validate, it usually stops. If you ignore it for a year, you pay a full year of monthly penalties on top of the program fee.
A misread worth correcting. Some merchants treat the non-compliance fee as a kind of coverage, as if paying it kept them in good standing. It doesn't. It's a penalty for missing validation, and it buys you no protection if card data is stolen.
When you compare offers, put both PCI lines next to the rest of the pricing. Our guide on how to compare merchant processing quotes side by side walks through the method. Ask each provider four questions: the amount of each PCI fee, how often it bills, what it includes, and how long you have after approval to validate before the non-compliance fee starts. A provider that can't answer clearly fits the pattern in red flags to spot before signing with a processor.
PCI Scan Cost, Penetration Tests and QSA Audits by Level
The card networks sort merchants into validation levels by annual transaction volume, and each network sets its own thresholds. Your acquiring bank tells you which level applies to you. Most independent merchants sit in the lowest tier.
Small Merchants in the Lowest Tier
Small merchants usually validate with a self-assessment questionnaire (SAQ). Several versions exist, and yours depends on how you accept cards. A merchant that hands card data entirely to a third party gets a short form. A merchant whose own computers or servers handle card numbers gets the full version, which is far longer and more technical.
Some questionnaires also require quarterly external scans by an Approved Scanning Vendor (ASV). An ASV is a company the PCI Council has certified to probe your internet-facing systems for known weaknesses. Other questionnaires don't require these scans. Scan rules for some questionnaires changed in recent versions of the standard, so confirm the current requirement with your processor instead of relying on an old checklist.
PCI scan cost is often folded into the processor's program fee. If you buy scans separately, vendors usually price them per quarter and scale the price by how many IP addresses or domains get scanned. The scan is rarely where the money goes. A failed scan means fixing the problem and scanning again. Paying an IT contractor to close an open port or patch a server is often the bigger expense.
Larger Merchants
Higher-volume merchants carry heavier validation duties. The largest generally need an annual on-site assessment by a Qualified Security Assessor (QSA), a firm certified by the PCI Council, which produces a formal Report on Compliance. Penetration testing is an authorized simulated attack on your systems. It applies to many larger environments, and also to small merchants on the full questionnaire. Assessors and testers both price per engagement, and the price climbs with the number of locations and systems in scope. Get at least two proposals and compare how each firm defines your scope.
Size isn't the only trigger. After a breach, the networks can require a merchant that used to self-assess to validate at a higher level.
| Cost item | Who usually needs it | How it's typically priced |
|---|---|---|
| Processor PCI program fee | Nearly every merchant account | Monthly or annual, set by your processor |
| Non-compliance fee | Merchants who haven't validated | Monthly until you validate |
| ASV vulnerability scan | Merchants whose questionnaire requires it | Per quarter, by IP or domain; sometimes bundled |
| Penetration test | Full-questionnaire and larger merchants | Per engagement, by environment size |
| QSA assessment | The largest merchants, or when required | Per engagement, by locations and systems |
| Remediation | Anyone who fails a scan or a requirement | IT labor plus any replacement equipment |
Hardware and Software That Shrink Your Scope
Every system that touches card data has to meet the requirements in your questionnaire. Take a system out of the card data path, and its share of the work goes with it. Scope is the one part of the bill you control directly.
Retail Counters
For a store, the biggest change is a terminal that encrypts card data at the moment the card is read. With that in place, your POS software and store network never see a readable card number. Ask whether the solution appears on the PCI Security Standards Council's list of validated point-to-point encryption (P2PE) solutions, because a validated solution can qualify you for a much shorter questionnaire. A smart terminal that handles payment on the device itself keeps card data off the back-office PC. Also check that receipts and reports print only truncated card numbers.
Restaurants and Bars
Restaurants often enlarge their own scope without noticing. Say a catering order comes in by phone, someone writes it on a notepad with the card number, and the slip ends up in a binder. That binder is now in scope. Key phone orders straight into a terminal or a virtual terminal for phone and catering orders, stop writing card numbers down, and securely shred any old slips that carry them.
Guest Wi-Fi belongs on a separate network from the POS. If a vendor set up your network, ask them in writing whether the two are separated. Pay-at-table handheld terminals keep the card in the guest's hand instead of carrying it to a back station. That mainly helps with skimming risk and guest trust. Whether it also reduces scope depends on how the device encrypts.
Online Stores
For an online store, the deciding question is where the card number goes when the customer clicks Pay. With a hosted checkout page or hosted payment fields from your gateway, the number goes straight to the gateway and never reaches your server. A self-hosted form that passes card data through your server puts that server in scope. That usually means the full questionnaire, often with scans on top. Subscription billers should store the gateway's tokens, never card numbers. MannyPay supports payment gateways such as Authorize.net and NMI along with carts including Shopify and WooCommerce. Before you build, ask which questionnaire your checkout setup typically qualifies for.
Some merchants confuse two different protections. 3-D Secure authentication helps fight card-not-present fraud and can shift fraud liability on authenticated transactions. It does nothing for your PCI scope.
Breach Costs vs. Compliance Costs
Compliance costs are small and predictable. Breach costs are neither. After a suspected compromise, the networks can require a forensic investigation by an investigator the PCI Council has approved, and the merchant generally pays for it. The networks can also bill your acquirer for fraud losses and card reissuance, and your merchant agreement usually lets the acquirer pass those charges to you.
More costs follow from there. Fraudulent use of the stolen cards brings chargebacks. State law may require you to notify affected customers, and that usually means hiring a lawyer. Your acquirer may move you to a stricter validation level or close the account.
Validating doesn't make you breach-proof, and a compliant merchant can still lose card data. Your compliance status at the time of a breach will still matter when your acquirer and the networks review what happened. If you're already dealing with a suspected compromise, follow our card data breach response plan.
A Realistic Annual PCI Compliance Cost for Small Merchants
Two small merchants with the same processor and the same program fee can end up with very different annual PCI bills. The gap comes from setup, not pricing. Here is how the cost lines compare for two common setups.
Store A takes cards on encrypting countertop terminals and sells online through a hosted checkout page. Store B runs its own payment form on its own web server, and its POS shares a network with guest Wi-Fi.
| Cost line | Store A | Store B |
|---|---|---|
| Processor PCI program fee | Yes | Yes |
| Questionnaire | Short form | Full version |
| Quarterly ASV scans | Only if its questionnaire calls for them | Expected, since card data passes through a public server |
| Penetration test | Not typically | Likely under the full questionnaire |
| IT remediation | Little expected | Separating networks and fixing scan findings |
| Risk of non-compliance fees | Lower, because the form is quick to finish | Higher, because the long form is easy to put off |
To put dollars on your own setup, add up these lines for the past year:
- Your processor's PCI program fee, converted to an annual amount.
- Any non-compliance fees on your statements.
- Scan costs you paid outside the program fee.
- Staff hours spent on the questionnaire, multiplied by what that time is worth to you.
- IT contractor invoices for PCI fixes.
- Any penetration test or assessor fees.
If lines 4 and 5 make up most of the total, scope is the problem. A terminal change or a hosted checkout may cost less than another year on the long questionnaire. When you plan your monthly processing budget, include these PCI lines with the rest of your processing costs.
Start with your last three statements. Find the PCI program and non-compliance lines. Then log in to your processor's compliance portal to see which questionnaire you're assigned and when your validation expires. If a non-compliance fee is showing, file this week. If you're on the full questionnaire, ask whether a different terminal or a hosted checkout would move you to a shorter one. To have a MannyPay specialist review your setup and pricing, request a free processing quote.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


