Starting a payment service provider used to mean building a gateway, and passing its audit, before the first merchant went live. With white label PSP software you license the gateway, the merchant back office and the connections to acquirers, put your brand on all of it and spend that time signing merchants instead.
This page is for PSP founders and the people who run payment operations. It covers what our white-label PSP solution includes, how a launch runs, what we do after go-live and which parts of the business stay with you.
What a white-label PSP solution includes
A PSP needs far more than a way to pass payments to a bank. It has to onboard merchants, price them, watch their risk, settle their money and answer their questions about every transaction. Here's what ships with ours.
| Area | Out of the box |
|---|---|
| Admin panel | One interface for merchants, payments, routing, risk and reports |
| Merchant management | KYB and KYC onboarding, underwriting, pricing and tariffs, chargebacks |
| Routing and cascading | Rules by card country, currency or amount; soft declines retried on another acquirer |
| Connectors | 700+ ready connectors to acquirers and payment methods, plus the ones you bring |
| Checkout | A branded payment page with cards, mobile wallets, BNPL and local methods |
| Risk | 150 built-in configurable fraud filters, 3-D Secure including an external MPI |
| Money flows | Billing and smart invoicing, settlements with reserves, batch payouts |
| Reporting | Transaction reports, merchant statements, reconciliation |
| Access control | Roles, permissions and a full audit trail |
Our merchant management system is the part most PSPs underestimate. It's where your operations team will spend its day, long after the launch is forgotten.
How to launch a white-label PSP
Every launch we run follows the same five steps. The length of each one depends mostly on your acquirers and your deployment choice, not on the software.
- Scope it. We go through your markets, merchant types, acquirers and payment methods on a demo and agree what goes live first.
- Brand it. Your domain, logo and colors go on the payment page, the admin panel, the merchant dashboards and the reports.
- Connect your acquirers. Most come from the 700+ ready connectors; a missing one takes about 14 days to build.
- Configure the business. You set up merchant onboarding rules, fee plans, routing rules and fraud filters, and invite your first merchants.
- Go live. On SaaS, processing starts in 5 business days on average.
Licensing runs in parallel and stays on your side. Our guide on how to become a PSP covers that part, from choosing a license type to opening acquiring relationships.
Your brand on every screen
Merchants judge a PSP by what they see, so the branding goes all the way down. Payment page and admin panel URLs, logos, buttons and reports all carry your identity. Nobody sees ours.
That matters most when you sell to merchants who compare you with a global processor. A checkout on your domain and a dashboard with your name look like a product you built, because, to the merchant, it is.
SaaS, your cloud or your own servers
Most new PSPs start on SaaS. Some licensed institutions have to keep payment data in their own country or their own data center, and for them the same software runs on their infrastructure.
| Option | Time to start | Who runs the infrastructure | PCI DSS |
|---|---|---|---|
| SaaS | 5 business days on average | We do, with a 99.95% uptime SLA | Covered by our Level 1 certification |
| Your cloud account (AWS, Azure, Google Cloud, Oracle) | About 30 days | Your team, with our support | Your own certification, which we support |
| Your own servers | About 60 days | Your team, with our support | Your own certification, which we support |
The choice changes who runs the servers and who certifies them. It doesn't change what your merchants see.
The team behind the white label PSP software
Software alone doesn't run a PSP. You get a dedicated payment team: an account manager who knows your setup, help with implementation and ongoing support for your payment operations through a Jira service desk. The platform itself gets new features in monthly updates.
PSPs in Qatar and Saudi Arabia have launched and scaled on that combination, inside two of the region's regulated markets.
What stays your job
A white label gateway for PSP businesses takes the software off your hands, not the business. Four things stay with you whatever vendor you choose:
- The acquiring contracts, and the relationship with each acquirer
- Your license, or the partner whose license you operate under
- Decisions on which merchants to accept, made with the risk rules you configure
- Support for your merchants, who will call you, not us
Settlements run from your acquirers to you and your merchants, because we never sit in the money's path. The funds stay under contracts you control.
Questions
Can I move my existing merchants to the platform?
Yes. Existing merchant accounts can be imported into the merchant management system, so you can move a portfolio over without onboarding every merchant again.
Do I need my own acquirer?
You need at least one acquiring relationship to process card payments. If you don't have one yet, we'll introduce you to an acquiring partner that works in your markets.
How do my merchants connect?
Through a hosted checkout, a host-to-host API, CMS plugins or iOS and Android SDKs. Each merchant picks the option that suits its site or app.
Is white label PSP software only for new PSPs?
No. Existing PSPs use a white label payment gateway for PSP work too, to replace an aging gateway, add connectors and markets, or take on features like routing and network tokenization without building them.