Every few months the question returns to a conference panel in Kampala: when does Uganda get its own digital currency? The framing hides the more useful question, because Uganda already has a digital shilling and has had one for over a decade. It sits on a phone, it moves in seconds, it reaches villages no bank branch will ever serve, and it is called mobile money. Any central bank digital currency arriving now is not filling a void. It is entering a market with an incumbent that already works, that people already trust with wages and school fees, and whose agent network is one of the most successful pieces of financial infrastructure the region has ever built. That changes the entire nature of the question. A CBDC in a cash economy has an obvious job. A CBDC in Uganda has to justify itself against a rail that already does most of what it would do, and the honest test is not whether the technology is impressive but whether it beats the incumbent on something specific enough to be worth the build. Nigeria ran this experiment in public with the eNaira and produced the region’s most instructive result, which was not a technical failure at all.
Key Takeaways
- Uganda is not a blank slate. Mobile money already delivers digital value transfer at scale, so a CBDC competes with an incumbent rather than filling a gap, and must be judged on displacement, not novelty.
- The eNaira is the region’s most important CBDC lesson, and the lesson is about demand, not technology: a working system that answers no question users were asking gets built and then ignored.
- The defensible cases for an eShilling are narrow and real: settlement finality between institutions, interoperability that regulation has failed to force, offline payment for areas without reliable network, and programmable disbursement for public transfers.
- The costs are not mainly technical. Bank disintermediation, privacy exposure, and the risk of taxing or restricting a rail people depend on are the live risks, and the mobile money levy already showed how fast users punish a mistake.
- The Displacement Test is the honest filter: name the user, name the incumbent it beats, name the margin it beats it by, and name what breaks if adoption stays low.
What would a CBDC actually do that mobile money does not?
Start with the honest inventory. A Ugandan with an MTN or Airtel wallet can already receive a salary, pay a supplier, settle a school fee, buy airtime, and cash out through an agent within walking distance. What that user cannot easily do is move value between networks without friction, hold value that is a direct claim on the central bank rather than on a telco’s float account, or transact when the network is down. Those three gaps are the entire honest case for an eShilling, and they are worth stating plainly because they are narrower than the rhetoric. Interoperability is real: a decade of policy pressure has improved but not solved cross-network transfer, and a central rail could force what regulation has struggled to. Claim quality is real but subtle: a mobile money balance is a liability of a private company backed by a trust account, and while that has held, it is not the same as central bank money, which matters more in a stress event than in ordinary weeks. Offline capability is the most underrated: a payment instrument that clears without connectivity would serve the parts of the country the current rail serves worst, and it is one of the few features mobile money genuinely cannot replicate. Everything beyond those three tends to be a restatement of what already exists, dressed in newer language, and a central bank that cannot name which of the three it is buying should not be building.
Why did the eNaira disappoint, and what does that teach Kampala?
Because it solved a problem Nigerians did not have, in a market where the alternatives were better. The eNaira launched with genuine ambition and functioning technology, and adoption stayed a rounding error against Nigeria’s population and against the volumes moving through the country’s existing bank transfer system and its very large informal crypto economy. The failure was not the build. It was the demand hypothesis. Users already had instant bank transfers that worked, agents who knew them, and, for those seeking dollar exposure, stablecoin rails that answered a need the eNaira never addressed. A naira in a new wrapper is still a naira, and the people converting savings out of naira were not going to be recruited by a more modern way to hold one. The transferable lesson for Kampala is uncomfortable and worth stating directly: a CBDC is a distribution problem and a demand problem wearing a technology costume. The engineering is the easy part. The hard part is the answer to a merchant in Owino market who asks why she should accept a new instrument when the one in her hand already clears, already has an agent on her street, and already gets accepted by her suppliers. If that answer requires a policy mandate to be persuasive, the product has already lost the argument. Nigeria proved you can ship a working CBDC and still fail, which is exactly the result a smaller economy should study hardest.
What is the Displacement Test?
The named framework of this essay: four questions any central bank, and any founder building payment rails alongside one, should answer before the first line of code. It applies the corridor-audit discipline to domestic infrastructure.
- Name the user, not the use case. Not “financial inclusion” but a specific person: the boda rider paid in cash, the trader settling with a Kampala wholesaler, the mother receiving a government transfer. A use case survives any objection. A person does not, and the discipline of naming one kills most weak proposals immediately.
- Name the incumbent it beats. For that person today, what rail carries the payment? Cash, mobile money, bank transfer, or a savings group. If the answer is cash, the case is strong. If the answer is mobile money, the case must be specific about what breaks in the current experience, because “more modern” is not a benefit anyone feels.
- Name the margin. By how much does it win. Cheaper by a measurable amount, faster by a noticeable one, or capable of something the incumbent cannot do at all, such as clearing offline. A margin too small to notice will not move behaviour, and behaviour is the only thing that matters after launch.
- Name what breaks at low adoption. The eNaira’s real cost was not the build budget. It was the credibility spent, and the policy temptation that follows a quiet launch, which is to mandate acceptance or to disadvantage the alternative. A plan that has no honest answer for the low-adoption case is a plan that will reach for coercion when the numbers arrive.
The test’s usual verdict, applied honestly to Uganda today, is that the retail case is weak and the wholesale and offline cases are the ones worth pursuing. That is not an argument against an eShilling. It is an argument for a much smaller and more specific one than the panels usually imagine.
What should builders, banks, and policymakers do while the question is open?
Build for the gaps, not for the announcement. Founders should notice that the three genuine gaps, interoperability, claim quality, and offline capability, are each a business before they are a central bank project, and that the ventures that matter are the ones solving them on rails that already have users rather than waiting for a rail that may never ship. Offline-capable payment for low-connectivity areas is a product, not a policy. Cross-network settlement tooling is a product. Treasury and reconciliation for merchants juggling three wallets is a product, and it is one whose demand is visible today rather than hypothetical. Banks should treat disintermediation seriously rather than dismissively: if a central bank rail eventually holds retail balances directly, deposit funding changes, and the institutions that will handle it best are those already earning their place through distribution partnerships and lending capability rather than through captive balances. Policymakers carry the heaviest responsibility and the clearest precedent, because the region has already run a natural experiment in how quickly users abandon a digital rail that is treated as a revenue source. The mobile money levy suppressed the very transactions it taxed, and the lesson generalises: infrastructure that people adopt voluntarily can be un-adopted just as voluntarily. Meanwhile the more promising public work is regional and unglamorous, connecting to cross-border payment integration and strengthening digital public infrastructure that any future instrument would need anyway. The eShilling may eventually arrive. It should arrive because it passed the Displacement Test, not because a neighbour launched one first.
FAQ
Does Uganda have a CBDC?
No. Bank of Uganda has approached the question as a subject of study rather than a committed programme, which given the eNaira’s result and Uganda’s mobile money penetration is a defensible position rather than a cautious one.
Would an eShilling replace mobile money?
Almost certainly not, and designs that try tend to fail. The realistic outcome is a wholesale or settlement layer beneath the existing rails, or a narrow retail instrument for cases mobile money serves poorly, such as offline payment.
What is the strongest argument for a Ugandan CBDC?
Offline clearing and forced interoperability. Both are things the current rail genuinely cannot do well, and both serve the users the existing system serves worst.
What is the strongest argument against?
Cost against benefit in a market with a working incumbent, plus the risk that low adoption invites mandates, and the privacy exposure of a payment record held centrally rather than across competing private ledgers.
What should founders build while this is unresolved?
The gaps themselves. Interoperability tooling, offline-capable payment, and merchant reconciliation across multiple wallets are businesses today, and none of them require a central bank to ship anything first.
Related Reading
- Mobile Money Levies: The Tax That Taught a Region
- Stablecoin Remittances: Reality vs Rhetoric
- Agentic Commerce, M-Pesa, and Mobile Money
- EAC Payments Integration and PAPSS
Sources and Evidence
- Bank for International Settlements CBDC research: design typologies, wholesale versus retail, and cross-border work.
- IMF Digital Money and CBDC coverage: adoption analysis including the eNaira experience.
- Central Bank of Nigeria eNaira: the programme’s own documentation of design and rollout.
- Bank of Uganda: monetary policy and payment systems oversight, including the national payment systems framework.