Skip to main content
Compliance

PCI Compliance Cost: What Merchants Pay For, and Who Sets Each Fee

PCI compliance cost: what PCI SSC does and does not charge, who sets non-compliance fees, what drives validation costs, and how an MSP scopes it for a client.

G
GetCybr Research
··10 min read
MSP adviser reviewing PCI DSS validation costs and acquirer non-compliance fees for a merchant client

Key Takeaways

PCI compliance cost is paid to several parties, and the PCI Security Standards Council is not one that sets merchant fees. This guide separates validation costs (self-assessment, a QSA assessment, quarterly ASV scans) from the non-compliance fees that card brands and acquirers apply under their own contracts, says honestly where no published price exists, and shows an MSP how to scope and price PCI DSS v4.0.1 work for a merchant client. No dollar figures are given because no source states one that could be verified. Sources read on 21 November 2026.

PCI compliance cost is not one price paid to one body. Merchants pay for the work of validating and fixing, and may be charged by their acquirer if they do not. The PCI Security Standards Council (PCI SSC) writes the standard and does not set any of those fees. This guide separates what each party charges, as read on 21 November 2026, says plainly where no published price exists, and shows an MSP how to scope and price PCI DSS work for a client. It gives no dollar figures because we found no source for one that could be verified.

What you are paying for

Five different costs sit behind “PCI compliance cost”, paid to different parties.

  • Validation by self-assessment. PCI SSC describes the Self-Assessment Questionnaires (SAQs) as “validation tools for use by SAQ-eligible merchants and service providers to perform and report the results of their PCI DSS self-assessments”, per PCI SSC FAQ 1215. The merchant completes it. Each SAQ has eligibility criteria that must all be met, and the merchant checks with its acquirer or payment brand which applies.
  • Validation by a QSA. Qualified Security Assessor (QSA) companies are “independent security organizations” that PCI SSC has qualified to validate an entity’s adherence to PCI DSS, according to the PCI SSC program listings. The QSA sets its own fee.
  • Quarterly external scans. An Approved Scanning Vendor (ASV) provides “external vulnerability scanning services” for the external scanning requirement, per the same page. PCI SSC FAQ 1234 says a scan report is not an indication that any other requirement is in place.
  • The work of meeting the requirements. Scoping, network and system changes, policies, evidence and ongoing operation against PCI DSS v4.0.1. PCI SSC announced v4.0.1 as a limited revision on 11 June 2024 and said v4.0 would be retired on 31 December 2024, after which v4.0.1 would be the sole active version, per the PCI SSC blog. This is the largest variable and nobody publishes a price for it, because it depends on the merchant’s card data environment.
  • Non-compliance fees. Charged by card brands and acquirers under their own contracts, not by PCI SSC. See the next section.

Who sets non-compliance fees

The PCI Security Standards Council says it “does not manage compliance programs and does not impose any consequences for non-compliance”, and that payment brands may have their own compliance initiatives “including financial or operational consequences”, in FAQ 1015, an FAQ dated April 2012. FAQ 1004 says the Council will not be replacing the individual brands’ compliance programs and that each participating brand determines what entities must be compliant, including any brand-specific enforcement programs.

Visa shows how a brand’s programme works. On its own page, Visa says “Visa may assess a non-compliance assessment to the issuer or acquirer”, and that “The issuer or acquirer is responsible for paying all assessments”. Whether an acquirer then charges a merchant, and how much, is set in the contract between them. Acquirers commonly charge for non-validation or for running a PCI programme, but that varies, so read your merchant agreement and statements. The page we read states no dollar amount, so this guide states none. We could not fetch Mastercard’s own programme document, so we say nothing about its fees.

Merchant levels

Merchant levels come from the card brands, not PCI SSC. Visa says “A merchant’s total Visa transaction volume over a 12-month period determines your merchant level” and that “Acquirers must ensure that their merchants validate at the appropriate level”. PCI SSC’s merchant page says “Whether a small merchant is required to validate compliance is determined by the individual payment brands” and that merchants should consult their acquirer or payment brand, per PCI SSC. The merchant level, and so the validation route (an SAQ or a QSA’s Report on Compliance), is a question for the acquirer.

What it costs, component by component

No row below carries a price, because no source states one that could be verified. Where a row has no price it says so.

Component Who sets the price Typical driver Source
PCI DSS v4.0.1 and the SAQs Published by PCI SSC Which SAQ’s eligibility criteria the merchant meets No price stated on the pages read, per PCI SSC FAQ 1215
Self-assessment (SAQ) The merchant, with any help it buys Which SAQ applies; the size of the card data environment No published price. The merchant completes it, per PCI SSC FAQ 1215
Report on Compliance by a QSA The QSA company Scope and size of the environment; level set by the brand No published price. QSAs are qualified by PCI SSC but set their own fee, per the program listings
Quarterly external vulnerability scan The ASV Number of internet-facing systems No published price. Quarterly scans by an ASV, per PCI SSC FAQ 1234
Remediation and ongoing operation The merchant, you or a consultant State of the card data environment No published price. Practitioner estimate only
Card brand non-compliance assessment The card brand, via issuer or acquirer Brand rules and the merchant agreement No dollar amount stated, per Visa
Acquirer pass-through or program fee The acquirer, in the merchant agreement The contract and the merchant level No published price. Check your merchant agreement

