Mobile money UX patterns that work for Ugandan apps

In Uganda, many products do not collect card details inside the app. They hand the user to a USSD string, a deep link, or a merchant code. That handoff is where trust is won or lost. Good mobile-money UX is less about animation and more about clarity before and after the payment leaves your screen.

Show the amount, fee, and destination before leaving the app

Users should see what they will pay, who receives it, and whether any fee sits on top of the product price. If your fee and the telco fee differ, say so in plain language. Ambiguity here creates support tickets and chargeback-style disputes even when the money moved correctly.

Make the return state boring and reliable

After a USSD or wallet flow, the user may return minutes later—or never tap “Back.” Design for delayed confirmation: a pending state, a way to refresh status, and an SMS or in-app receipt when the provider confirms. Never tell someone a payment succeeded until your backend has an authoritative signal.

• Pending: “We are waiting for confirmation from your mobile money provider.”
• Success: amount, reference, date, and what happens next in the product.
• Failed or expired: one clear retry action and a support contact that already knows the reference.

Respect PIN and privacy norms

Never ask for a mobile-money PIN inside your own form. Never screenshot a PIN entry flow in marketing demos. Keep merchant codes and shortcodes readable offline so a user with patchy data can still complete the payment from memory or a printed instruction.

Design for shared phones and low literacy moments

Many sessions happen on shared devices or with a helper reading the screen. Prefer short sentences, large tap targets, and numbered steps. Icons help, but they do not replace the words “Pay UGX 25,000 to Clinic Care — Merchant 123456.”