White label payment gateway
White label payment gateway: sell acquiring under your own brand
Boldrails is a licensed payment gateway provider that lets PSPs, ISOs, platforms and resellers sell card and local-method acquiring under their own brand. Your checkout, your merchant dashboard, your customer relationship. Our licences, our acquiring, our settlement. We hold the necessary licences required in the markets we serve, with onboarding in 3 to 14 days.
- Acquiring and settlement under our licences
- Your brand end to end
- Onboarding in 3 to 14 days
- Built for high-risk verticals
Tell us about your merchant book. We come back with terms in 3 to 14 days, depending on your case.
The short version
What is a white label payment gateway?
A white label payment gateway is online payment infrastructure that one company builds and licenses to another, which sells it under its own name. Your customers see your brand at the checkout. The acquiring, the settlement and the regulatory perimeter stay with the provider behind it.
A white-label payment gateway is payment infrastructure that one company builds and licenses to another, which then sells it under its own name. Your customers see your brand at the checkout. The acquiring, the settlement and the regulatory perimeter sit with the provider behind it.
Boldrails is that provider. Stripe's public definition calls the product a ready-made platform that a business rebrands and sells as its own, and that is accurate as far as it goes. It leaves out the part that decides your risk: the money behind the brand belongs to whoever holds the licence. Every section below says which parts of the arrangement are yours and which stay ours.
Benefits and trade-offs
What are the benefits of a white label payment gateway, and what do you give up?
The benefit is speed and margin: you sell payments under your own brand without building acquiring, holding a licence or waiting years for scheme registrations. The trade-off is control. Every advantage on this product comes paired with something you hand to the provider behind it.
Most pages on this search list the upsides and stop. That is the wrong shape for a decision this expensive, because the benefits and the costs are the same facts read from two directions. You go to market in weeks instead of years, and in exchange the perimeter that makes that possible is not yours.
The table is the honest version. Read the right-hand column before the left one, because that is the column that decides whether this product fits your business at all.
| What you get | What it costs you |
|---|---|
| Go to market in weeks rather than years | The build is not yours, so the roadmap is not yours either |
| No licence application, no scheme registration, no acquiring build | The regulatory perimeter sits with the provider, and so does the ultimate say on who gets boarded |
| Your brand on the checkout, the dashboard and the merchant relationship | Not on the acquiring, the settlement or the licences. The split is set out below |
| You set your own merchant pricing and keep the margin | Your margin is the gap between your price and ours, so the wholesale rate decides your business model |
| PCI scope for the gateway sits with the provider | Not all of it. Anything you touch, host or store stays yours to certify |
If the right-hand column is unacceptable, what you actually want is your own licence and your own acquiring, which is a different and much longer project.
By vertical
White label payment gateways for banks, marketplaces, travel and ecommerce
The vertical changes what you need from the product rather than the product itself. Marketplaces need split payments and payouts. Travel needs delayed capture and chargeback tolerance. Banks usually need something else entirely, because they already hold the licence this product exists to supply.
The vertical searches on this product are not really asking for a different gateway. They are asking whether the pieces they depend on are in the box, and whether the provider will board the risk their model carries. Those are two separate questions and vendors tend to answer only the first.
The honest answer for banks is worth stating plainly, because it is the one nobody publishes. A licensed bank already has the perimeter, so white-label acquiring solves a problem it does not have. What a bank normally wants is reach into rails it does not run, which is a coverage question rather than a licensing one.
| Vertical | What it actually needs | Where we fit |
|---|---|---|
| Marketplaces | Split the buyer payment, hold funds under the platform's rule, then pay many sellers on the rails they use | Yes. Collections and mass payouts run on the same engine |
| SaaS platforms | Payments embedded in a product customers already use, with the platform setting merchant pricing | Yes. This is the core buyer for the product |
| Travel | Delayed capture between booking and departure, and a provider that will carry the chargeback profile that comes with it | Case by case. Tell us the booking window and the chargeback history before you plan around it |
| Ecommerce | Local methods at the checkout in each market, because a card-only checkout loses buyers who do not use cards | Yes, on the rails in the coverage table below |
| Banks | Usually reach into rails they do not run, rather than a licence they already hold | Talk to us about coverage rather than about white label. The product below may not be the right one |
If your vertical is not here, the question to send us is not which product you want but which rails your customers pay on and what your chargeback profile looks like.
The question nobody answers
Who holds the licence when you sell payments under your own brand?
Every white-label payment gateway on page one of Google sells you the brand. Not one of them tells you who keeps the licence, and under the Payment Services Regulations 2017 the answer turns on a single test: whether the provider ever enters into possession of the funds.
Those regulations define acquiring as a regulated payment service, where a payment service provider contracts with the payee to accept and process transactions that result in a transfer of funds to them. The same instrument excludes technical service providers that support payments without entering at any time into possession of the funds. The Financial Conduct Authority puts the consequence plainly: where those technical services form part of a payment service, responsibility sits with the payment service provider, not with the firm it outsourced the technology to. That is the UK rule, stated as the UK rule.
We acquire and we settle, so the perimeter is ours. We hold the necessary licences required in the markets we serve.
Four ways to sell payments under your own brand, and who carries what in each:
| Model | Who holds the licence | Who possesses the funds | Who registers with the card schemes | Who carries PCI DSS scope | What you still have to obtain |
|---|---|---|---|---|---|
| Gateway software vendor | You, or your acquirer | Neither. The vendor never touches the funds | You | Shared. You carry the merchant-facing scope | An acquirer, and scheme registration |
| Payment orchestrator | Each connected provider | Not the orchestrator | You | Shared | An acquiring relationship of your own |
| You become a payment facilitator | You | You | You | You, in full | A licence, sponsorship, and underwriting capability |
| Licensed principal under your brand (Boldrails) | We do | We do | We do | We carry the gateway scope | A commercial agreement, and your own branding |
Visa states that third party agents who solicit merchants, deploy acceptance devices or touch Visa cardholder data must be registered in its TPA programme before an acquirer can use them. That is Visa's own published rule and we state it as Visa's alone. We did not obtain a primary source for any other scheme, so we make no scheme-wide claim here. On an arrangement we acquire, that registration sits inside our perimeter rather than yours. Akurateco's FAQ says it does not participate in the financial flow. NMI sells its product as a way to avoid the regulatory complexity of being a financial services provider. Both statements are honest, and both mean the perimeter stays with you.
Sources: Payment Services Regulations 2017, reg 2 · PSRs 2017, Schedule 1 Part 2 · Visa security and compliance
Pricing
What does a white label payment gateway cost?
Price is the most searched question on this product and the hardest one to get answered. Every provider charges on the same four lines: a one-time setup fee, a monthly platform fee, a per-transaction fee, and extras such as extra connectors, compliance work and interface customisation.
What nobody publishes is the level. The two public figures for the same product differ twenty-fold. Stripe's resource page cites USD 500 to 5,000 for setup plus a few hundred dollars a month. A practitioner in the r/fintech thread that ranks second on this search puts white-label and PayFac-as-a-Service setup at USD 10,000 to 100,000 or more. That is one comment, not a rate card, and we report it as such. Five of five vendors we profiled publish no absolute price at all.
We quote per case. There is no public rate card because the price moves with four things: your monthly volume, how many markets you board, how much of the interface you want changed, and whether acquiring sits with us or with you.
Who publishes what, on the record:
| Provider | Fee line | Amount | Scope | Publishes a rate | Extracted |
|---|---|---|---|---|---|
| Stripe | Setup, one-time | USD 500 to 5,000 | Cited on its white-label resource page | Yes | 2026-08-02 |
| Stripe | Monthly infrastructure | A few hundred dollars | Same page | Partly | 2026-08-02 |
| r/fintech practitioner | Setup | USD 10,000 to 100,000 or more | White-label and PayFac-as-a-Service | One comment, not a rate card | 2026-08-02 |
| DECTA | Setup plus monthly maintenance | Not published | White-label gateway | No | 2026-03-09 |
| Spell | Setup plus subscription | Not published | White-label gateway | No | 2026-03-09 |
| Ikajo | Transaction, setup, monthly, customisation | Not published | White-label gateway | No | 2026-03-09 |
| Corefy | Subscription plus transaction | Not published | White-label gateway | No | 2026-03-09 |
| PayXpert | No information given | Not published | White-label gateway | No | 2026-03-09 |
| Nuvei | Gateway, transaction, quarterly PCI, yearly maintenance | Not published | White-label gateway | No | 2026-03-09 |
| Akurateco | Negotiated per client | Not published | White-label gateway | No | 2026-08-02 |
| Cardstream | None shown on the product page | Not published | White-label gateway | No | 2026-08-02 |
| NMI | None shown | Not published | Gateway and embedded payments | No | 2026-08-02 |
| Boldrails | Quote per case | Not published | Acquiring under your brand | No | 2026-08-03 |
Figures marked with a vendor name are that vendor's own published statement or a third-party listicle entry, recorded with its extract date. None is a market standard and none is our price.
Buyer fit
Who a white label payment gateway is for
Five kinds of business buy this. PSPs launching for the first time or moving off a platform they have outgrown. ISOs that want their own brand on the gateway instead of someone else's. SaaS platforms embedding payments into a product their customers already use. Marketplaces that need to collect and pay out under one name. Resellers who sell payments as a line of business.
Google's own answer panel names three of those: SaaS platforms, marketplaces and new PSPs. It leaves out the segment that decides most of these deals. If your merchant book includes high-risk verticals, the gateway is the easy part and acceptance is the hard part.
Payment service providers
Independent sales organisations
SaaS platforms
Marketplaces
Resellers
We are built for high-risk verticals, and we tell you what we can board before you sign anything.
The split
What carries your brand, and what stays ours
Every vendor on this search lists what you can rebrand. Almost none lists what you cannot. Here is both halves.
| Capability | Yours or ours | What that means |
|---|---|---|
| Checkout and hosted payment pages | Yours | Your domain, your colours, your copy |
| Merchant dashboard | Yours | Your logo, your login URL, your emails |
| The merchant relationship | Yours | You sign them, you support them, you keep them |
| Merchant pricing | Yours | You set the rate card. We bill you, you bill your merchants |
| Support portal and merchant comms | Yours | Your help centre, your ticket queue, your sender address |
| Merchant onboarding decisions | Shared | You submit the merchant, we underwrite and board them |
| Acquiring | Ours | We contract with the payee to accept and process the transaction |
| Settlement and reconciliation | Ours | We move the funds and reconcile them |
| Licences and the regulatory perimeter | Ours | We hold the necessary licences required in the markets we serve |
| PCI DSS scope for the gateway | Ours | We carry it. Your own scope depends on how you integrate |
| Scheme registrations | Ours | Including Visa third party agent registration where it applies |
| Fraud prevention and tokenization | Ours | Screening, rules and card tokenization run on our side |
The second column is the honest answer to white label credit card processing. You get the brand, the interface and the commercial relationship. You do not get the licence, and you should not want it: PCI DSS applies to every entity that stores, processes or transmits cardholder data, whatever its size, and carrying that scope yourself is a cost centre, not an asset.
Source: PCI Security Standards Council
Going live
How do you launch a gateway under your own brand?
Five steps take you from the first conversation to your first live merchant.
- 1
Scoping and KYB
You tell us the markets, the methods and the verticals in your book. We run know-your-business checks on you.
- 2
Commercial terms
Volume, fee structure, settlement currency, and who carries which cost.
- 3
Branding and domain
Your logo, colours, checkout domain, dashboard URL and transactional emails.
- 4
Merchant boarding
Your first merchants go through underwriting. You own the relationship throughout.
- 5
Go-live
First live transaction on your brand, on our acquiring.
Onboarding takes 3 to 14 days, depending on your case. Straightforward books in served markets sit at the fast end; complex corridors and compliance review sit at the slow end. One honest caveat, because the market is loose about it. Akurateco quotes 5 to 7 days for a branded dashboard and vendors commonly quote two weeks to launch a PSP platform. A branded dashboard and a live acquiring relationship are not the same milestone. We quote the second one.
Coverage
Which markets, methods and verticals can you resell?
Vendors on this search advertise 100 to 650 payment methods and 150 to 200 currencies. Those are self-reported counts and they do not tell a reseller what they need to know, which is which rails actually settle, in which currency, and at what status today. So we publish status instead of counts.
| Market or rail | Pay-in | Payout |
|---|---|---|
| Uganda, MTN Mobile Money | Yes | Yes |
| Uganda, Airtel Money | Yes | Yes |
| Nigeria, bank transfer and local cards | Yes | Yes |
| Card acquiring, Visa and Mastercard | Yes | Not applicable |
| Kenya, M-Pesa | Yes | Yes |
| Benin, MTN MoMo and Moov Money | Yes | Yes |
| Ghana, Tanzania and Zambia mobile money | Yes | Yes |
| Francophone West Africa, Orange Money, Wave and Moov Money | Yes | Yes |
| Southeast Asia wallets, GCash, PromptPay and TrueMoney | Yes | Yes |
| Multi-currency and crypto-to-fiat settlement | Not applicable | Yes |
Rails are listed per market. Limits, accepted verticals and pricing for your own programme are set at onboarding, because they depend on your business and your volumes rather than on the market.
Every status in this table is specific to that market and rail, and is confirmed for your account at onboarding. Local regulatory conditions and permitted-use rules differ by country, so a status here is not a promise that a given vertical can be boarded in a given market. Our acceptance index is the source for that, and it is where these status labels are maintained.
Not one white-label gateway on page one of this search mentions a single mobile-money rail.
The comparison
How we compare to white label gateway software
Compare models, not brand names. A gateway software vendor sells you the technology and leaves the licence, the acquirer and the scheme registration to you. That is a real option, and it wins on three things: you can deploy on your own infrastructure, you get a wider connector list than any single principal will offer, and the entry cost is lower.
An orchestrator sits above other people's acquiring, which means the perimeter still is not yours. Becoming a payment facilitator yourself gives you full control and full responsibility, including the licence.
We are the fourth option. We acquire, we settle and we disburse under our own licences, and you sell it under yours. If your book is straightforward and you already hold an acquiring relationship, buy software. If it is not, talk to us.
Questions
White label payment gateway FAQ
Written by Claude Igrow, Payments Specialist · Last updated: 2026-08-03