To choose a payout API for Africa, test it in your own corridors, not on its coverage map. Check which rails it pays to today and who holds the licence. Check how you fund it and how it reports each status. Then force failures in a small live test before you sign.
General information, not legal advice. Check current rules with your regulator and your providers.
What does a payout API for Africa do?
A payout API lets your system send money to recipients in African countries. It pays bank accounts over local rails, such as NIP in Nigeria. It pays mobile money wallets, such as M-Pesa in Kenya. Where it has no local rail, it may send over SWIFT instead.
Providers often publish similar lists of countries and features. Compare them on the rate, the delivery time and how often payouts fail.
Which countries and rails does it pay to today?
A coverage map shows where a provider wants to be. Ask where it paid last month.
- Live, not planned. Ask for the countries, currencies and rails with production payouts today.
- Direct or through a partner. Ask which rails it reaches itself and which go through another firm.
- Both payee types. Some platforms pay individuals and businesses from one integration. Check that the provider covers both, with one contract.
- Measured delivery. Ask for delivery times per rail, from real payouts, over a stated period.
| Payout method | Check before you sign |
|---|---|
| Bank account on a local rail | Whether it checks the account name before paying, cut-off times, the cap per transfer |
| Mobile money wallet | Which operators it reaches, the wallet caps, what happens with a closed wallet |
| SWIFT | Which countries go over SWIFT, deductions by intermediary banks, the payment record. See how to read an MT103. |
On NIP, a name enquiry lets the sending bank check the account holder's name from the account number. Ask whether your provider runs a check like it before each payout.
Who holds the licence in each country?
The firm you sign with may not hold the local licence. It may pay through a licensed bank, operator or money transfer operator. That chain matters to your regulator and to your own risk file. If the chain is new to you, see what a payout partner is.
- Ask which entity holds the licence in each payout country. Get it in writing.
- Check that entity on the regulator's public list.
- Ask whether the provider connects to its bank directly, or through other layers.
- Ask which of its entities will onboard you, for which flow.
Ask one more question in the first call. Will the provider rely on your customer checks? Some platforms expect a provider to accept their KYC without a second review. Some providers cannot, because their banks do not allow it. That single point can stop a deal, so raise it early.
| Market | Who may provide payment services | Rule and date |
|---|---|---|
| Nigeria | Payment firms hold a CBN licence by category, such as switching and processing, mobile money operator, or payment solution services. IMTOs hold a separate CBN licence. Banks may act as agents of licensed IMTOs. | CBN licensing pages and list of licensed IMTOs, read 19 October 2026. Revised IMTO guidelines of 31 January 2024. |
| Kenya | A payment service provider that is not a bank or similar institution needs CBK authorisation first. | National Payment System Regulations 2014, regulation 4(1). A draft National Payment System Bill 2026, published 21 September 2026, would replace this framework. It is still a draft. |
| WAEMU | Banks, microfinance institutions, e-money institutions and approved payment institutions | BCEAO Instruction n°001-01-2024 on payment services, January 2024 |
| Ghana | E-money issuers and payment service providers, licensed by category | Payment Systems and Services Act 2019 (Act 987). Check the current licence categories on the Bank of Ghana site. |
WAEMU is the West African Economic and Monetary Union. Its eight countries use the XOF, including Senegal and Côte d'Ivoire. Its central bank is the BCEAO.
Which local rules change what it can pay?
Local rules decide which rail a payout may use and how much it can carry. Ask each provider how it applies them.
- Nigeria, inbound remittances. The CBN's Foreign Exchange Manual took effect on 1 June 2026. A law-firm summary reports that IMTO transfers go to bank accounts, in naira. Wallets are not a listed channel. Cash is capped at the naira equivalent of USD 200.
- Kenya, mobile money. Since 15 August 2023, the CBK caps the transaction limit at KES 250,000. A wallet can hold up to KES 500,000. A provider may set lower limits.
- WAEMU, e-money. BCEAO Instruction n°020 was signed on 8 October 2026. From 2 November 2026, one identified client can hold up to FCFA 4 million per issuer. Monthly top-ups are capped at FCFA 15 million. Until then, the caps are FCFA 2 million and FCFA 10 million.
- Everywhere, recipient checks. On 18 June 2025, FATF revised Recommendation 16. It asks for tools that verify the recipient's account before payment. Countries are expected to apply it by the end of 2030. FATF consulted on draft guidance in June to August 2026. The final guidance is not yet out.
A payout that takes a wallet over its cap can fail. Ask whether the provider checks caps before it sends. The guide to bulk payouts in Africa has the full limits table.
How do you fund it?
Funding decides how much cash sits idle in each country. Compare three models.
- Prefunding per corridor. You keep a local balance with the provider in each country. Each balance ties up cash.
- One balance, paid by quote. You fund one balance in one currency. You take a quote per payout, and it converts at payment. Quotes expire, so check how long each one lasts.
- Local-currency funding. Some providers let you fund in the local currency you already collect, such as NGN or KES.
Then ask four questions. What are the funding cut-off times, and what happens at weekends? Where is client money held? When a payout fails, how fast does the money come back? Who carries the FX risk between funding and payout?
Compare the all-in cost per payout. Add the rail charge, the FX spread and the cost of cash held in balances.
Which statuses does it report?
Accepted is not paid. Ask which statuses are final, and which can still change.
- Failed is final. A failed payout should carry a reason you can act on.
- Paid is final unless a return follows.
- On hold covers a payout that waits for a document or a compliance question.
- Unknown means no final status yet. Never send a new payout for it until you have one.
- Returned covers money sent back after payment, sometimes days later. It needs its own status.
A request for information from the provider's bank can come back to you. Ask who chases it, and how fast. Ask for one webhook per payout when it reaches a final state. Then fetch the payout to confirm it. Each request needs an idempotency key, so a retry cannot pay twice.
How do you test a provider before you sign?
Give each shortlisted provider two weeks. Read the docs first. Check that every status and error code is listed. In week one, integrate the sandbox. In week two, send small live payouts to your hardest corridors. A sandbox may not show every failure case. Live rails can time out, reject and return.
| Test | How to trigger it | A good result |
|---|---|---|
| Wrong account | Pay a closed or mistyped account | Rejected before money moves, with a clear reason code |
| Name mismatch | Pay with a name that differs from the account holder | Flagged by a name check before payment |
| Wallet over its cap | Pay above the recipient's wallet limit | Rejected with a limit reason, not left pending |
| Slow rail | Ask the provider for a timeout test case | Status stays open, then ends as paid or failed, with no duplicate |
| Duplicate request | Send the same request twice with one idempotency key | One payout and one debit |
| Return after payment | Ask to see how a past return appears in reports | A separate returned status, with the money back in your balance |
| Outage mid-batch | Ask how it reported its last rail outage | Open lines resolve one by one, and you get a notice |
| Reconciliation | Export one day of payouts | Every line matches your ledger by your own reference |
Log the delivery time of every live payout. Keep the results per rail, for every provider on the shortlist.
FAQ
Should I ask who holds the licence in each country?
Yes. The firm you sign with may pay through a licensed bank, operator or money transfer operator. Get the chain in writing and check it on the regulator's list.
What is the difference between a failed and a returned payout?
A failed payout never reached the recipient. A returned payout was paid, then sent back by the recipient's bank or wallet. Track them as two separate statuses.
How long should a payout API test take?
About two weeks. Spend one week in the sandbox. Then send small live payouts to your hardest corridors for a second week.
Is a sandbox enough to test a payout API?
No. A sandbox shows the shape of the API. Only live payouts show real delivery times, failure reasons and returns.
How much can a WAEMU mobile money wallet hold?
FCFA 4 million per identified client per issuer, from 2 November 2026. Until then the cap is FCFA 2 million. Monthly top-ups rise from FCFA 10 million to 15 million.
For PSPs, fintechs and remitters
Nilos pays out in 100+ local currencies, plus SWIFT. You can fund in local currency: NGN, KES, XOF and XAF. Go live in about six weeks: a two-week integration, with compliance in parallel. See payouts and coverage by country and rail, or talk to our team about payouts across Africa.