The detail worth sitting with: this round is led by SC Ventures, Standard Chartered's venture arm. The same bank that has been exiting correspondent relationships across African markets is now funding the stablecoin rail positioned to fill the gap its own retreat creates. That's not a coincidence, that's a bank hedging its own de-risking decision.
A question rather than a statement, aimed at extending the thread rather than closing it: if the scarce asset really is NGN payout reliability plus balance-holding capacity on the Nigerian side, as his own framing implies, does that mean the next winning remittance model looks less like a standalone app and more like a merchant-acquiring platform that treats consumer remittance as a loss-leading acquisition channel into SME float, rather than a business on its own?
GSMA's own breakdown of that volume is the tell. Cross-border remittances were about $34 billion of $1.68 trillion in mobile money value that year, roughly two percent. The other 98 percent never leaves a single switch. Kenya to Kigali still runs through a USD detour with no shared reconciliation ID, which is a different product than what moved that $1.1 trillion.
The existing Act already has a section built for exactly this. So the bureau side may not need amendment at all, an MOU could work there. The open question sits on GRA's side: whether its own 2009 Act confidentiality provisions block presumptive-tax data from crossing even with an MOU in place.
A pattern worth naming for anyone underwriting African payments infrastructure right now: connectivity gets solved faster than liquidity.
Stablecoin rails connected in months what correspondent banking took decades to wire. But connectivity was never the hard part of correspondent banking.
The hard part was a bank somewhere holding pooled local currency positions deep enough that a $50,000 transfer moved at the same rate as a $500 one. That function got built quietly, funded by balance sheet, and almost nobody thought of it as infrastructure because it never had to announce itself.
Digital rails skipped straight to the messaging layer. Off-ramp liquidity on several African corridors is thin enough that transfers above a few thousand dollars start slipping meaningfully against the quoted rate, the opposite of what "faster, cheaper rails" is supposed to deliver at scale.
The institutions that figure out how to fund and hold pooled local liquidity, not just connect to it, are the ones that end up owning the corridor economics. Everyone else is renting access to somebody else's balance sheet and passing the slippage downstream.
It's worth asking, for anyone deploying capital into this space: are you underwriting a rail, or are you underwriting the liquidity behind it. They are not the same investment.
Kenya's VASP regime goes live in ten weeks. Licensing gets the headlines.
The part that determines whether this works is duller: monthly transaction and fraud reporting from every licensed VASP, seven year record retention, annual cybersecurity audits.
That's a standing supervisory function, not a one time gate. Worth watching whether CBK builds for it before November or after.
Good thread to close on. The monthly reporting requirement is worth flagging too, licensed VASPs have to report transaction data, fraud, and security incidents to CBK and CMA every month, not just pass a one-time audit. That's a standing supervisory workload from day one, not a year-two problem. Whether CBK has built the capacity to actually process that volume monthly is the real open question, and it won't be visible from outside until the reports start landing.
A sharp comparison circulating this week.
Ethiopia just banned crypto exchange, transfer, and custody outright, while Kenya went the other direction with a full VASP licensing regime. Framed as opposite philosophies on the same technology.
It's worth looking at what each central bank was actually defending against.
Ethiopia devalued the birr by roughly 200% under its 2024 macro reforms and is running tight capital controls to manage the fallout. In that position, stablecoins aren't just a savings hedge for citizens.
They're a pressure valve that lets capital exit the currency regime the central bank is actively trying to hold together. A licensing regime only works if the central bank has the reserve capacity and FX market depth to tolerate legal outflows through it.
Ethiopia doesn't have that room right now. Kenya, with a comparatively more stable capital account, does.
So this isn't "one regulator embraced innovation, one feared it." It's two central banks with the same underlying concern. Capital flight via unregulated digital dollars.
Choosing the only tool each currently has the balance-sheet room to use. Ethiopia's ban and Kenya's license are the same policy instinct wearing two different levels of fiscal slack.
Ethiopia just banned crypto exchanges, transfers, and custody outright.
โKenya did the opposite: a full licensing framework covering exchanges, custody, and stablecoins (Nov 2026 deadline).
โSame continent, opposite bets on the same tech.
โSource: BitKE
Fair, the state-instrument point is the sharper correction. On the wiring: credit bureaus sit under Bank of Ghana supervision via a separate 2007 act, GRA sits under its own 2009 act. Different regulators, different statutes, no bridge between them that I can find. That's usually a longer fix than a directive.
@nbelthan@jonah_b A capital-allocation question instead of a market-structure one. What regulatory capital treatment or working-capital line would let a licensed aggregator actually hold meaningful local float, since that's arguably the real constraint, not the absence of rails?
Good add on the shilling number, and it matches what I've seen operators say informally. When your local currency is gaining, holding dollars off-platform looks less urgent, so the political cost of licensing digital dollar rails goes down.
When your currency is in freefall, every dollar sitting outside the banking system is a dollar the central bank can't see or tax, so the ban isn't really about the technology, it's about visibility into capital that's already leaving.
It's worth adding one operational note from that angle. A licensing regime doesn't just need reserve room, it needs enforcement capacity to actually monitor the licensed players once they're live.
Kenya's shilling strength buys policy room, but the harder test over the next year is whether CBK can actually supervise VASPs at the volume this creates, not just whether it can afford to let capital move legally.
Ethiopia's ban is enforceable by simple prohibition.
Kenya's license only works if the supervisory infrastructure behind it actually functions day to day.
Missed a meeting today. Not carelessness, caution.
Someone I was set to meet hadn't confirmed, so I waited before joining. Turns out they were already in the room. I got there three minutes later. They'd already gone.
I keep thinking about how small that gap actually is. Three minutes. Nobody overslept. Nobody forgot. Just two different reads of the same silence, one of us treating it as "still pending," the other as "see you there."
It's a strange thing to sit with, because I spend most of my working hours thinking about exactly this kind of gap, just at a much bigger scale.
Somewhere tonight a settlement desk is watching a clock at 2am, waiting on a trade to clear before a window closes. Nobody there gets the grace of "I wasn't sure, so I waited." The window doesn't care how sure you felt. It closes when it closes, and whatever didn't make it through gets repriced, delayed, or lost.
I know that about corridors. I forgot it about my own calendar this morning.
The real lesson isn't punctuality, I was basically on time. It's about defaults. When something is ambiguous, the safer default is to show up anyway, not wait for certainty that may never come.
Worst case, you sit alone for a few minutes. Best case, you don't lose whoever was already there, waiting on you.
Small mistake today. Cheap lesson, honestly, next to what it costs when the stakes are a settlement leg instead of a calendar invite. Taking it.
Fair. No single body can mandate across 28 sovereign central banks, that framing was too broad. Withdrawn.
But PAPSS's own participant model shows the gap I meant. Central banks join PAPSS at the governance level and 28 have now, including BEAC covering all six CEMAC states in one step this July. Yet commercial banks within those countries connect as opt-in "Participants," direct or indirect, each meeting qualifying requirements separately.
A country can be a PAPSS member for years while most of its banks stay unconnected.
That's a national-level lever, not a supranational one. A joined central bank can push its own supervised banks to connect faster than voluntary uptake would.
Some are already doing this. BEAC's CEMAC accession is explicitly working toward operationalizing across all six states by end of 2026, not leaving it open-ended.
That's closer to what got Pix moving than a marketing push would be.
Seven OSBPs cut border dwell time across Kenya's busiest corridors.
Good. But if the payment settlement on those same shipments still takes 3 days through correspondent banking, you haven't removed the bottleneck. You've relocated it from the border to the bank.
Physical and payment infrastructure need to upgrade on the same clock.
Everyone's reading this as a border-clearance story.
It's actually a KYC story. A regional biometric ID that works at the border is also a portable identity credential.
The exact thing payment providers along this corridor currently rebuild separately, country by country.
Customs solved a problem payments has too.
@pointed88@kinjeketile PAPSS's problem isn't marketing.
Pix won because Brazil's central bank mandated every bank onto the rail on day one. No chicken-and-egg problem.
PAPSS onboarding is still voluntary, country by country. Awareness doesn't fix a supply-side gap. Mandate would
Not a rail war. A layering problem.
Stablecoin OTC solves liquidity timing. PAPSS solves settlement finality. Different jobs, not competing bets.
The real fight: does PAPSS absorb stablecoin liquidity as a rail, or does an issuer formalize settlement first and cut PAPSS out of the loop entirely.
SCRYPT's expanded stablecoin settlement corridors. Now live across Kenya, Tanzania, Rwanda, and Uganda allow local-currency-to-stablecoin flows without mandatory USD conversion.
That detail matters more than the stablecoin framing suggests. Most of the cost and delay in traditional cross-border African payments doesn't come from currency instability itself.
It comes from the mandatory hop through USD as an intermediary currency, which adds a conversion leg, a correspondent relationship, and a pricing markup that has nothing to do with the actual origin and destination currencies.
Removing that mandatory hop is a settlement-architecture change, not a technology story. It's the same principle behind PAPSS's local-currency settlement model.
The win isn't "faster payments," it's eliminating an unnecessary currency conversion that was never economically necessary in the first place, just structurally required by how correspondent banking routes cross-border flows.
Worth tracking corridor volume here against PAPSS's own local-currency settlement growth in the same markets. If both are removing the same USD-hop friction through different mechanisms, the more interesting question over the next year is which approach African treasury teams actually prefer, and why.