Guard Policy CloudEnterprise Underwriting Intelligence
Compliance

What PCI DSS 4.0 Compliance Costs a Mid-Size Online Merchant, Worked Through

At 2 million card transactions a year, your first-year PCI bill can run from roughly $20,000 to $400,000. Checkout architecture decides which. Here's a line-by-line budget for three designs.

By the Guard Policy Cloud editorial team · November 2026 · 8 min read

Why a 2-Million-Transaction Merchant's PCI Bill Can Swing Tenfold

If your online store processes about 2 million card transactions a year, your first PCI DSS compliance cost under version 4.0.1 depends less on the standard than on one engineering choice: where card numbers travel. A merchant whose servers handle raw card data can spend well over $300,000 in year one once assessment fees, testing, tooling and staff time are counted. The same merchant using a hosted payment page or iframe-based fields from its payment service provider (PSP) can often get through for a fraction of that, frequently under a fifth.

Start with your merchant level. Under Visa's widely used thresholds, 1 to 6 million transactions a year makes you Level 2. That usually means a Self-Assessment Questionnaire (SAQ) rather than a full Report on Compliance (ROC) written by a Qualified Security Assessor (QSA). In practice it's often stricter. Mastercard expects self-assessing Level 2 merchants to have either an internal auditor trained as an Internal Security Assessor (ISA) or a QSA. Your acquiring bank can also demand a full ROC, especially after a breach or if you're growing toward Level 1. Thresholds and enforcement vary by card brand and region, so get your acquirer's requirement in writing before you budget.

Advertisement

The future-dated 4.0 requirements became mandatory on March 31, 2025. Year one therefore includes controls many merchants never paid for under 3.2.1. For e-commerce, the costliest are payment-page script management (6.4.3) and tamper detection (11.6.1).

One Hypothetical Merchant, Three Checkout Designs

Hypothetical worked example: say an online retailer with 120 employees sells across Europe, the Middle East and Asia-Pacific and runs about 2 million card transactions a year. Its IT team is small: two infrastructure engineers and a part-time security lead. The table shows its first-year budget under three checkout designs. Figures are typical 2026 market ranges in USD. They vary by contract, region and scope, so confirm them with vendors.

Cost lineA: Own card form, data hits merchant servers (SAQ D / ROC)B: Direct post or JavaScript fields served by merchant page (SAQ A-EP)C: PSP iframe or redirect with tokenization (SAQ A)
Gap assessment$10k–$20k$6k–$12k$0–$5k
QSA ROC or QSA/ISA-supported SAQ$35k–$70k$10k–$30k$5k–$15k
Quarterly ASV scans$1k–$3k$1k–$3k$500–$2k
Penetration testing$20k–$45k$10k–$25k$0–$12k (optional)
Payment-page script monitoring$5k–$20k$5k–$20k$0–$10k
Logging, FIM, vulnerability management, MFA$30k–$80k$10k–$30k$2k–$10k
Remediation consulting$20k–$60k$10k–$25k$0–$5k
Internal staff time (loaded cost)$60k–$120k$25k–$60k$10k–$25k
Year-one total$181k–$418k$77k–$205k$18k–$84k

Two things drive the gaps. The first is the number of applicable requirements: SAQ D covers essentially the whole standard, SAQ A-EP a substantial subset, SAQ A a small set. The second is the number of systems in scope. Under design A, every web server, application server, database, jump host and logging system that touches card data, or could affect its security, gets assessed and tested.

Staff time is the line finance teams most often leave out, and it's frequently the largest. Loaded engineering costs in India or Southeast Asia will sit at the low end of the range. In the UK, Western Europe, the Gulf or North America, expect the high end or beyond.

Line by Line: QSA Fees, ASV Scanning Cost and Penetration Testing

QSA assessment

QSA audit fees scale with assessor days. A mid-size ROC for design A commonly needs somewhere between 10 and 25 days of evidence review, interviews and report writing, though scope can push that well beyond. Day rates differ widely. Large global consultancies charge more than regional QSA firms, and firms based in India, Eastern Europe or Latin America often quote well below London or New York for similar scope. For design C, many merchants pay a QSA a few days' fee to check SAQ eligibility and review the completed questionnaire. It's usually worth it, since filing the wrong SAQ is a common problem after an incident.

ASV scans

Requirement 11.3.2 calls for quarterly external vulnerability scans by an Approved Scanning Vendor, and even SAQ A merchants generally need them. For a handful of public IPs, ASV scanning cost is low: often bundled by acquirers, or a few hundred to a few thousand dollars a year. The hidden cost is remediation. Every failing scan must be fixed and rescanned before you get a passing quarter, so budget engineering hours as well as the license.

Penetration testing

Requirement 11.4 requires internal and external penetration tests at least annually and after significant changes. Segmentation testing is also required if you use segmentation to reduce scope, and service providers must repeat it every six months. For design A, expect separate scoping for network, application and segmentation work. SAQ A-EP adds external testing of the payment page environment. SAQ A doesn't require a pen test. Even so, a focused web application test of the checkout flow, perhaps $8,000 to $12,000, is cheap insurance, and some cyber insurers ask about testing at renewal.

