White Label Payment Gateway: What It Is, What It Costs, and Who Actually Needs One

Most content about white label payment gateways is written by companies selling them — here is the honest version, including who should not buy one at all.

A white label payment gateway is someone else’s payment infrastructure sold under your brand. It makes sense if payments are part of what you sell — a platform, a marketplace, a payment service provider. If you are a merchant who simply wants to take card payments, it adds cost, compliance scope and engineering work in exchange for a logo.

What a White Label Payment Gateway Actually Is

A white label gateway is a payment platform built by a provider and licensed to you, presented to your users as your own product. Your brand on the checkout, your brand in the dashboard, someone else’s code and connections underneath.

Typically you get a payment page, a merchant dashboard, connections to acquirers and processors, routing logic, tokenised card storage, and reporting. What you do not get is the acquiring relationship or the risk appetite — those still belong to whoever underwrites the money.

The distinction that matters is between reselling payments and using payments. One is a business model; the other is a purchase.

Where It Sits in the Stack

It helps to separate the three layers, because vendor marketing routinely blurs them.

• Gateway — captures the card at checkout, tokenises it, and transmits the authorisation request. This is the layer you white label.
• Processor and acquirer — route the transaction through the card networks and settle funds. These you connect to, not rebrand.
• Merchant account — where card funds sit before payout, and where underwriting and risk decisions live.

A white label deal gives you the first layer with your name on it. The other two remain third-party relationships with third-party rules.

Who Actually Needs One

There is a real market here, and it is narrower than the search volume suggests.

1. Payment service providers and ISOs whose product is payments. Reselling processing under your own brand is the business, and owning the interface is how you keep margin and customers.
2. SaaS platforms embedding payments for their users — booking systems, marketplaces, invoicing tools. If your customers get paid through you, payments are a feature of your product and should look like it.
3. Marketplaces splitting funds between multiple sellers on a single transaction. Split settlement, seller onboarding and payout logic are genuinely hard, and a white label platform is a reasonable shortcut.
4. Regional operators connecting local acquirers and payment methods that global providers don’t serve well. Owning the routing layer is the whole advantage.

Who Thinks They Need One and Doesn’t

If you are selling your own products and want card payments to work, a white label gateway is the wrong tool. You would be buying infrastructure to resell to yourself.

The costs are real, and the benefit is cosmetic — customers do not abandon checkouts because a provider’s name appears on them. They abandon because the page is slow, the form is long, or the decline handling is a dead end.

What It Actually Costs

Public pricing in this category is scarce, which should tell you something. The structure, though, is consistent, and the line items are what you should be asking about.

• Setup or licence fee — a one-off to stand up your instance and branding.
• Monthly platform fee — the base licence, usually tiered by volume or feature set.
• Per-transaction fee — a fraction of a cent to a few cents, on top of processing.
• Processing costs — interchange, scheme fees and acquirer margin. Separate, and by far the largest number.
• Integration engineering — your developers, connecting your product to their API.
• Compliance — PCI validation, and it is not a rounding error. See below.
• Ongoing operations — someone has to answer when a payment fails at 2am, and that someone now works for you.

The mistake sellers make is comparing the monthly licence fee to a payment provider’s percentage and concluding the white label option is cheaper. It rarely is once integration, compliance and support are counted, and those three are the ones that don’t appear on a pricing page.

The Compliance Part Nobody Leads With

This is the section that changes the decision, and vendor content tends to reduce it to a badge.

When your brand sits on the payment page, your PCI DSS scope depends on your architecture — specifically, whether card data touches anything you control. A hosted page in an iframe keeps your scope narrow. A page you serve, with fields you render, does not, no matter whose backend receives the data.

And the standard moved. PCI DSS requirements 6.4.3 and 11.6.1 became mandatory on 31 March 2025, after three years as best practice. According to the PCI Security Standards Council, they exist because “scripts running in a consumer’s browser are now a significant target for attackers seeking to steal payment card data.”

In practice, they require you to inventory and authorise every script on your payment page, justify why each one is there, verify script integrity, and detect unauthorised changes to the page as delivered to the browser. That is an ongoing operational duty, not a one-time assessment.

The Council removed both requirements from the SAQ A self-assessment form, which some vendors present as an exemption. It isn’t. They remain in the standard, and SAQ A eligibility now requires confirming your site isn’t susceptible to script-based attacks in the first place.

Build, Buy, or Neither

That third option is the one white label vendors don’t mention, because it isn’t a product they sell. The merchant of record model shifts tax registration, dispute handling and compliance to the platform — which for a digital seller is usually a better use of engineering time than owning a payment page.

Cross-border is where the difference gets expensive. Building your own stack means owning VAT registration, currency handling and local payment methods in every market, and the global payment mistakes sellers make there tend to surface a year later, with interest.

What to Ask Before You Sign

Answers to these separate a serious provider from a reseller with a slide deck.

• Who is the acquirer, and can we bring our own? Locked acquiring removes your ability to negotiate rates or add redundancy.
• What is our PCI scope under this architecture — in writing? Including who is responsible for requirements 6.4.3 and 11.6.1.
• Is the payment page hosted by you or served by us? This single answer drives most of your compliance cost.
• What is the actual uptime record, with incident history? Not the SLA number. The history.
• Who handles chargebacks and reserves? Dispute workload and risk exposure both hide here — our chargeback reduction tips cover what that work involves.
• Can we export tokenised card data if we leave? If not, the contract is longer than its stated term.
• What does support look like at 2 am on a Sunday? Your customers will find out before you do.

One more that gets skipped: does the checkout convert? A branded payment page is worth nothing if it performs worse than the generic one it replaced, and that is a measurable thing you can test before committing.

Take Payments Without Building the Layer

Gateway, processing, tax handling, disputes and payouts as one managed system — so payments are something you use rather than something you maintain.