Why Africa Needs Stablecoin Rails Before It Needs a Digital Currency

Every few months, a new paper arrives from a central bank, a development finance institution, or a technology think tank announcing that Africa's financial inclusion problem will be solved by a central bank digital currency. The CBDC is coming. The CBDC will bank the unbanked. The CBDC will eliminate remittance fees. The CBDC will — the papers imply — do essentially everything that mobile money hasn't quite done, minus the private intermediary.

I want to be careful here. I am not opposed to CBDCs as a concept. Some of the people building them are doing rigorous, important work. But I think the CBDC conversation is drawing attention away from a more immediate, more tractable, and more transformative opportunity: building stablecoin-native payment rails that work for African utilities, cooperatives, and community institutions right now, without waiting for regulatory frameworks that will take years to mature.

This is the problem PesaRails is trying to solve. And it starts with being honest about what the legacy financial system is actually doing to African money.

The 7% Tax

When someone in the UK sends £200 to their family in Nairobi, they pay, on average, about £14 in fees. That is 7%. The money moves through correspondent banks, foreign exchange desks, and mobile money aggregators, each taking a slice. By international remittance standards, Kenya does relatively well — some corridors into West Africa charge 12–15%. The global average for sending money to sub-Saharan Africa is the highest of any region in the world.¹

These fees are not a technical inevitability. They are a rent extracted by the infrastructure layer. The question is not whether the infrastructure can be replaced — it clearly can — but whether the replacement serves the actual institutions that need it.

The 7% tax is not random. It is the cost of a financial infrastructure built for a different world — one in which cross-border value transfer required physical correspondent relationships, manual clearing, and human intermediaries at each step. SWIFT was designed in 1973.² The architecture of international payments reflects the technology and geopolitics of that era. It has been iterated and patched, but its fundamental structure has not changed.

What has changed, in the last several years, is that an alternative exists. Dollar-denominated stablecoins — USDC, USDT — can be sent from a wallet in London to a wallet in Nairobi in under five minutes for a fee that is a fraction of a percent. The transfer is settled on-chain, cryptographically verified, and final. There is no correspondent bank. There is no foreign exchange desk waiting to clip the spread. There is no three-day clearing cycle.

What This Has to Do with Water Utilities

The stablecoin remittance use case gets most of the attention. But I am more interested in a different application — one that is less visible but more structurally important: using stablecoin rails to build payment and financial infrastructure for African community-scale institutions.

Consider a water utility in Kisumu. It collects payments from 80,000 customers, mostly via M-Pesa. It pays its field contractors. It repays a loan from a development finance institution denominated in euros. It reports to a county government and a national regulator. Each of these financial flows runs through a different system — M-Pesa for customer collections, a bank for contractor payments, a SWIFT transfer for the DFI loan repayment, a separate accounting system for regulatory reporting. The friction at each interface costs the utility money, time, and operational visibility.

Now consider a SACCO with 2,000 members across three counties. It collects member contributions in cash and M-Pesa. It disburses loans. It needs to report loan performance to a regulatory body. It would like to access working capital from an impact investor based in Amsterdam. Every one of these flows is slower, more expensive, and less visible than it needs to be — not because the SACCO is doing anything wrong, but because the financial infrastructure it is operating on was not designed for it.

I can tell you exactly how many loans we have outstanding and which members are in arrears. What I cannot tell you is what our liquidity looks like in real time, because the money is in three different places and reconciling them takes my accountant two days a month.

— SACCO treasurer, Western Kenya

Stablecoin rails don't solve all of this. But they solve the settlement layer — and the settlement layer is where a surprising amount of the friction lives. If a water utility could receive payment from a DFI, settle contractor invoices, and hold working capital in a stablecoin-denominated account that earns yield while waiting to be disbursed, the number of intermediaries it is paying — and the number of systems it is reconciling across — drops significantly.

The Infrastructure Problem the CBDC Debate Ignores

Here is what the CBDC debate mostly ignores: the institutions that most need financial infrastructure reform in Africa are not individuals. They are organizations — utilities, cooperatives, constituency offices, hospitals, community development funds. And the financial infrastructure these organizations need is not primarily consumer payments. It is treasury management, cross-border settlement, working capital access, and regulatory reporting.

CBDCs, as currently conceived, are primarily designed for retail payment use cases — replacing cash, enabling person-to-person transfers, maybe bridging to formal banking. That is valuable. But the institutional financial infrastructure problem is different, and it is not being addressed.

The distinction matters: retail payments need ubiquity and simplicity. Institutional finance needs programmability, composability, and auditability. These are different engineering problems.

What institutional finance needs is programmable money — value that can be released automatically when conditions are met, transferred across borders in minutes, audited on-chain, and integrated into the operational software the institution is already using. This is what stablecoin infrastructure can provide, and what CBDCs — with their retail focus and sovereign constraints — are not designed to provide.

What PesaRails Is

PesaRails is our attempt to build the stablecoin-native financial infrastructure layer that African community-scale institutions actually need. Not a consumer payment app. Not another M-Pesa aggregator. A financial operations platform that lets a water utility, SACCO, or cooperative:

Hold and manage value in stablecoin-denominated accounts alongside local currency accounts. Receive international payments from development finance institutions, impact investors, or diaspora donors at near-zero cost. Disburse payments to contractors and staff with on-chain auditability. Access working capital from liquidity providers who can extend capital against on-chain proof of cash flows. Generate regulatory reports that are automatically reconciled against on-chain transaction records.

This is not speculative technology. The pieces exist. What has not been built is the institutional layer — the compliance framework, the account structure, the integration with the existing operational software that African institutions use, the user interfaces that work for a treasurer in Kisumu who has never touched a blockchain wallet.

That translation work is what we are doing. Kill the fees. Keep the money. Build the rails that African institutions actually deserve.