At nine on a Monday morning, a payments team in London queues three payouts. One goes to a bank account in Lagos. One goes to a mobile money wallet in Kumasi. One goes to an M-Pesa number in Nairobi. On the team's dashboard they look identical: an amount, a currency, a beneficiary. Underneath, they are three separate payout routing problems on three different rails, in three countries with their own regulators, clearing systems and habits.

Payout routing is the work of getting each of those payments onto the right local rail, checked, settled and confirmed, without the sender's product having to know how any of it works. Done well, it is invisible. Done badly, it shows up as stuck transfers, support tickets and recipients who stop trusting the app.

This article explains why payout routing across African markets is a local problem, how the rails differ in Nigeria, Ghana and Kenya, what happens to a payout from the moment you call the API, and what to ask any provider before you trust them with your volume.

Why payout routing in Africa is a local problem

For decades, the default way to move money into Africa was a chain of correspondent banks. Each bank in the chain held an account with the next, and the money hopped from one to another until it reached the recipient's bank. That model has been shrinking. The Bank for International Settlements found that correspondent banking relationships worldwide contracted by about 25% between 2011 and 2020. Fewer relationships means longer, thinner chains, and every extra hop is another place a payout can stall or arrive short.

Meanwhile, the money people actually use at home moves on domestic rails that were built locally and work very well. A naira transfer between Nigerian banks, a cedi payment to a Ghanaian wallet and a shilling payment to M-Pesa each run on infrastructure designed for that market. The fastest route into any of them is to arrive as a local payment, on the local rail, rather than as the last link of a long international chain.

What it means for operators: the question is no longer which correspondent bank you use. It is whether your provider can reach the local rail in each market you serve, under the right licence, and tell you exactly what happened when it did.

Three markets, three sets of rails

Nigeria, Ghana and Kenya are often grouped together as "African payouts". From a routing point of view, they behave very differently.

Nigeria runs on bank rails

Nigeria is a bank transfer market. Instant interbank payments are part of daily life, and the volumes are enormous. The Central Bank of Nigeria reports that NIBSS Instant Payment (NIP) transactions reached 5,626,762,540 in volume and ₦476.89 trillion in value in the first half of 2024 alone. A payout into Nigeria needs a valid account number and bank code, a licensed route into that clearing system, and FX handled in line with CBN rules.

Ghana splits between banks and mobile money

Ghana splits its traffic between bank accounts and mobile money, and mobile money is growing fast. According to the Bank of Ghana's 2025 Systems Oversight Annual Report, as reported by the Ghanaian Times, mobile money transaction value rose 50.8% to GH¢4.54 trillion in 2025, and active customers increased from 23.5 million to 26.7 million. A payout router for Ghana has to decide, per transaction, whether the destination is a bank account or a wallet, and validate the right identifier for each.

Kenya is M-Pesa first

In Kenya, mobile money is the main event. Safaricom's results for the year to March 2026 show M-Pesa one-month active customers in Kenya at 40.99 million and transaction value of KShs 41.68 trillion for the year. For many Kenyan recipients, M-Pesa is the account they use every day, so a payout product that only supports bank transfers misses the channel they rely on most.

The practical point: "pay out to Africa" is really three different integrations, three different data formats and three different compliance conversations, unless your provider absorbs that difference for you.

How Chrisborough approaches payout routing

We built Chrisborough around the idea that a business moving money into Africa should integrate once and inherit the local work, rather than rebuild it market by market.

What happens to a payout, step by step

Chrisborough gives you one REST API across NGN, GHS and KES. Here is what happens between your request and the recipient's balance.

1. You send one request. A single call to the payouts endpoint carries the corridor, the amount, your own reference and the beneficiary details. On our developer page, the example is an NGN payout with an account number and bank code. The corridor field names the market. Everything else runs through the same API.

2. The payout is accepted and given an ID. You get back a payout ID and a status of "processing", so your system has something to track from the first second.

3. Every transaction is screened. Before anything settles, the payout is checked against sanctions lists, watchlists and risk indicators in real time. KYC, KYB, AML and CFT controls sit in the rail itself.

4. The payout moves on the local rail for that corridor. NGN payouts go through licensed local bank rails. GHS payouts go to bank accounts and mobile money. KES payouts go to bank accounts and M-Pesa.

5. Settlement is confirmed with a timestamp. Settlement takes under 5 seconds, and the status changes to "settled" with the time it landed. You can check it with a single call or watch it in the dashboard.

6. Failures surface immediately, with a reason. If a payout cannot complete, it does not sit quietly in "pending". It surfaces straight away with a reason your team can act on.

Your product sees one integration. The routing, the local rails and the compliance checks happen underneath it.

What sits behind the routing

On licensing, Chrisborough is a CBN-Licensed IMTO in Nigeria, operating through licensed local partners across our other markets. We are registered with SCUML, and we handle partner and end-user data in line with the Nigeria Data Protection Act 2023 and the NDPC's GAID 2025. Sensitive payment information is handled to PCI-DSS aligned standards across the payout flow.

On reliability, the two numbers we hold ourselves to are 99.9% platform uptime and a 99% payout success rate. They measure different things. Uptime tells you the API answered. Payout success tells you the money landed.

On pricing, you pay a transparent spread per corridor, with no hidden deductions. The rate you quote is the rate that lands, which matters when your own customers are comparing you on the amount received.

On integration, you get a full sandbox with access in minutes, versioned releases, clear errors, and engineers on call from testing to go-live. Production follows in days. Every corridor we open becomes yours the day it goes live, on the same integration. The API documentation covers the endpoints, schemas and error handling in full.

Questions to ask about payout routing

Every provider says it covers Africa. These questions separate real local reach from a long chain with a nice front end.

• Which local rails do you reach in each market: bank accounts, mobile money, or both?

• Are you licensed in the markets you settle into, and where you are not, which licensed local partners carry the regulatory weight?

• Is one API used for every corridor, or does each market need its own integration and data format?

• Is every transaction screened against sanctions and watchlists before settlement, or after?

• What is your measured payout success rate, separate from your platform uptime?

• How quickly does a failed payout surface, and does it come with a reason?

• Can we test every payout flow and webhook in a sandbox before we touch production?

• What exactly is the spread per corridor, and are there any deductions on the way?

If a provider answers in generalities, assume the routing is less local than the sales deck suggests. We go deeper on why success rate matters more than uptime in why payout reliability decides who survives.

The bottom line

Routing payouts across African markets is a local job. Nigeria runs on instant bank transfers, Ghana on a mix of banks and mobile money, and Kenya on M-Pesa. Each has its own rules and its own way of failing. The providers worth building on are the ones that reach those local rails under the right licences, screen every payment before it settles, and tell you plainly when something goes wrong. Once that is in place, three payouts on a Monday morning really are as simple as they look on the dashboard.

Schedule a discovery call and we will map your NGN, GHS and KES payout flows to the right local rails.

About Chrisborough: a CBN-Licensed International Money Transfer Operator providing payout infrastructure across the NGN, GHS and KES corridors, operating through licensed local partners in Ghana and Kenya. Fintechs, remittance operators and USD senders use Chrisborough to move money into Nigeria, Ghana and Kenya with a 99% payout success rate, local payout reach and a transparent spread per corridor.

Related reading: Why Local Payment Rails Matter for Cross-Border Payments and Settlement in Seconds: What Real-Time Visibility Changes.