Mobile money, identity checks and messaging in Africa
Connect your own MTN MoMo, M-Pesa, Smile ID, Dojah, Termii and Africa's Talking accounts, test them in each provider's sandbox and go live when you are ready.
Updated 12/10/2026
On this page
Six connectors help businesses that sell, pay and verify across Africa:
MTN MoMo: ask customers to pay from their MoMo wallet, pay suppliers and staff to MoMo wallets, and check every payment's status.
M-Pesa (Daraja): send M-Pesa payment prompts, receive paybill and till payments, pay customers and businesses, and check balances.
Smile ID: check a person's ID number with the issuing authority, across many African countries.
Dojah: look up Nigerian companies and their tax IDs, screen people and companies for sanctions, and receive the results of Dojah's verification widget.
Termii and Africa's Talking: send SMS, WhatsApp and voice messages, and receive delivery reports and replies.
You bring your own keys for each one. Nexra stores them encrypted and never uses keys of its own. See Connections.
Start in the sandbox
Every provider except Termii has a sandbox where no real money moves and no one is charged. Connect in Test mode first.
| Provider | Where your keys are | Sandbox |
|---|---|---|
| MTN MoMo | momodeveloper.mtn.com: subscribe to Collections (and Disbursements or Remittances if you pay out). Each subscription has a key; each also needs an API user and API key | MTN's sandbox uses EUR. Creating the sandbox API user and key is a one-time step through MTN's provisioning API: ask your developer or MTN partner to run it, using Nexra's API host as the callback host |
| M-Pesa (Daraja) | developer.safaricom.co.ke → My Apps: consumer key and secret | Test short code 174379 and the passkey from the M-Pesa Express test credentials |
| Smile ID | Smile ID portal → Developer → API keys: partner ID and API key | Answers only Smile ID's test identities |
| Dojah | Dojah dashboard → Developers → Configuration: app ID and secret key | Uses Dojah's test data |
| Termii | Termii → Settings → API token: API key and your base URL | No sandbox: send your first test to your own number |
| Africa's Talking | Your app → Settings → API key | The sandbox app sends to Africa's Talking's simulator |
When everything works, take each provider live in its own portal (MTN's go-live, Safaricom's Go Live, live keys for the others) and connect the live keys in Live mode. For MTN MoMo you also choose your country.
Payments stay under your control
Requests that ask a customer to pay (an MTN MoMo payment request or an M-Pesa payment prompt) move money only when the customer approves with their PIN. They need approval in Nexra like any other action that reaches a customer.
Payouts, deposits, refunds, remittances, business payments and reversals move money. They stay off until your workspace switches on money movement for that action, sets its limits and chooses who approves. Nexra sends each provider a reference made from the payment itself, so a repeat is refused rather than paid twice, and an uncertain result is held for you to check instead of being retried.
Know when something happens
Each connector has a trigger that starts a flow when the provider reports an event:
MTN MoMo: a payment or payout succeeded or failed. Paste the trigger's address into the Status callback address of your MTN MoMo steps.
M-Pesa: a customer paid your paybill or till, answered a payment prompt, or a payout, transfer, reversal, status or balance result arrived. Use the trigger's address as the Result address, and run Send customer payments to Nexra once.
Smile ID, Dojah, Termii and Africa's Talking: add the trigger's address in the provider's dashboard, as the setup steps show.
MTN, Safaricom and Africa's Talking do not sign their callbacks, so these triggers use a private address that includes a key Nexra shows you once. Confirm a payment with its status check before you book it.
Match payments to your books
Reconciliation compares mobile money with your ERP or ledger:
MTN MoMo has no list of transactions, so Nexra looks up each MoMo reference your ledger entries carry. Write the reference ID from the payment step to the ledger entry.
M-Pesa customer payments are read from the last 48 hours of your paybill or till history, so run reconciliation at least once a day.
Personal data
ID numbers are masked in every result, and photos, documents, addresses and full phone numbers are never passed to flows. Nexra never puts ID numbers or phone numbers in a request address, so Dojah's NIN, BVN and phone lookups run through Dojah's own verification widget, and the results reach Nexra with the numbers masked.