Build vs White-Label: What a Payment Gateway Actually Costs to Run Yourself
A gateway's PCI validation and Visa registration are not one-time events. They are permanent operating obligations a white-label product already carries.

- PCI DSS lets a card network or acquirer require a service provider to validate through a full Report on Compliance rather than a simpler self-assessment questionnaire. A payment gateway handling other merchants' cardholder data is squarely the kind of entity pushed into that heavier validation path.
- PCI DSS Requirement 12.9 is a binding, ongoing obligation specific to being a third-party service provider: actively supporting every customer's own compliance monitoring and providing evidence that the gateway meets applicable requirements, for as long as the relationship lasts, not a one-time certification exercise.
- Visa Core Rules Section 1.9.8.6 requires a Member to register a Third Party Agent with Visa before it performs any contracted services or transaction activity, and that registration information has to be reviewed and updated annually. A self-built gateway connecting into Visa's network inherits this registration and maintenance obligation directly.
- None of this reflects engineering quality. A perfectly built gateway still carries the same validation path, the same Requirement 12.9 obligation, and the same registration requirement as a poorly built one, because these are structural program costs tied to the role the gateway plays, not to how well it was coded.
Build versus white-label for a payment gateway comes down to a cost most comparisons miss entirely. It is not the engineering cost of writing the software. A gateway’s real, permanent cost is the compliance program that has to exist underneath it, validated once and then maintained forever, regardless of how well the software itself is built.
The validation path a payment gateway cannot avoid
PCI DSS applies different validation paths depending on an entity’s role, and the standard’s own text is specific about who decides which path applies. Whether an entity validates through a full Report on Compliance or a simpler self-assessment questionnaire is, in the standard’s own words, at the discretion of the organizations that manage compliance programs, meaning the payment brands and acquirers an entity actually works with. A payment gateway that stores, processes, or transmits other merchants’ cardholder data on their behalf is a textbook PCI DSS service provider, and service providers are routinely pushed into the heavier Report on Compliance path specifically because of the risk concentration a gateway represents.
A Report on Compliance is a materially different undertaking than a merchant’s self-assessment questionnaire. It typically requires engagement with a Qualified Security Assessor, detailed evidence gathering across the full environment, and a formal Attestation of Compliance submitted to whichever payment brand or acquirer is requesting it. This is not a cost that scales down for a smaller gateway operation. The assessment covers the same ground regardless of transaction volume, because the risk PCI DSS is addressing, cardholder data moving through the gateway’s systems, exists at any volume.
The obligation that never ends once you are certified
The heavier validation path is not even the largest ongoing cost. PCI DSS Requirement 12.9 creates a standing obligation specific to being a third-party service provider, and it does not expire once an assessment is complete. A service provider must acknowledge in writing to its customers that it is responsible for the security of account data it possesses, and it must support its customers’ own compliance obligations by providing the information customers need to monitor the service provider’s compliance status, along with evidence that the service provider is actually meeting the requirements its services are supposed to satisfy.
A gateway operating under this requirement is not done once a Report on Compliance is filed. It has to maintain a process for sharing its own Attestation of Compliance with every customer who asks, respond to customer requests for evidence of ongoing compliance, and be prepared to demonstrate this continuously, because every customer relying on the gateway has its own PCI DSS obligation that depends on the gateway actually meeting this standard. This is a genuine, recurring operational function, not a document that gets filed once and forgotten. A gateway with a hundred active merchant customers is running this support function for all hundred relationships simultaneously, indefinitely.
The registration a self-built gateway cannot skip
A gateway that connects directly into a card network’s own infrastructure to process transactions takes on a second, separate obligation that has nothing to do with PCI DSS at all. Visa Core Rules Section 1.9.8.6 requires a Member, the sponsoring bank or acquirer behind the gateway’s network access, to register that gateway as a Third Party Agent with Visa before it performs any contracted services or transaction activity on the Member’s behalf. Registration has to happen through Visa’s own Program Request Management application, and Visa may deny or reject that registration at any time, with or without cause.
This registration is not a one-time filing either. The same section requires the Member to maintain accurate, complete, and current information about the registered Third Party Agent, and to review and update that information on an annual basis, following any change, or whenever Visa requests it. A self-built gateway connecting into Visa’s network inherits this entire registration and maintenance relationship, running on its own schedule, independent of the PCI DSS validation path and the Requirement 12.9 obligation already sitting on top of it.
Why none of this disappears if you build thoughtfully
A team that builds a genuinely excellent gateway, clean code, strong security architecture, thoughtful API design, does not build its way out of any of these three obligations. The Report on Compliance validation path, the Requirement 12.9 ongoing support function, and the Visa Third Party Agent registration and annual maintenance requirement all attach to the role a gateway plays in the payment ecosystem, not to the quality of its engineering. A beautifully engineered gateway and a mediocre one face the identical compliance program requirements, because PCI DSS and Visa’s own rules are testing what the gateway does and who it does it for, not how well the code was written to do it.
This is the part of the build-versus-white-label decision that a technical feasibility study almost always misses. A team can accurately conclude that building the gateway’s actual functionality is achievable within a reasonable engineering budget and timeline. That conclusion says nothing about whether the business can sustain the compliance program that has to run underneath that functionality for as long as the gateway operates, which is a separate, parallel cost center with its own specialized staffing and ongoing institutional relationship requirements.
What white-label is actually buying
A white-label gateway provider has already absorbed every one of these costs. Its Report on Compliance validation already exists and gets renewed on its own cycle. Its Requirement 12.9 support function is already built and already running for every customer on the platform. Its Visa Third Party Agent registration is already in place and already being maintained annually. A reseller licensing that white-label product is not simply buying a piece of software with a familiar feature set. It is buying access to a compliance program that someone else already built, staffed, and is actively maintaining, with the reseller’s own branding layered on top of it.
This reframes the actual comparison a company evaluating build versus white-label should be running. The question is not whether the engineering team can build equivalent gateway functionality. It is whether the business is prepared to stand up and permanently staff a Report on Compliance validation cycle, a Requirement 12.9 customer-support function, and a Visa registration relationship, on an ongoing basis, for as long as the gateway exists, as a cost center that exists independently of how much gateway revenue the business actually generates.
The staffing question most build decisions skip entirely
Each of these three obligations needs a specific kind of ongoing attention that is easy to underestimate when a decision is being driven primarily by an engineering timeline. The Report on Compliance cycle needs someone who can actually prepare for and manage a Qualified Security Assessor engagement year after year, not just once at launch. The Requirement 12.9 support function needs someone who can respond to customer compliance inquiries promptly and accurately, since a slow or incomplete response can itself become a problem for a customer relying on the gateway to satisfy its own PCI DSS obligations. The Visa registration needs someone tracking the annual review deadline and keeping the underlying Member relationship informed of any change.
None of these roles disappears once the gateway is built and launched. They are permanent additions to the organization’s headcount and institutional knowledge, running for as long as the gateway operates, regardless of how much of the actual engineering work is ever revisited again after launch. A build-versus-white-label decision that only compares engineering costs, without pricing in these three ongoing roles, is comparing a fraction of the real decision against the whole of it.
A concrete example: two companies, same features, different real cost structure
Picture two ISOs, each wanting to offer a branded gateway product to their merchant base. The first builds its own gateway with a strong engineering team over eight months, launches with feature parity to established competitors, and immediately discovers it needs a Qualified Security Assessor engagement, a formal Requirement 12.9 support process for every merchant it onboards, and a Visa Third Party Agent registration that has to be requested, approved, and then reviewed annually going forward. None of this was in the original engineering budget, because the engineering team scoped software development, not a permanent compliance program.
The second ISO licenses a white-label gateway from an established provider, configures its branding, and launches within eight weeks. Its white-label partner has already cleared the Report on Compliance validation, already runs the Requirement 12.9 support process across its entire customer base, and already maintains its own Visa registration. The second ISO’s actual gateway functionality looks nearly identical to the first’s from a merchant’s perspective. Its underlying cost structure, and the compliance staffing it has to carry permanently, is entirely different.
What to actually calculate before building
A company seriously evaluating build versus white-label should price out the Report on Compliance validation cycle specifically, including the ongoing Qualified Security Assessor relationship it requires, as a recurring cost rather than a one-time project expense. It should staff and budget for the Requirement 12.9 support function as a permanent operational role, not a feature to ship once. And it should confirm, before committing to build, whether its sponsoring Member or acquirer relationship can actually support registering and annually maintaining a Visa Third Party Agent registration for a gateway the company controls directly.
Running that calculation accurately, against a specific company’s real compliance staffing capacity rather than an engineering team’s software estimate alone, is exactly the work behind Midcore’s white-label payment gateway consulting engagements. Where the broader banking relationship behind the gateway needs its own evaluation, banking-as-a-service consulting is where that foundational structure gets worked through. And for a platform weighing the same build-versus-partner tradeoff for payment facilitation rather than a gateway specifically, PayFac-as-a-Service consulting is where that parallel calculation gets run.
Frequently Asked Questions
Isn’t PCI compliance just a one-time certification a gateway completes and moves on from?
No. PCI DSS Requirement 12.9 specifically requires a third-party service provider to continuously support its customers’ own compliance monitoring, providing information and evidence that the service provider is meeting applicable requirements, for as long as the relationship exists. A gateway’s compliance obligation does not end when a Report on Compliance is signed. It runs for every customer, every year, for the life of the business.
Does a self-built gateway actually need to register with Visa directly?
If it connects into Visa’s network to perform contracted services or transaction activity on a Member’s behalf, yes. Visa Core Rules Section 1.9.8.6 requires the Member to register that Third Party Agent before any contracted services or transaction activity begins, and requires the Member to review and update that registration information annually, following any change, or upon Visa’s request. A white-label provider has already cleared this requirement. A self-built gateway has to clear it independently.
What is white-label actually buying a reseller out of, if not the software itself?
The compliance program sitting underneath the software: an existing Report on Compliance validation, an existing Requirement 12.9 process for supporting every customer’s own compliance needs, and an existing Visa or card network registration already in good standing. A reseller licensing a white-label gateway is buying access to a program that already absorbed these costs, not just a piece of software that happens to process transactions.
Sources: PCI Security Standards Council, Payment Card Industry Data Security Standard, Version 4.0.1, Requirement 12.9 and the Assessment Process guidance, and Visa Core Rules and Visa Product and Service Rules, Section 1.9.8.6.