White-label payment gateway software: launch your own payment brand on licensed rails
White-label payment gateway software lets a company run a payment brand under its own name without building the platform: the checkout, the merchant cabinet, the webhooks, the reports and the mail all carry the brand, while the software underneath is licensed from Tranzify and the payment service is provided by a licensed payment partner, or by the company itself when it holds the licence.
What a white-label gateway includes
- A network per brand: domain, certificate, logos, colours, mail sender, legal texts.
- A hosted checkout in 29 languages with cards, 3-D Secure, Apple Pay and Google Pay, Open Banking and local methods, all under the brand.
- Cabinets: the merchant cabinet with payments, refunds, payouts, reports and API keys; the admin panel with merchants, terminals, routing, fees and users.
- Providers from the catalogue, enabled with the brand’s own accounts, with routing and cascading between them.
- Finance: fees per merchant, the brand’s margin, rolling reserve, settlements and reports in one ledger.
- Operations: webhooks with resend, a trace per payment, support tickets, roles and audit.
What the merchant and the payer see
| Touchpoint | What carries the brand |
|---|---|
| Checkout | The brand’s domain, logo, colours and style; the payer never sees another name |
| Merchant cabinet | The brand’s domain and design; the brand’s support team answers the tickets |
| Receipts and notifications from the brand’s address | |
| Webhooks | Sent from the brand’s domain with the brand’s signature secret |
| Documents | Terms, privacy text and reports with the brand’s name |
| API | Keys and documentation under the brand’s domain where the brand wants it |
Who runs white-label brands on Tranzify
- PSPs and acquirers that give partners, ISOs and large merchants their own branded gateway.
- Fintechs and EMIs that launch a payment product on top of their licence.
- Resellers and ISOs that sell payments under their name together with a licensed payment partner.
- Banks that offer a modern gateway to corporate clients without touching the core processing.
Two models
A company with its own licence runs the brand as its own network: it contracts with merchants and providers, settles, and the platform is its software. A company without a licence runs the brand with a licensed payment partner: the partner’s network holds the provider contracts and the settlement, the brand’s network is created inside it with its own merchants, fees and look, and the ledger shows each party its share. The merchant sees one brand in both cases; the solutions page for white-label partners describes who does what.
How a brand is launched
- A network with the brand’s domain and design, created in the back office.
- Providers enabled with the brand’s or the payment partner’s accounts; routing rules written in the flow builder.
- The first merchant on the checkout or the API; webhooks and reports verified.
- Fees, reserves and settlement schedules set; the operations team trained on the cabinets.
The software side of a brand takes days; the time goes into the providers’ onboarding, not into the software.
Where it runs
In the Tranzify cloud, or in the client’s own AWS account with the same images and release process when policy or a bank partner requires it. Journals of every payment are kept five years in both cases, and every brand’s data is isolated from the others down to the database row.
Updated: 2026-11-08