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

PCI/AoC isn't a cost — it's what closes your enterprise deals

The quote arrives, lands in the budget somewhere between legal fees and infrastructure, and gets filed under overheads: a thing you pay for because someone makes you.

That framing is expensive, and not because of the invoice. It's expensive because it puts the work at the back of the queue, behind revenue. Then a deal turns up that needs it, and the sequence runs backwards — sign the intent, discover the requirement, scramble for months while the contract sits unsigned.

Look at where the document actually gets used and a different picture appears. The output of a PCI DSS assessment isn't a certificate for the wall. It's commercial infrastructure: the artefact that lets a large customer's procurement function say yes to you.

What is an AoC, and how is it different from a RoC?

Some plain-English definitions first, because the acronyms hide what's going on.

PCI DSS is the Payment Card Industry Data Security Standard — twelve requirement areas, currently at version 4.0.1, published by the PCI Security Standards Council. It applies to any organisation that stores, processes or transmits payment card data, or that can affect the security of someone else's card data.

CDE is your cardholder data environment: the systems that touch account data, plus everything that can affect their security.

SAQ is a Self-Assessment Questionnaire — a validation document you complete yourself, in one of several types depending on how you accept payments.

RoC is a Report on Compliance: the full assessment, documented by a Qualified Security Assessor (QSA) or an internal assessor, running to hundreds of pages.

AoC is the Attestation of Compliance — the official PCI SSC form on which a merchant or service provider attests to the results of an assessment, whether that assessment was documented in an SAQ or a RoC. It's short. It's signed. It names the assessed entity, the scope, the validation path, the assessor and the date.

When a partner writes "please send us your PCI," they mean the AoC. Nobody in procurement wants to read a RoC. They want the page that tells them who was assessed, what was in scope, who signed it, and when it expires.

One correction worth making early, because it changes how you talk to your own board: there is no such thing as PCI certification. The Council doesn't certify merchants or service providers. You validate compliance for a point in time, and your acquirer or the card brands decide what validation they will accept from you. Anyone selling you a "PCI certificate" is using marketing language rather than standard language.

Why does enterprise procurement ask for your AoC?

Nobody at your enterprise prospect is asking out of curiosity. Three separate mechanisms produce the request, and they arrive from different directions.

Their own compliance obligation cascades to you. If your customer handles card data, PCI DSS requires them to manage the third-party service providers who handle it on their behalf — maintaining a list of those providers, holding written agreements about responsibility, and monitoring their compliance status at least annually. Your AoC is how they discharge that obligation. Without it, their next assessment has a gap with your company's name on it. That isn't a preference they can waive for you.

Registration and scheme requirements. Depending on how the relationship works, a partner may need you registered and validated with the card brands. Visa maintains a public Global Registry of Service Providers, and getting listed depends on validated compliance. Some partners check the registry before they check your pitch deck.

Vendor security review as a gate. Any company large enough to have a procurement function has a security questionnaire, and that questionnaire has a PCI field. A signed AoC answers in one line what forty questions otherwise circle around. It's the difference between a review that clears in a week and one that generates three rounds of follow-up.

The pattern that follows is consistent: the deal doesn't die; it stalls. Nobody says no. Legal has no problem. Your champion still wants you. But the security review can't be closed out, and the contract sits in a queue behind a document you don't have yet.

The real cost is the timing, not the fee

Here's the arithmetic that never makes it into the budget conversation.

A first RoC-path assessment typically runs three to six months end to end for a company that hasn't been through one — scoping, remediation, evidence, fieldwork, report. That isn't an outrageous timeline. It's a perfectly manageable one, if it runs in parallel with your roadmap.

It becomes painful in exactly one scenario: when it starts after the deal is already on the table. Then the same three to six months lands entirely inside your sales cycle. A quarter of revenue moves to the next quarter. Your engineers stop shipping to chase evidence. And you negotiate from the weakest position available — the one where the customer knows you need this more than they do.

The fee is roughly the same either way. What changes, depending on when you start, is how much of that timeline your pipeline pays for.

