You'll run your business on this software for years, and switching later means moving every merchant and every stored card. So the choice deserves more than a feature comparison on vendor websites, where every row says "yes".
Here's how to choose a white label payment gateway provider in four passes: settle the type of product you need, score the shortlist, test it in a demo you control, then read the contract for the things that only matter when something goes wrong.
First, decide what kind of provider you need
Three kinds of companies sell under the white label label, and they solve different problems. Picking the wrong kind wastes the whole evaluation.
| Kind of provider | What you get | Fits |
|---|---|---|
| White label gateway software | The whole gateway and merchant back office under your brand, with your own acquirers | PSPs, banks, ISOs that want their own product |
| Payment orchestration platform | Routing across several providers, often merchant-facing | Enterprise merchants with many PSPs |
| Processor reseller program | Someone else's processing, sometimes with your logo | Agents who want commissions, not a platform |
If you plan to sign merchants, price them yourself and own the relationship, you need the first kind. The rest of this page assumes that.
How to choose a white label payment gateway provider with a scoring sheet
If you're wondering how to choose a white label gateway when every feature list looks the same, this sheet is the answer. Score each vendor from 1 to 5 on every row, then weight the rows by what matters to your plan. The weights below suit a new PSP. A bank replacing a legacy system would weight deployment much higher.
| Criterion | Suggested weight | The question that separates vendors |
|---|---|---|
| Connectors in your markets | 20% | Which of my target acquirers and local methods are live today? |
| Merchant back office | 20% | Can I onboard, price, settle and reconcile a merchant without a spreadsheet? |
| Deployment options | 10% | Can it run in my own cloud account or servers if my regulator asks? |
| Branding depth | 10% | Does my brand reach URLs, reports and the merchant dashboard? |
| Routing and fraud tools | 15% | Can rules combine cost, region and card type, and who edits them? |
| Support and updates | 15% | Who answers at 3 a.m., and how often does the software change? |
| Exit terms | 10% | How do my card data and merchant records leave if I go? |
Price isn't on the sheet on purpose. Score the product first, then compare quotes between the two or three vendors that score best, since a cheap gateway that can't settle your merchants costs more than its fee.
Run the demo yourself
Vendors' demos show the best path. Ask to drive instead, and bring a script built from your own business. A good vendor will happily follow it.
- Onboard a test merchant from your target market, with its documents and a beneficial owner.
- Give it a pricing plan with a rolling reserve and a weekly settlement schedule.
- Run a card payment, a declined payment that cascades to a second acquirer and a refund.
- Trigger a 3-D Secure challenge and check that the result screen shows your brand.
- Download the merchant's settlement statement and reconcile it against the transactions.
- Change a fraud rule for that merchant only, and see who has to do it.
Each step that the vendor can't show live becomes a question for the contract or a reason to drop it from the shortlist.
Questions to settle in the contract
The contract matters most on the day something breaks or you want to leave. These are the clauses to read before price.
- the uptime figure in the SLA and what you get when it's missed
- support hours, response targets and the channel you raise incidents in
- how card data, tokens and merchant records are returned if you leave, and in what format
- notice periods and how price changes are announced
- who owns custom features built for you
Write down each vendor's answer word for word. Vague answers here tend to stay vague after you sign.
Red flags that rule a vendor out
Some answers end the evaluation, however good the demo looked. Treat these as disqualifying for a payment business.
The first is a vendor that requires its own acquiring and won't connect yours, because your margin then depends on its rates. Another is no PCI DSS Level 1 validation you can check, for example in Visa's Global Registry of Service Providers. A third is a connector count that can't be filtered by your countries. Last comes an export process for card data that nobody can describe in writing.
When you've narrowed the field, a comparison of providers is a quick way to check you haven't missed a strong candidate.
How our gateway answers the sheet
We'd rather you score us than take our word for it, so here are our answers to the rows above. The gateway has 700+ ready connectors, and a missing one takes about 14 days. Its merchant management system covers onboarding to reconciliation.
The gateway runs as SaaS, in a cloud account of yours with one of four major providers, or on hardware you own. Your brand covers URLs, logos, buttons and reports. Routing and cascading work by cost, region and card type, alongside 150 configurable fraud filters.
SaaS comes with a 99.95% uptime SLA, monthly updates and a dedicated payment team. Card data belongs to you and is handed back by PGP or another encrypted method on request.
Questions
Is it worth choosing a white label payment solution instead of building one?
It usually is when payment software isn't the thing you sell. Licensing removes the work of building connectors, a back office and a PCI DSS Level 1 environment before your first merchant, while building makes sense mainly when the software itself is your product.
How many vendors should I shortlist?
Three is enough for a fair comparison. Score more on paper if you like, but run full demos with only the top three, since each one takes real time from your team.
Should I choose the vendor with the most connectors?
Not on the total alone. Count only the connectors in your target markets, then ask how long a missing one takes to build.
What should I ask for in writing before signing?
The SLA uptime figure, support response targets, the data-return process for card data and merchant records, notice periods and the ownership of any custom work.