Mambo 👋
The hard parts of stablecoins did not disappear in Africa. They just moved to a different address.
That is the part nobody is saying loudly enough.
Two Layers
At scale Africa's stablecoin market is going to have two distinct layers of users.
The first layer is the stablecoin-native companies. HoneyCoin. Rafiki by Nala. Swahilies. Due. Companies that understand which stablecoin to use, how to source it, which networks to move it on, and how to manage the full plumbing between stablecoins and fiat. There are also individuals in this layer; people who have been trading on Binance P2P for years and understand crypto directly. But that group is not growing as fast as the second layer.
The second layer is everyone else. The average African individual or business who has never touched crypto. For them stablecoins are just another version of Bitcoin. Crypto is crypto. They do not have time to understand the difference between USDT and USDC. They do not want to.
And that is fine. The first layer exists to serve the second layer; letting them use stablecoins without realizing it. Same Flutterwave dashboard. Same LemFi app. Faster settlements underneath. The second layer never sees the infrastructure. They just see better payments.
But here is what that arrangement actually means.
The second layer did not lose the problems. They passed them up.
The Wrong Address Has No Undo Button
An average African business owner who has spent their career making bank transfers understands one thing; if you send money to the wrong account number, you can call the bank. There is a process. There is recourse. There is someone accountable.
Stablecoins do not work that way. Send to the wrong address and the money is gone. Permanently. No bank to call. No reversal. No support ticket that fixes it.
For Layer Two users this risk is invisible because Layer One absorbs it. A fintech provider handles the wallet addresses. The business owner never sees them.
But the risk does not disappear. It sits with the provider. If a fintech company sends $10 million in prefunding to a wrong address and that $10 million is half their operating capital, the downstream effect hits real users. Payments delay. Settlements fail. Customers feel it without understanding why.
The infrastructure that moves billions still has no reliable solution for human error at scale. That problem has not been solved. It has been centralized.
Liquidity Breaks Before It Scales
Moving $5,000 or $50,000 in stablecoins across Africa is relatively straightforward today.
Moving $15 million in a single transaction is a different problem entirely.
A large importer in Tanzania needs to pay a supplier. The provider needs to source $15 million in USDT or USDC at the best available rate. That means finding someone who needs Tanzanian shillings fast enough to give up $15 million in stablecoins. In most African markets that process is slow, expensive, and unreliable at that ticket size.
At some point it starts to feel exactly like sourcing dollars in Africa the traditional way. Different interface. Same problem.
I spoke with the founder of one of Africa's most valuable fintechs. When I walked him through a stablecoin use case for moving large volumes across borders his response was direct; it works at small scale but moving $30 million in a single stablecoin transaction from Africa to the US is not something he would trust today.
That ceiling affects Layer Two users even when they never see it. Their provider hits the wall. Their payment delays. They blame the app.
The License Does Not Cover the Rails
Most stablecoin fintechs operating in Africa are licensed companies. Their customers trust them because of that license.
A business owner in Lagos or Dar es Salaam does not ask what technology their payment provider uses. They ask if the company is licensed. If yes they trust them.
But here is the problem. Most of those licenses have nothing to do with stablecoins. They are PSP licenses, payment licenses, money transfer licenses issued by regulators who oversee traditional payment flows. When that same licensed company moves your $1 million through stablecoin rails in a country with no stablecoin regulation and something goes wrong, the accountability framework does not exist.
Taking someone to court for misusing $1 million prefunded in stablecoins in a jurisdiction where stablecoin regulation is still being written is extremely difficult. The license the customer trusted does not cover the technology the company actually used.
Layer Two customers do not see this gap. Layer One lives inside it every day.
Not Seeing Something Does Not Make It Safe
There is a specific risk that comes with invisibility.
When Layer Two users do not see stablecoins they also do not see the accountability gaps, the liquidity ceilings, or the wrong address risks that their providers carry. They trust the licensed company above them. That trust is reasonable. It is also built on a foundation that regulation has not yet caught up to.
As long as stablecoin regulation remains unclear across most African markets the problems do not disappear because the end user cannot see them. They accumulate at Layer One. And when Layer One hits a serious problem, a wrong address at scale, a liquidity crisis, a regulatory crackdown; Layer Two feels it without any warning.
The invisibility that makes adoption easy also makes the risks invisible until they are not.
The Reality
The two-layer model is the right model for this stage of adoption. Getting stablecoins into the hands of people who need them without forcing those people to understand crypto is the correct approach.
But the problems that got passed up need to be passed forward. Better address verification tools. Deeper liquidity infrastructure at large ticket sizes. Regulatory frameworks that cover the actual technology being used not just the company holding the license.
The second layer is protected because the first layer is absorbing the hard parts.
That only works as long as the first layer can keep absorbing.
Written from inside Africa with love 🇹🇿💚
Was this useful? Let me know on X or LinkedIn