A founder called us last year in exactly that position: an enterprise customer had put a signed-in-principle deal on hold pending proof of PCI compliance, and that deal was most of the coming quarter. He assumed it meant a frozen roadmap. It didn't have to. We scoped tightly, ran remediation in parallel with their build, and pulled evidence through automation instead of putting engineers on screenshot duty. They kept shipping, and the deal closed. But the cheapest version of that story is the one where the AoC already exists when the question arrives.

Under v4.0.1, "we're compliant" has to mean something different

There's a second reason to stop treating this as an annual expense, and it comes from the standard itself.

Version 4.0.1's future-dated requirements — the set that became mandatory on 31 March 2025 — push heavily toward controls that must operate continuously rather than be demonstrated once: multi-factor authentication across the CDE, ongoing monitoring, payment-page script integrity, targeted risk analyses justifying the frequency you've chosen for flexible requirements. Service providers carry additional obligations, including validating that scoping remains accurate every six months rather than annually.

The practical consequence: a folder of screenshots from last spring is not compliance. It's a snapshot. If your controls only run in the weeks before an assessment, the next cycle is where that shows — and a lapsed or narrowly-scoped AoC in front of a sophisticated buyer raises more questions than no AoC at all.

Which is also the opportunity. Build the controls to run continuously and annual validation stops being a project. It becomes a report on something that was already true, and the AoC becomes a document you produce on request rather than a programme you have to launch.

How to turn your AoC into a sales asset

Five things worth doing, roughly in order.

Ask your acquirer, in writing, what they expect. Which level, which validation path, which deliverable. One email removes the single largest source of wasted effort we see — companies building toward the wrong deliverable for two months.

Get scope right before you build toward it. Scope decides cost, duration and how much of your product the assessment touches. Tokenisation, hosted payment fields and tested segmentation shrink the CDE; an hour of assessor time at the scoping stage is the highest-value hour in the whole project.

Read the scope statement on your AoC, not just the signature. An AoC covering a legal entity and environment that isn't the one your customer is buying from will not survive a competent security review.

Treat the expiry date as a commercial deadline. Validation is point-in-time. A gap between cycles is a gap in your ability to answer procurement — usually discovered at the worst moment.

Put it in the sales motion. Sales should know what the AoC covers, what its date is, and how to send it under NDA without escalating to engineering. If answering "are you PCI compliant?" takes three days and a Slack thread, you have a document but not an asset.

Frequently asked questions

What's the difference between a RoC and an AoC?

The RoC is the full assessment report — hundreds of pages, produced by a QSA or internal assessor, for your acquirer and your own records. The AoC is the short signed attestation form summarising the result. Both the SAQ path and the RoC path produce an AoC, and the AoC is the document you share with partners and customers.

Do we need an AoC before we have enterprise customers?

Not always — but if enterprise or partner revenue is in your plan for the next two quarters, starting before the request arrives is the difference between a parallel project and a stalled deal. First-time assessments commonly take three to six months.

Can we share our RoC with a customer instead?

Rarely appropriate, and seldom wanted. The RoC contains detailed information about your environment and controls. The AoC exists precisely so you can evidence compliance without handing over an architecture map.

Who signs the AoC?

An executive officer of your organisation signs the attestation, and where a QSA performed the assessment, the assessor signs their section too. That signature is why the document carries weight with a third party.

How long is an AoC valid?

It attests to a point-in-time assessment and is refreshed on an annual validation cycle. Service providers also have interim obligations, including confirming scope accuracy every six months.

Where to go next

If a partner or enterprise prospect asked you for an AoC tomorrow, the useful question isn't whether you'd eventually get one — it's how many weeks it would take, and whose quarter pays for them.

That's a one-hour conversation: your architecture on a screen, a clear answer on what's actually in your CDE, which validation path applies, and a realistic timeline. Book a scoping call, and we'll tell you where you stand, whether or not you end up working with us.

Mölnir is a QSA-led cybersecurity and compliance partner for payment companies. 100+ PCI DSS audits delivered, 30+ enterprise clients.

Comments

Be the first to comment.

Leave a comment