The model
A white-label partner sells payments under its own name; a licensed payment partner holds the licence and the money; Tranzify runs the software that makes both look like one product: the checkout, the cabinets, the webhooks and the reports all carry the partner’s brand. The partner brings merchants and service; the payment partner brings the licence, the provider contracts and the settlement; the platform makes the division invisible to the merchant.
What the partner gets
- A network with its own domain and certificate, logos, colours and mail, created in the back office in minutes.
- A merchant cabinet and checkout under the brand; an admin panel for the partner’s team with roles and two-factor authentication.
- Fees per merchant and the partner’s margin in the ledger; settlements through the payment partner, with the partner’s share shown per merchant and per period.
- Providers from the catalogue as the payment partner allows, with routing and cascading; the partner’s own acquirer as a terminal where it has one.
- Support tickets and notifications under the brand; reports in XLSX and CSV for the partner and for each merchant.
- Onboarding of merchants with KYB documents, reviewed by the partner or by the payment partner as they agree.
Who does what
| Task | White-label partner | Licensed payment partner | Tranzify |
|---|---|---|---|
| Finding and serving merchants | yes | — | — |
| Merchant agreements, KYC and KYB | by agreement | yes | — |
| Provider contracts and accounts | own acquirer, if any | yes | — |
| Settlement of funds | — | yes | — |
| Checkout, cabinets, routing, ledger, journals | — | — | yes |
| Brand on everything the merchant sees | yes | — | applied by the platform |
What stays with the payment partner
Merchant contracts, KYC and KYB, settlement, compliance, the contracts with providers. Tranzify documents the split in the data processing agreement and the service agreement, and the regulatory status page explains why the platform itself needs no payment licence.
Two ways to run the model
A partner with a payment partner already in place brings it to the platform: the payment partner’s network holds the provider contracts, and the partner’s network is created inside it with its own brand, merchants and fees. A partner without one starts with a payment partner that already runs on the platform, so the merchants, the providers and the settlement are in place from the first day; the partner’s work is sales and service. In both cases the merchant sees one brand, and the ledger shows each party its own numbers.
How a partner starts
A conversation with a payment partner on the platform, or with Tranzify to find one; then a network under the partner’s domain, the first merchants on the checkout, and the fees in the ledger. A second brand or a second country is another network, run by the same team from the same admin panel.