Uganda's mobile-money environment includes major merchant-payment routes from MTN MoMo and Airtel Money. A recurring business can use those rails without making the billing model operator-specific.
MTN MoMo merchant payments
MTN Uganda offers merchant payments through its MoMo business wallet and merchant-code flow. Customers can pay a merchant using the merchant code and authorize the transaction with their MoMo PIN.
Airtel Money merchant payments
Airtel Uganda supports Airtel Money payments for goods, services, utilities and other transactions. Merchant and API arrangements should be confirmed for the exact business setup.
One Ugandan invoice, separate wallet attempts
If a customer owes UGX 120,000 for a monthly service, the merchant should create one invoice for that period. An MTN MoMo attempt or Airtel Money attempt should attach to that same invoice rather than creating separate billing records.
What to verify before launch
- Merchant onboarding and legal/KYC requirements.
- Whether the business is integrating directly with the operator or through a PSP.
- Which wallet and collection products are enabled in production.
- How final payment status is delivered and verified.
- How finance accesses transaction and settlement evidence.
Keep recovery provider-independent
The business rule should remain simple: a final unsuccessful attempt can become eligible for recovery; an unresolved attempt should be verified; a successful payment closes the invoice and stops collection.
Use provider-neutral invoice state across MTN and Airtel
A Ugandan merchant may reach MTN MoMo and Airtel Money directly or through a PSP. The billing model should record the wallet and provider route on each attempt while preserving one invoice for the billing period.
Do not assume the payer is the account holder
A family member, employer or colleague may complete a mobile-money payment on someone else's behalf. Use a stable customer or invoice reference where the payment flow allows it, and keep payer information as transaction evidence rather than primary customer identity.
Build an operations view before adding recovery
Support should be able to tell whether the invoice is due, which wallet was attempted, whether the result is final, and which provider reference exists before the system begins automated follow-up.
A useful Uganda launch checklist
-
production merchant account approved for each wallet route;
-
currency and settlement account confirmed;
-
callback or status-check mechanism tested;
-
failed/expired and unresolved outcomes distinguished;
-
reconciliation export mapped to invoice/customer records;
- support team trained on the two wallet routes.
The goal is not to make MTN MoMo and Airtel Money look identical. It is to give the merchant one operational model while keeping provider evidence intact.
Keep local support language practical
Customer messages should name the wallet the customer chose and explain the next action without exposing provider codes. Operations can retain the raw MTN or Airtel result for investigation while the customer sees a stable business message.
Sources
MTN Uganda merchant payments: https://www.mtn.co.ug/momo/merchant/
MTN Uganda Pay with MoMo: https://www.mtn.co.ug/momo/pay-with-momo/
Airtel Uganda Airtel Money: https://www.airtel.co.ug/ug/about/airtel_money_with_you_always
