Skip the reading? Sign up and get a readiness score today. Plans from $47 a month, prices published.
PCI DSS compliance costs a small SaaS or online business roughly $1,000 to $10,000 a year when it validates with a self-assessment questionnaire (SAQ), and $25,000 to $200,000 or more when a Qualified Security Assessor (QSA) has to write a Report on Compliance. Those figures are third-party estimates, not a PCI Council fee schedule. The number that moves your bill most is scope: a business that sends cardholder data straight to a processor's hosted fields fills in the short SAQ A, while one that touches card data on its own servers faces SAQ D and, at high volume, a QSA.
Nobody publishes one price for PCI DSS, because there is no single PCI fee. The PCI Security Standards Council writes the standard and does not charge merchants to comply. Your cost is the sum of separate purchases and hours: scanning, assessment help, tooling, staff time and fixes for what the scan finds. This article breaks the bill into those lines, shows two worked budgets, and flags where teams overspend. For the requirement-by-requirement view, use our PCI DSS compliance checklist.
What does PCI DSS compliance cost?
Third-party guides put a small merchant's annual total anywhere from about $1,000 to $10,000, a Level 2 merchant using a QSA-assisted SAQ D at $10,000 to $50,000, and a full QSA assessment at $25,000 to $200,000. Treat every one of those as a planning band. They come from vendor blogs, they disagree with each other, and none is an official rate. Get quotes from your acquirer, an ASV and, if you need one, a QSA.
| Cost line | Typical range (third-party estimates) | Who needs it |
|---|---|---|
| Self-completed SAQ | $50 to $500 in direct cost, plus staff hours | Merchants eligible for SAQ A, A-EP, B, P2PE or C |
| Consultant-assisted SAQ | $1,000 to $5,000 | Teams unsure of scope or answering SAQ D |
| ASV external scan, quarterly | $100 to $200 per IP a year, up to about $2,000 for larger footprints | Anyone whose SAQ requires external scans (requirement 11.3.2) |
| Rescan after a failed scan | $200 to $800 plus remediation labor | Teams that fail on TLS, patching or exposed services |
| Penetration test (requirement 11.4) | Quoted by scope, often $5,000 and up for an application | SAQ D and Level 1 environments |
| QSA assessment and Report on Compliance | $25,000 to $200,000 or more | Level 1 service providers and merchants, or when the acquirer demands it |
| Processor non-validation fee | About $10 to $125 a month | Merchants whose acquirer has not received a validation |
| Compliance platform | $47 to $299 a month published for Complies; most others quote only | Teams running PCI next to SOC 2 or ISO 27001 |
Why does scope decide the bill?
Scope decides the bill because every system that stores, processes or transmits card data, and every system connected to it, is in scope for the requirements. A SaaS company that embeds a processor's hosted payment form never sees a card number, validates with a short questionnaire and has a small scope. The same company that takes card numbers through its own API inherits the full question set, internal scans, segmentation testing and a pen test.
That is why the first dollar belongs on scoping, not tooling. Confirm with your acquirer which SAQ applies, read the eligibility criteria on the PCI SSC's document library, and write the answer down. Teams that skip this step buy a QSA engagement they did not need or fill in the wrong questionnaire and have it rejected.
What does PCI compliance cost for a small SaaS company?
Take a 25-person SaaS company that sells subscriptions through a processor's hosted checkout and never handles card numbers. It qualifies for the shortest questionnaire. The budget is small and mostly time.
| Line | Annual cost | Note |
|---|---|---|
| SAQ completion and attestation | About 12 staff hours | Scope check, answers, signature on the Attestation of Compliance |
| ASV scans, four a year, 2 public IPs | $200 to $400 | Only if the SAQ requires scans |
| Policy set and access reviews | About 20 staff hours | Requirements 7 and 12, reused for SOC 2 |
| Compliance platform | $564 to $1,428 | Starter $47 or Growth $119 a month billed yearly |
| Total cash | Under $2,000 | No QSA, no pen test required for this SAQ |
Now the opposite case: a payments startup that receives card numbers on its own API. It validates with SAQ D, needs quarterly internal and external scans, an annual penetration test, file integrity monitoring and logging, and often a QSA to review it for its bank partner. Cash cost lands in the $20,000 to $60,000 range before staff time, and a Level 1 service provider assessment starts above that. Same standard, a 20x difference, entirely from scope.
Is a PCI compliance platform worth it?
A platform pays for itself when PCI is not your only framework, because the controls overlap. One quarterly access review satisfies PCI DSS requirement 7.2.4, SOC 2 CC6.2 and ISO 27001 A.5.18 once, and a cross-mapped control set records it once. The platform does not run your ASV scan, perform your pen test or sign your Report on Compliance. What it replaces is the spreadsheet, the lost evidence and the week of scrambling before the assessor arrives.
If PCI is the only framework and you validate with SAQ A, a spreadsheet and a calendar reminder are a defensible choice. When the second framework arrives, or when the SAQ grows, software starts to cost less than staff time. Our guide to the best PCI compliance software compares the platforms by what each covers, and PCI DSS compliance software in Complies shows how scoping to your real SAQ works with the price on the page. The wider category pricing is in our compliance software pricing comparison.
What are the penalties for PCI non-compliance?
The PCI Council does not fine merchants. Penalties flow through your contract: the acquirer or processor charges non-validation or non-compliance fees, commonly quoted at $5,000 to $100,000 a month for large merchants in third-party guides and a few dollars to about $125 a month for small ones, and can raise your processing rates or end the relationship. After a breach, card brands can assess fines on the acquirer, which passes them to you, plus forensic investigation and card reissue costs. The cheapest control is a signed attestation on time.
Where do teams overspend on PCI?
- Buying a QSA engagement before scoping. If hosted fields keep card data off your systems, a QSA is usually not required for a small merchant. Confirm with your acquirer.
- Scanning every IP. ASV scanning is priced per IP or per scan. Scan only the systems in scope, and keep a current list.
- Treating PCI as separate from SOC 2 and ISO 27001. Access reviews, vendor reviews and policy approval overlap. Build them once. Our page on SOC 2 audit cost shows the same overlap on the audit side.
- Letting scans fail. A failed quarterly scan means rescans and urgent patching. A calendar reminder and a named owner are cheaper.
- Ignoring the version change. PCI DSS v4.0.1 made the future-dated requirements mandatory from March 31, 2025, including payment page script controls in requirements 6.4.3 and 11.6.1 for e-commerce sites. Budget for them if you serve a payment page.
Compliance spend sits next to every other line in a growth-stage budget, including hires such as an AI marketing lead for growth-stage companies that some teams now use before a first marketer. Putting PCI on a fixed, published cost helps you plan both.
How do you keep PCI cost down year after year?
Run PCI as a calendar, not a project. Put the quarterly scan, the six-month access review required by 7.2.4, the annual SAQ and the annual policy review on one schedule with named owners and attach each result as dated evidence. Teams that do this spend the same hours every year instead of a panic in the month before the attestation is due. If an internal review of the program is part of your plan, see how internal audit software for ISO 27001 and SOC 2 programs tracks findings to closure.
Questions about PCI DSS compliance cost
How much does PCI compliance cost per year?
A small merchant that validates with a self-assessment questionnaire typically spends about $1,000 to $10,000 a year in third-party estimates, mostly scans, tooling and staff time. A business needing a QSA and Report on Compliance commonly spends $25,000 to $200,000 or more. Your acquirer and scope decide which applies.
Do small businesses have to be PCI compliant?
Yes. Any business that accepts card payments is bound by its merchant agreement to follow PCI DSS, whatever its size. Small merchants usually validate with a self-assessment questionnaire and, where required, quarterly ASV scans, rather than a formal on-site assessment.
How much does a PCI ASV scan cost?
Third-party sources quote about $100 to $200 per IP address a year, and $400 to $2,000 a year for a typical small footprint. The scan must be performed by an Approved Scanning Vendor listed by the PCI Council, at least once every three months under requirement 11.3.2.
Who sets the fee for PCI compliance?
Nobody sets one fee. The PCI Security Standards Council publishes the standard and does not charge merchants. Costs come from the vendors you hire and from your acquirer, which may charge a monthly non-validation fee if you have not submitted your attestation.
Can software make us PCI compliant?
No tool certifies you. Software tracks requirements, evidence and deadlines and shows gaps early. The scan comes from an ASV, a Report on Compliance comes from a QSA and the attestation is signed by you. Used well, software shortens the work and lowers the chance of a missed deadline.
Ready to see where your PCI program stands? Start with the PCI DSS readiness score and plan from $47 a month billed yearly.
RUN IT, NOT JUST READ IT
Turn this into tracked rows with owners
Everything in this guide becomes obligations, controls, and evidence with owners and due dates inside Complies, with a live readiness score on top. Plans from $47 a month, prices published.