White label mobile money, under your name and your licence

A real white label reaches every place a customer looks: app name and icon, portals, SMS, receipts, USSD text and support details. If one of these still shows the vendor, the customer will notice it the first time something goes wrong.

It should not hide the money. Ask to see the ledger, the trust account report and the audit trail. You answer to the regulator for those numbers, so you need to read them yourself, not ask a vendor for a summary.

No vendor can give you the right to issue e-money. That comes from your central bank, or from a licensed bank or issuer that partners with you. A vendor that blurs this is selling you a risk. Plan the two tracks side by side: the licence and the trust account on one, the software and your brand on the other. Our country guides name the regulator and the route for each market.

You should own the customer records, the tariffs, the agent contracts and the brand. The vendor owns the code and keeps it maintained. Put the exit in writing before you sign: how you get a full export of customers and ledger entries, in what format, and how long the vendor keeps running while you move.

Building gives you full control, and you then pay for a ledger team, mobile engineers on two platforms, a USSD integration and a security programme for as long as the service lives. Expect to spend a long time on features customers take for granted. White label makes sense when your edge is distribution, a licence or a community, and not the wallet code itself. Build when the software itself is what you plan to sell.

First you register for a demo and see the apps under your own name. Then you settle the licence route, the trust account and the first rails. Staff test each flow on test apps with no real money. A pilot with your own staff and a few agents comes next, then a controlled opening. The software is ready on day one; the licence and the partners set the date.