Skip to content
Services
PCI DSSISO 27001SOC 2GDPRPenetration TestingNIST CSFvCISODORA
Company
Case StudiesPartnersTrust CenterBlogGlossaryFAQFree AssessmentContact
Industries
FintechHealthcarePaymentsSaaS
AboutResourcesVeedar

PCI DSS for scaling payment companies — getting scope right

The good news: scope is not fixed. Most scaling payment companies can meaningfully shrink theirs. And the work to do that is cheaper than the work of auditing the larger version. This article covers how to figure out which path you are on, how to shorten that path, and what a first assessment actually involves.

Get free Assessment →

Not sure where your CDE actually begins? Get a free assessment of your current scope before you spend a dollar on an audit.

What does PCI DSS scope actually mean?

Your scope includes everything that stores, processes, or transmits cardholder data, as well as everything that can affect the security of those systems. In PCI DSS terms, this is your cardholder data environment, or CDE.

The second half of that sentence is where teams get surprised. It is not only the server that handles a card number. It is the admin laptop with access to that server, the logging pipeline that might capture a card number in an error payload, the support tool where an agent once pasted a PAN into a ticket, and the network the whole thing sits on if it is not segmented.

Four terms worth defining before going further:

  • CDE — cardholder data environment. The systems in scope.

  • SAQ — Self-Assessment Questionnaire. A self-attested compliance path.

  • RoC — Report on Compliance. A formal assessment documented by a QSA.

  • AoC — Attestation of Compliance. The one-page summary your partners actually ask for.

When a processor or enterprise customer says "send us your PCI compliance," they mean the AoC.

One detail worth knowing before your first audit: scope isn't a one-time exercise. Requirement 12.5.2 requires an annual scope confirmation — mapping every location card data flows through and every system that could impact the CDE if compromised, even ones that never touch a card number directly (an authentication server, a logging server, a failover site). Assessors validate that this confirmation happened; they don't do it for you.

Which compliance path are you on: SAQ or RoC?

Your path depends on transaction volume and how card data flows through your systems. Volume sets the floor; architecture sets everything else.

Transaction volume determines your level. For merchants, Level 1 is generally above 6 million card transactions per year across a single brand; for service providers, the common split is above or below 300,000 per year. Thresholds vary by card brand, and your acquirer can impose stricter requirements than the brand's default — which, in practice, is what happens most often to growing payment companies.

The distinction between SAQ A and SAQ A-EP is what catches people. Both feel like "we use a payment provider, so we're fine." They are not equivalent. If your own code is involved in collecting the card, even just the JavaScript that renders the form, you are likely in A-EP territory, and A-EP carries most of the weight of a real security programme.

One structural point worth understanding early: if you are moving from merchant status toward being a service provider, your obligations change category, not just degree. Plan for that transition before a partner forces the timing.

How do you reduce PCI DSS scope?

You reduce scope by reducing the number of systems that touch card data, and by making the boundary around the remaining systems provable. Four moves, in order of leverage:

  • Stop card data reaching your systems at all. Hosted payment fields or a redirect means the card number goes from the customer's browser to your provider without transiting your infrastructure. This is the largest scope reduction available.

  • Tokenize and stop storing PANs. Hold a token from your provider, not the primary account number. Tokenization is not compliance by itself, but it removes entire categories of systems from scope.

  • Segment the network. Segmentation is not a PCI DSS requirement in itself — the standard is explicit that it's a strongly recommended risk-reduction method, not a mandate. But without it, your CDE is your whole network (a "flat network"). With it, the CDE is a small, walled room, and only the walled room is in scope. The boundary has to be proven: a segmented system is out of scope only if it truly could not impact the CDE even if compromised, and Requirement 11.4.5 requires that the boundary be validated by penetration testing at least annually.

  • Find where card data leaks into non-payment systems. Logs, error tracking, support tickets, call recordings, backups, analytics payloads. A single log line containing a PAN drags that system into scope. Run data discovery before you scope, not after.

  • None of this is exotic. It is mostly architecture hygiene that happens to have a large compliance dividend.

  • What changed in PCI DSS v4.0.1, and why does it matter now?

  • PCI DSS v4.0.1 is the only active version of the standard. Version 4.0 retired at the end of 2024, and the 51 future-dated requirements introduced with v4.x became mandatory on 31 March 2025. There is no longer a transition period to sit inside.

  • Four changes matter more than the rest for scaling payment companies:

  • MFA for all access into the CDE, not only remote or administrative access. A wider rollout than teams expect, usually touching internal tooling, nobody thought of as in-scope.

  • Payment page script management. An inventory of scripts running on payment pages, justification for each, and assurance of their integrity. If you have ever added a marketing tag to a checkout page, this is about that.

  • Tamper and change detection on payment pages, monitoring HTTP headers and page content for unauthorised modification.

  • Continuous rather than annual posture. Automated log review, targeted risk analyses justifying control frequency — ongoing evidence rather than a once-a-year snapshot.

That last one is the real shift. Under v4.x, compliance is a state you must demonstrate on any given day, not a folder of screenshots from the week of the audit. Many companies did the minimum to clear the March 2025 deadline and are now approaching their first assessment cycle under rules that assume the controls have been running all along.

How long does PCI DSS certification take for a payment startup?

For most scaling payment companies, a first assessment takes about three to six months end to end. A lighter SAQ path can be considerably faster. The dominant variable is scope.

  • Scoping and gap assessment — 2 to 4 weeks. Map data flows, define the CDE, identify what fails today.

  • Remediation — 4 to 12 weeks. The variable part. Segmentation, MFA rollout, logging, policy work. Can and should run in parallel with your product roadmap.

  • Formal assessment and report — 2 to 4 weeks. Evidence collection, testing, RoC and AoC production.

Companies that tokenize and use hosted payment fields compress this substantially, because remediation shrinks along with the CDE.

Where to start this week

If you are heading toward a first assessment, the order that saves the most money is: map your card data flows, decide which path you want to be on, do the architectural work to qualify for it, and only then bring in an assessor.

That sequence is unglamorous, and it is where the savings live. Getting scope right does not just reduce the audit — it reduces the permanent security burden your team carries afterwards.

Talk it through with a QSA. If you want a straight answer on where your cardholder data environment actually begins and which path you qualify for, book a scoping call. We have delivered 100+ audits for payment companies and the first conversation is about scope, not scoping fees.

Get free Assessment →

See exactly where you stand against PCI DSS v4.0.1

Comments

Be the first to comment.

Leave a comment