What a White-Label Payment Gateway Actually Owes Under PCI DSS
A white-label gateway reseller is not just a merchant with a logo on top. PCI SSC's own glossary already classifies it as a service provider.

- PCI SSC's own glossary defines a service provider as any business entity directly involved in processing, storing, or transmitting cardholder data on behalf of another entity, and names payment gateways and PSPs by name as examples. A white-label gateway reseller fits that definition regardless of whose brand appears on the login screen.
- PCI DSS Requirement 12.8.2 requires a written agreement with every third-party service provider, including an explicit acknowledgment of who is responsible for the security of the account data involved. A white-label relationship without that specific acknowledgment is missing a requirement, not just a formality.
- Requirement 12.8.5 goes further and requires maintaining a documented allocation of responsibilities between the service provider and the entity, for each applicable PCI DSS requirement, not a general statement that compliance is handled.
- PCI SSC owns and maintains the PCI DSS standard itself. The payment brands, not PCI SSC, set and enforce the compliance validation levels and requirements that actually determine what a given white-label operator has to prove and how often.
What a white-label payment gateway actually owes under PCI DSS is usually not written anywhere in the reseller agreement itself. It is written in PCI SSC’s own glossary, which already classifies a white-label gateway operator as a service provider rather than simply a merchant with its own logo on the login screen. That classification is not a technicality. It comes with specific, written, document-level requirements that a reseller agreement focused on revenue share and support terms routinely leaves out entirely, and those requirements exist regardless of whether either party’s legal team ever opened PCI SSC’s own documents while drafting the deal.
What PCI SSC’s own definition actually says
The PCI Security Standards Council’s glossary defines a service provider as a business entity that is not a payment brand, directly involved in the processing, storage, or transmission of cardholder data on behalf of another entity. The definition does not stop at a general description. It names specific examples: payment gateways, payment service providers, and independent sales organizations.
A white-label gateway operator, by definition, is processing or transmitting cardholder data on behalf of the merchants using its platform under a reseller’s own brand. The branding on the login page does not change what the system is actually doing with the data flowing through it. PCI SSC’s glossary also defines a more specific category directly on point here: a multi-tenant service provider, meaning one that offers shared services, including connections to payment gateways and processors, to multiple merchants and other service providers who share the same underlying system resources. A white-label gateway reselling access to one shared platform under multiple reseller brands is close to a textbook description of exactly this category.
The written agreement most white-label deals never actually write
Once an entity is a service provider under PCI DSS, specific requirements attach that do not attach to an ordinary merchant. Requirement 12.8.2 is the one most white-label arrangements get wrong by omission rather than by active violation. It requires maintaining a written agreement with every third-party service provider with which account data is shared, or that could affect the security of the cardholder data environment. That agreement has to include an acknowledgment from the service provider that it is responsible for the security of the account data it possesses, stores, processes, or transmits, or to the extent it could affect the other party’s environment.
A standard white-label reseller agreement, built by a sales or business development team around revenue share percentages, support service levels, and branding rights, frequently never states this acknowledgment at all. The underlying gateway provider usually is handling cardholder data security in practice. The agreement just never says so in the specific way Requirement 12.8.2 actually asks for. PCI DSS’s own applicability notes give some flexibility on exact wording, since the specific language depends on what the parties actually agreed to and which services are involved. Flexibility on wording is not the same as an exemption from having the acknowledgment exist in writing at all.
The responsibility allocation most white-label operators assume rather than document
Requirement 12.8.5 goes a step further than the written agreement itself. It requires maintaining documented information about how responsibility for each applicable PCI DSS requirement is actually allocated between the service provider and the entity using its services. That is a specific, requirement-by-requirement allocation, not a general statement in a master services agreement that the gateway provider “handles PCI compliance.”
This is exactly where a white-label structure creates ambiguity a straight reseller relationship usually does not. In a white-label deal, the reseller’s brand faces the merchant, the reseller’s support team usually fields the merchant’s first call, and the underlying gateway’s infrastructure is invisible to the merchant entirely. Which party is actually responsible for which of PCI DSS’s requirements, network security, access control, encryption, logging, vulnerability management, depends on exactly how the technical integration is built, and that allocation needs to be written down per requirement, not assumed from who answers the phone when something breaks.
PCI SSC’s own guidance on this exact question, addressing a related scenario involving acquirers, states the underlying principle plainly: when a party provides services beyond the narrowest definition of its role, the entities involved should work together to understand which party is responsible for managing the applicable PCI DSS requirements for the services actually provided. That is Requirement 12.8.5 in practical terms. It is also precisely the step a white-label deal structured entirely around commercial terms tends to skip.
Who actually sets the bar, since it is not PCI SSC itself
A separate confusion compounds the first one. PCI SSC owns and maintains the PCI DSS standard, the written requirements already discussed above. It does not set or enforce compliance validation levels, meaning how often an entity has to prove compliance, to whom, and through what kind of assessment. Those levels, and the enforcement behind them, are set separately by each payment brand.
Visa’s own compliance materials state this distinction directly: the Council owns, maintains, and manages the PCI DSS and its supporting documents, while Visa separately manages the data security compliance enforcement and validation initiatives built on top of that standard. A white-label operator asking “what PCI level am I” is asking a question PCI SSC’s own documents do not answer, because the standard itself does not set levels. The answer comes from whichever payment brand’s rules actually govern the transactions flowing through the white-labeled platform, and a reseller supporting multiple underlying gateway relationships can find itself answering to more than one brand’s validation program at once.
A concrete example: the reseller agreement that never mentioned any of this
Picture a vertical SaaS platform that signs a white-label agreement with a payment gateway provider, rebrands the gateway’s dashboard with its own name, and resells it to its own base of several hundred small-business customers. The agreement runs twelve pages, covering revenue share, support response times, uptime commitments, and branding guidelines. It never uses the phrase “service provider” in the PCI DSS sense, never includes the specific account-data-security acknowledgment Requirement 12.8.2 describes, and never documents which party owns which specific PCI DSS requirement.
The underlying gateway provider is, in practice, doing the actual cardholder data handling and almost certainly maintains its own PCI DSS compliance independently. That is not the gap. The gap is that the platform reselling the gateway under its own brand has no written record satisfying 12.8.2’s acknowledgment requirement, and no document satisfying 12.8.5’s responsibility allocation, for its side of the relationship with its own merchant customers, who are themselves relying on the platform’s brand rather than the invisible gateway behind it. If one of those merchants has a data security incident, the platform is the entity its own customer looked to, and the platform’s own paper trail is the one with nothing in it.
What to actually put in a white-label gateway agreement
Start from PCI SSC’s own glossary definition rather than from how the deal is marketed commercially. If the arrangement involves processing, storing, or transmitting cardholder data on behalf of another entity, service provider obligations apply regardless of whose brand sits on top. Write the Requirement 12.8.2 acknowledgment into the agreement explicitly, stating which party is responsible for the security of account data each party actually touches, rather than relying on a general confidentiality or data-protection clause to imply it.
Build the Requirement 12.8.5 responsibility allocation as its own documented artifact, specific enough to answer, for each applicable PCI DSS requirement, whether the gateway provider, the reselling platform, or both carry it. Confirm which payment brand’s validation program actually governs the transaction volume flowing through the white-labeled platform, since that determines the validation cadence and method, not anything PCI SSC’s own standard specifies directly. None of this slows down a white-label launch meaningfully once it is built into the agreement from the start. Drafting the acknowledgment and the responsibility allocation alongside the commercial terms, rather than after them, typically adds days to a negotiation, not months. It is considerably more expensive to reconstruct after a merchant’s data security incident turns an assumed allocation into a disputed one, with lawyers on both sides arguing over what a silent agreement was always supposed to mean.
Getting this structure right before a white-label gateway program launches, rather than during an incident review, is exactly the work behind Midcore’s white-label payment gateway consulting practice. Where the broader question is which underlying processing structure, white-label gateway, payment facilitation, or something else entirely, actually fits a given platform’s model, PayFac-as-a-Service consulting is where that foundational choice gets made with the same compliance questions in view from day one. And because the right white-label partner is rarely obvious from a commercial term sheet alone, payments vendor and partner selection is where a platform tests a prospective gateway partner against exactly these PCI obligations before signing anything.
Frequently Asked Questions
Is a company that white-labels someone else’s payment gateway actually a merchant or a service provider under PCI DSS?
Usually a service provider, at least for that activity. PCI SSC’s glossary defines a service provider as a business entity directly involved in processing, storing, or transmitting cardholder data on behalf of another entity, and specifically lists payment gateways, payment service providers, and independent sales organizations as examples. A company reselling gateway access under its own brand to its own merchant customers is processing cardholder data on behalf of those customers, which is the service provider relationship PCI DSS describes.
What does PCI DSS actually require to be in a contract with a white-label gateway partner?
Requirement 12.8.2 requires a written agreement that includes an acknowledgment from the service provider that it is responsible for the security of the account data it possesses, stores, processes, or transmits, or to the extent it could affect the security of the other party’s cardholder data environment. Requirement 12.8.5 separately requires documenting how responsibility for each applicable PCI DSS requirement is actually allocated between the two parties, not just confirming that an agreement exists.
Who actually decides what PCI compliance level a white-label operator has to meet?
Not PCI SSC. PCI SSC owns and maintains the PCI DSS standard itself, but compliance validation levels and enforcement are set and managed separately by each payment brand. Visa’s own compliance materials state this distinction directly: the Council owns the standard, while Visa manages the data security compliance enforcement and validation initiatives that determine what a given entity actually has to demonstrate.
Sources: PCI Security Standards Council, Glossary: Service Provider, Glossary: Multi-Tenant Service Provider, PCI SSC FAQ: Are acquirers considered service providers for the purpose of PCI DSS Requirements 12.8 and 12.9?, and Visa, PCI DSS Compliance.