Red flags when buying:

  • A pen test quote that names no methodology and includes no retest.
  • A QSA firm that also sells the remediation tooling it then assesses.
  • ASV reports with no false-positive dispute process.

Budgeting for Payment-Page Scripts Under Requirements 6.4.3 and 11.6.1

These 4.0 requirements surprise e-commerce finance teams most. Requirement 6.4.3 says every script running on the payment page in the shopper's browser must be inventoried, authorized and integrity-checked, with a written justification for each. Requirement 11.6.1 requires a mechanism that detects unauthorized changes to the page's HTTP headers and content, run at least weekly or at a frequency set by your targeted risk analysis. Both target skimming attacks that inject malicious JavaScript into checkout pages.

You have three ways to comply:

  • Dedicated client-side security platforms such as Jscrambler, Feroot, Source Defense or cside. Pricing commonly runs from about $5,000 to $30,000 a year and scales with traffic and the number of protected pages.
  • CDN or WAF add-ons such as Cloudflare Page Shield or Akamai Page Integrity Manager. These are often cheaper if you already run on that network, though reporting depth for assessors varies.
  • In-house controls: Content Security Policy, Subresource Integrity hashes and a script inventory tied to change management. License cost is low, but engineering and upkeep are real, especially when marketing teams keep adding tags.

Design C changes the math. In its January 2025 revision of SAQ A, the PCI Security Standards Council removed 6.4.3 and 11.6.1 from that questionnaire. It added an eligibility condition instead: the merchant must confirm its site isn't susceptible to script attacks that could affect the embedded payment form. You still need evidence, which typically means a CSP, some monitoring or your PSP's documented guidance. Budget something here rather than zero.

For design B there's no shortcut. Your page serves the card fields, so both requirements apply in full. If you carry dozens of third-party tags, a commercial tool will usually cost less than building and maintaining this in-house.

How Tokenization and Hosted Payment Pages Cut the Bill

Tokenization reduces scope because systems that only ever see a token, not a primary account number (PAN), can fall outside the cardholder data environment, provided they can't reverse the token. Stripe, Adyen, Checkout.com, Braintree and Worldpay all offer hosted fields or redirect pages with vaulted tokens, usually priced into processing fees. Network tokens from Visa and Mastercard add protection for stored credentials. Regional rules sometimes push the same way: India's card-on-file tokenization rules bar most merchants from storing card numbers, and in Europe, strong customer authentication requirements make PSP-managed flows the practical default for many merchants.

In our hypothetical, moving from design A to design C saves on the order of $100,000 to $400,000 in year one, depending on where each cost line lands. Migration sits on the other side of the ledger. Rebuilding checkout, re-tokenizing stored cards through your PSP and retesting conversion often takes 6 to 16 engineering weeks. The case is strongest if you'd otherwise face a full ROC every year.

Before you commit, check these points:

  1. Map every place a PAN currently exists, including logs, call-center tools, refund workflows and data warehouses. Forgotten copies are what usually keep a merchant on SAQ D.
  2. Confirm with your acquirer which SAQ it will accept for the new design.
  3. Get your PSP's PCI Attestation of Compliance and responsibility matrix for the specific integration you'll use.
  4. Check whether recurring billing or marketplace payouts need card data. If you might switch providers, vault portability terms and network tokens matter.
  5. Brief your broker. Cyber insurers often ask about PCI status, and reduced scope can support better terms.

Here's the decision rule. If any system you operate stores, processes or transmits full card numbers without a regulatory or business reason, scope reduction will likely cost less than compliance within two years. Have a QSA confirm the target design's scope before you build it. For contractual or liability questions with your acquirer, involve qualified legal counsel.

Frequently asked questions

Does a Level 2 merchant always need a QSA?

Not always. Many card brands let Level 2 merchants self-assess with an SAQ. Mastercard, however, expects either an ISA-trained internal auditor or a QSA, and acquirers can require a full Report on Compliance. Ask your acquirer for its requirement in writing before you budget.

What is a realistic ASV scanning cost for a mid-size online store?

For a small number of public-facing IP addresses, quarterly ASV scans typically cost a few hundred to a few thousand dollars a year in 2026, and acquirers sometimes bundle them. The bigger expense is engineering time spent fixing failed findings and rescanning. Confirm pricing with vendors, because it scales with IP count and region.

If we use a hosted payment page, do requirements 6.4.3 and 11.6.1 still apply?

For merchants that qualify for SAQ A, the January 2025 revision removed those two requirements. It replaced them with an eligibility condition: you must confirm your site isn't susceptible to script attacks on the embedded payment form. You'll still need evidence for that, such as a Content Security Policy or monitoring. Merchants on SAQ A-EP or SAQ D must meet both requirements in full.

Written by the Guard Policy Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.