A brand, not a reseller page
A white-label partner’s merchants sign in at the partner’s domain, see the partner’s logo in the cabinet and the checkout, receive mail from the partner’s address and get webhooks from the partner’s domain. Tranzify’s name appears nowhere, and the licensing client’s name appears only where the client wants it. A payment business can hand a large partner a complete payment product under the partner’s name without a second platform and without a second operations team.
What a network contains
| Element | Set per network |
|---|---|
| Domains | The admin panel, the merchant cabinet, the checkout and the webhook sender, each on the brand’s own domain with its certificate |
| Look | Logo, favicon, colours, the checkout’s style, the e-mail templates |
| The sender’s name and address for receipts, notifications and the cabinet’s mail | |
| People | Users and roles, two-factor settings, the support team that answers the network’s tickets |
| Merchants | Onboarding, KYB documents, fees, limits, balances, API keys |
| Payments | Terminals, routing rules, limits and restrictions, the journal and the trace |
| Legal texts | The terms and the privacy text the merchant cabinet shows, in the brand’s languages |
Providers and routing can be shared between networks when the client wants to offer its acquirer contracts to a partner, or separate when the partner brings its own.
Isolation by design
Every table carries the network, and every query is bounded by it: a user of one network cannot read a merchant, a payment or a setting of another, whatever the request. Branding, domains and mail are stored per network with a cache that refreshes on change, so a new logo appears on the checkout without a release. Reports, exports and searches are bounded by the network of the user who runs them; the audit log records which network every change belongs to.
How a partner starts
- The client creates a network in the back office: name, domains, logo, colours, mail sender, languages.
- The partner’s domains point at the platform; the platform’s operators connect them, and the checkout answers on the partner’s domain.
- The client grants the partner’s administrator access; the partner creates its users and roles.
- Terminals and routing rules are assigned: the client’s shared contracts, the partner’s own, or both.
- The partner onboards its merchants; every payment, webhook and report carries the partner’s brand.
Running many brands with one team
The client’s operations team works in one admin panel with every network it is allowed to see, switching between brands without logging out; reports, dashboards and the audit log are per network and across networks for the people whose role allows it. Fees are set per network, so a partner’s price list and the client’s margin on it are visible in the ledger. A new country is a new network with its own domain, languages and providers, created in minutes and run by the same team, and a partner that leaves takes its merchants’ data in an export while its network is closed.
For whom
PSPs that run several brands or countries; ISOs and resellers that sell payments under their own name; acquirers that give large partners their own cabinet; fintechs that want a payment product without building the platform. In every case the licensed client stays responsible for its merchants and its funds, and the platform makes sure every brand looks and behaves like a platform of its own.