Delivering this for a client as an MSP: how to scope and price it

This section is practitioner guidance, not a published rate. It gives a method; the numbers have to be yours.

  1. Ask the acquirer first. The acquirer decides the merchant level and what validation it accepts, so start by asking it in writing which level applies and whether it needs an SAQ, a Report on Compliance and ASV scan reports.
  2. Scope the card data environment. List where card data is stored, processed or transmitted, and the systems and people connected to it. A smaller scoped environment is a smaller job. Check each SAQ’s eligibility criteria: PCI SSC says all must be met before one is used.
  3. Price readiness in hours. Estimate hours per requirement area for this client’s environment, multiply by your own cost per delivery hour, and add the margin you need. The vCISO cost guide has a worked method for turning hours and margin into a fee; use your own rates, not a market average.
  4. Treat the QSA and ASV as the client’s purchases. Ask two or three providers to quote the same scope in writing and show each fee as its own line, so the client can see what goes to them and what is your service.
  5. Keep acquirer and brand fees out of your price. They are set in the client’s merchant agreement. Show the client where to find them rather than estimating them.
  6. Put assumptions in a written quote. State what is in scope, what is excluded, who pays for remediation tooling, and what happens if the acquirer asks for more validation.

If software helps you deliver the work, its cost per client belongs in your cost base. See GetCybr pricing for current prices; this guide does not restate them.

Where GetCybr fits

GetCybr publishes this guide, so weigh this section accordingly. GetCybr is multi-client GRC software for MSPs, consultancies and vCISO practices. Its framework library lists PCI DSS v4.0.1, written in GetCybr’s own wording and mapped to the Secure Controls Framework, so a merchant client’s PCI work can sit beside its other frameworks.

GetCybr’s AI interview asks the assessment questions and drafts control maturity, and nothing is saved until your reviewer applies it. A built-in vCISO assistant answers questions about each client and proposes actions. Nothing runs until you confirm.

GetCybr does not certify anyone and is not a QSA or an ASV. A Report on Compliance comes from a QSA and scan reports from an ASV, and GetCybr does not change what they or an acquirer charge, which is why no GetCybr price appears in the table.

Frequently asked questions

How much does PCI compliance cost?

There is no single price and none is published by the PCI Security Standards Council. The cost depends on how a merchant validates: a Self-Assessment Questionnaire it completes itself, a Report on Compliance from a QSA, and quarterly scans by an ASV where required. QSAs and ASVs set their own prices. As read on 21 November 2026, we did not find two providers’ own price pages that we could verify, so this guide gives no figure.

Does PCI SSC charge a non-compliance fee?

No. PCI SSC FAQ 1015, read on 21 November 2026, says the Council “does not manage compliance programs and does not impose any consequences for non-compliance”. Consequences come from the payment brands’ own programs and from acquirers under their contracts.

Who sets PCI non-compliance fees?

Card brands and the acquirers that contract with merchants. On its own page, as read on 21 November 2026, Visa says it “may assess a non-compliance assessment to the issuer or acquirer”, and that the issuer or acquirer is responsible for paying all assessments. Whether an acquirer passes that cost to a merchant, and how much, depends on your merchant agreement, so check it. No dollar figure is stated on Visa’s page.

What is my PCI merchant level?

The card brands define merchant levels, not PCI SSC. Visa says a merchant’s total Visa transaction volume over a 12-month period determines its merchant level, and PCI SSC says whether a small merchant must validate compliance is determined by the individual payment brands. Ask your acquirer which level applies and what validation it requires.

Is an ASV scan enough to be PCI compliant?

No. PCI SSC FAQ 1234, read on 21 November 2026, says an ASV scan report is not an indication that any other PCI DSS requirements have been reviewed or are in place. Quarterly external scans by an ASV are one requirement among many.

How should an MSP price PCI work for a merchant client?

Separate your service from the client’s other costs. Quote scoping and remediation in hours at your own cost per delivery hour, show any QSA fee and ASV scan fee as the client’s cost from a written quote, and keep acquirer fees out of your price. Do not use a market-average rate as yours.

Sources

Read on 21 November 2026. Statements and quotations in this guide are taken from these pages.

Fees and programme rules can change, so check your merchant agreement and ask your acquirer.

Next step

If you run compliance services across many MSP clients, you can become a partner.

Run compliance and vCISO work for every client

MSPs: put the repeatable assessment, roadmap, and reporting work on GetCybr while your team stays in control of every client relationship.