Most vendor feature lists look alike, because every gateway claims routing, fraud tools and a branded checkout. The differences sit one level down. How many connectors are live today? Can a rule send one merchant's Visa traffic to a different acquirer than its Mastercard traffic? Who changes the logo on the settlement report?
This checklist covers the white label payment gateway features a PSP, bank or ISO actually uses every week. For each group you get the questions to ask a vendor and what our gateway does, so you can compare like with like.
Top white label payment gateway features at a glance
Here is the short version. Everything in it gets its own section below.
| Area | What to check | In our gateway |
|---|---|---|
| Connectivity | Live connectors and the time to add a new one | 700+ ready connectors; a new one takes about 14 days |
| Routing | Rules by cost, region and card type, plus cascading | Routing and cascading in the same payment attempt |
| Fraud and security | Built-in filters, 3-D Secure, tokens | 150 built-in configurable fraud filters, 3-D Secure, network tokens |
| Checkout | Hosted page, SDKs, local methods | Hosted page on your domain, JS SDK, iOS and Android SDKs |
| Back office | Onboarding, pricing, settlements | Full merchant management system |
| Branding | How far your brand reaches | Payment page and admin URLs, logos, buttons, reports |
| Operations | Uptime, updates, support | 99.95% uptime SLA, monthly updates, Jira service desk |
A vendor that answers every row with a number is easier to hold to its promises than one that answers with adjectives.
Connectivity and payment methods
Connectors decide which acquirers, local methods and wallets your merchants can use from day one. Ask for the live count, then ask what happens when the one you need isn't on the list.
Ours ships with 700+ ready connectors, and you can bring the acquirer contracts you already hold. When a provider is missing, we build its connector from the provider's own documentation in about 14 days, so you can plan a new market around that figure rather than a guess. The platform supports 200+ currencies, crypto among them.
Ask for the full connector list in a demo, filtered by the countries you plan to serve, before you compare totals.
Routing and cascading
Routing is where a gateway earns its fee, because each declined payment that could have gone through elsewhere is lost revenue for your merchant. Check whether rules can use cost, region and card type together, and whether a failed payment retries on a backup route inside the same attempt.
Our routing does both. It also stops sending traffic to a connector that goes down, so one acquirer's outage doesn't spread to every merchant on it. Rules are set per merchant or merchant group in the payment orchestration layer, so a high-volume merchant can run routing of its own.
Fraud prevention and security
Ask which checks run before a payment reaches the acquirer, which run after, and who can change them. A fraud module that only the vendor can configure turns every new rule into a support ticket.
Our anti-fraud combines in-house and external scoring:
- 150 built-in configurable fraud filters, plus whitelists and blacklists
- anti-fraud plans set per merchant, merchant group or MID
- third-party risk scoring providers you connect yourself
- 3-D Secure 2, including an external MPI if you already use one
- tokenization and vaulting, with network tokens for stored cards
The gateway holds PCI DSS Level 1 certification under v4.0.1. On SaaS our certification covers you, and on your own infrastructure you certify your environment while we support the audit.
Checkout and merchant integration
Your merchants judge the gateway by how fast they can plug it in. Count the integration options, because each missing one is a merchant you can't sign.
Ours offers four.
There's a hosted payment page that runs on your domain in 25+ languages, and host-to-host for merchants with their own PCI DSS scope. Ready plugins cover popular CMS platforms, and iOS and Android SDKs cover apps. A lightweight JS SDK embeds card fields into a merchant's own page.
The page shows cards, wallets, BNPL and local methods by the shopper's location and language, and Pay by Link covers sales over email, chat or SMS.
Merchant back office
The back office is the part buyers forget to test, and it's where your team spends its day. It should take a merchant from application to payout without a spreadsheet in between.
Ours covers onboarding with KYB and KYC checks, underwriting and risk scoring, pricing per merchant or group, and settlements with fees, rolling reserves and holdbacks. Reconciliation, chargeback workflows and a self-service merchant dashboard sit in the same system, so none of the merchant management features needs a separate tool.
Branding and deployment
White label should mean that no merchant or shopper ever sees our name. So check every screen. Start with the admin panel and the payment page URL, then open the reports your merchants download and any screen that sends them email.
In ours, your name sits on every one of those screens, down to the buttons and the logo on each downloaded report. It runs as SaaS, inside a cloud account you own on Azure, AWS, Oracle Cloud or Google Cloud (about 30 days to set up), or on your own hardware (about 60 days).
Reliability and support
Ask for the uptime figure in the SLA and how incidents are reported to you. Then ask how often the software changes, since a gateway that ships one release a year falls behind the card schemes.
Ours comes with a 99.95% uptime SLA on SaaS. It runs on microservices with automated monitoring and real-time alerts, across several nodes in different locations with replicated databases and backups. New features arrive in monthly updates, and a dedicated payment team works with you through a Jira service desk.
Questions
Which payment solutions offer white label capabilities?
White label gateway software vendors, some payment orchestration platforms and a few processors with reseller programs. Only the software vendors let you run the whole gateway, back office included, under your own brand and with your own acquirers.
Which features matter most for a new PSP?
Connectors in your target markets, a merchant back office that handles onboarding and settlements, and a hosted checkout your first merchants can set up in a day. Advanced routing pays off once you have two or more acquirers.
Can I switch features on per merchant?
Yes. Each merchant or merchant group carries its own routing rules, anti-fraud plan, pricing and payment methods, so you can start narrow and widen the setup later.
Are all features available on every deployment?
The gateway is the same software on SaaS, in your cloud and on your servers. Dashboard localization is available on self-hosted setups, while the payment page runs in 25+ languages on any deployment.