Airtel Money API integration for Kenya and Uganda
Airtel Money API integration lets your system request payments from Airtel Money users (a USSD push prompt) and send payouts to them, with results confirmed by callback. You need an Airtel Money merchant account and access to Airtel Africa's developer portal. Mjengo Corporate adds Airtel Money alongside M-Pesa in about 1–3 weeks, depending on approvals.
Updated
| Item | Details |
|---|---|
| Collections | Your system triggers a payment prompt on the customer's Airtel phone; result returned by callback |
| Disbursements | Send money from your merchant wallet to Airtel Money users (refunds, payouts) |
| Account | Airtel Money merchant/business account in the country you operate in |
| Developer access | App and credentials on Airtel Africa's developer portal; test in staging first |
| Go-live | Production credentials after Airtel approves your application |
| Countries | Separate configuration per country (e.g. Kenya, Uganda) |
Why add Airtel Money if you already have M-Pesa?
In Kenya M-Pesa dominates, but a share of your customers will hold Airtel Money and prefer to pay with it. Outside Kenya the picture changes: in Uganda, Airtel Money and MTN Mobile Money are the main wallets. If you sell across East Africa, a single "pay with mobile money" checkout that routes to the right wallet removes a reason for customers to drop off.
How does the Airtel Money payment flow work?
- Your server authenticates with Airtel's API using your client credentials.
- It sends a collection request with the customer's phone number, amount, currency and your reference.
- The customer gets a prompt on their phone and enters their PIN.
- Airtel sends the transaction result to your callback, and you can also query the transaction status.
- Your system records the payment and fulfils the order.
Pitfalls to plan for
- Country-specific settings. Currency, phone number format and credentials differ per country. Keep them in configuration, not code.
- Status checks. Don't rely on the callback alone; poll the transaction status for pending payments after a timeout.
- Reference uniqueness. Every request needs a unique transaction ID, or retries can be rejected or double-counted.
- Unified reporting. Finance teams want one report across M-Pesa, Airtel Money and banks. Design the payments table for multiple providers from day one.
How Mjengo Corporate builds multi-wallet payments
Our own product, Netily, accepts M-Pesa in Kenya and MTN MoMo and Airtel Money in Uganda, so we have built one payment layer that speaks several wallets. For clients we build the same pattern: a provider-agnostic payments module, callbacks with duplicate protection, a reconciliation job and a single dashboard for every payment channel.
Frequently asked questions
Can one checkout accept both M-Pesa and Airtel Money?
Yes. The checkout detects or asks for the customer's network and routes the request to M-Pesa or Airtel Money. Both results land in the same payments table.
How long does Airtel Money integration take?
Building and testing usually takes 1–2 weeks. Go-live depends on Airtel's approval of your merchant and production access, which varies.
Does Mjengo Corporate integrate Airtel Money in Uganda?
Yes. Netily, our own product, already supports Airtel Money and MTN MoMo in Uganda, and we build the same integrations for client systems.
