A white label payment platform gives you a complete payment business under your brand, from the gateway that accepts payments and the rules that route them to the back office that runs your merchants. You license it instead of building it, and you decide where it runs.
The word "platform" matters here. A gateway on its own handles one payment at a time. A platform also handles the people and the money around those payments, which is where most of a payment company's work actually sits.
What a white label payment platform covers
Think of it in three layers. Each layer answers a different question your business has to answer every day.
| Layer | The question it answers | What's in it |
|---|---|---|
| Acceptance | How do shoppers pay? | Gateway core, branded checkout, mobile SDKs, 700+ ready connectors |
| Control | Where does each payment go, and is it safe? | Routing and cascading, 150 built-in configurable fraud filters, 3-D Secure, tokenization |
| Operations | How do we run merchants and their money? | Merchant onboarding, pricing, billing and smart invoicing, settlements, reconciliation, reports |
Leave out any layer and you end up buying it somewhere else, then paying to make the pieces talk. Our merchant management system is the operations layer in detail.
Four ways companies use a white label payment platform
The same software serves very different starting points. These are the four we see, and what each one gets out of it.
Launching a payment business from scratch
A new PSP gets the whole stack at once, from the checkout to the settlement report, and spends its first months on licensing and sales instead of engineering. On SaaS, the first live payment can go through within 5 business days on average.
Growing an existing payment business
An established PSP adds connectors and markets without a rebuild, since a missing acquirer takes about 14 days to connect and features like routing or network tokenization are already in the platform.
Upgrading a bank's payment technology
Banks use the platform to modernize merchant acquiring, giving merchants self-onboarding and branded payment pages under the bank's own name, with settlements and anti-fraud tools behind them. Where data has to stay in the country, the platform runs in the bank's own cloud account or data center.
Embedding payments into a software product
A SaaS product or a marketplace can take payments from its users' customers and pay its sellers from inside its own interface. Payments become a revenue line without the company turning into a processor, since we never touch the funds and the acquiring sits with partners.
Who uses white-label payment platforms, and who shouldn't
Most buyers are payment service providers or acquiring banks. ISOs and other resellers make up much of the rest, along with software platforms that have merchants of their own. What they share is a plan to sell or embed payment processing under their own brand.
Some plans need a different kind of software. Accounts, stored balances and card programs belong to banking and issuing platforms, and our page on the white label fintech platform shows where payments fit next to them.
White-label payment platforms for enterprise volumes
High volumes ask different questions of a platform. Will it hold up on the busiest day of the year? Who notices first when an acquirer goes down?
Ours runs on a microservices architecture built for high transaction volumes, with automated monitoring and real-time notifications for critical situations. SaaS comes with a 99.95% uptime SLA. Routing stops sending traffic to a connector that fails, so one acquirer's outage doesn't become yours, and new features arrive in monthly updates instead of in a migration project every few years.
One platform or several tools?
Some companies assemble a payment business from separate products, say a gateway from one vendor and an onboarding tool from another, with settlements in a spreadsheet. It works until the volume grows.
| What you need | With separate tools | With one platform |
|---|---|---|
| A new merchant goes live | Data entered in two or three systems | One onboarding flow ends with a merchant ID |
| A payment is declined | Logs checked in each system | One payment record from checkout to acquirer |
| Month-end settlement | Exports stitched together by hand | Settlements calculated from processed volume |
| A new acquirer | A new integration in each tool | One connector, available everywhere |
The difference shows up in headcount. Every manual handoff between tools is work somebody on your team does by hand, forever.
Questions
Can a SaaS company use a white label payment platform?
Yes. A SaaS company can offer payments inside its product under its own brand, while acquiring partners handle the money.
Is a payment platform different from payment orchestration?
Orchestration is one part of it, the part that routes payments across several acquirers and retries failures. A platform adds the checkout and the merchant back office around that routing.
Can I bring my own acquirers and payment methods?
Yes. You can use the 700+ ready connectors and bring the ones you already work with, and a missing connector takes about 14 days.
Where can the platform run?
As SaaS, in your own AWS, Azure, Google Cloud or Oracle Cloud account, or on your own servers. Cloud setup takes about 30 days and your own servers about 60.