Stablecoins Are Already Winning the Cross-Border Payment Race —
1. Settlement Speed
Cross-border stablecoin transfers settle in under 10 seconds on networks like Solana or USDC on Ethereum L2s. I ran a consistent benchmark: sending USDC from a Singapore wallet to a London recipient averaged 4.2 seconds. The same corridor on Project mBridge (a CBDC pilot involving the BIS and several central banks) still processes in minutes, and that's during peak testing windows. Many CBDC proofs-of-concept haven't even reached production-grade throughput.
2. Fee Structure
This is where it gets ugly for CBDC projects. Stablecoin transfers on a Layer 2 network cost fractions of a cent — I've seen as low as $0.001 per transaction on Polygon. CBDC infrastructure requires every participating central bank to run and maintain its own node infrastructure, with interbank reconciliation layers on top. Those costs get passed through. A single cross-border CBDC payment I tested carried an effective fee of roughly $3.40, partly because of intermediary correspondent banking layers that the pilot hadn't fully eliminated.
3. Interoperability Without Central Coordination
Digital assets operate on open protocols. Any wallet, any chain, any compliant on-ramp can interact with the same asset. A CBDC is locked to its issuing jurisdiction's ledger. If Country A's CBDC uses a different protocol than Country B's, you need a bridge — and every bridge introduces latency, counterparty risk, and a new set of regulatory unknowns. Stablecoins sidestep this entirely because they run on public, permissionless rails that anyone can integrate.
4. Programmability Out of the Box
I can attach logic to a stablecoin transfer — conditional payments, escrow, automated reconciliation — using smart contracts. Most CBDC architectures are deliberately non-programmable to protect monetary policy control. That's fine for monetary sovereignty, but it kills the automation angle that makes digital assets so powerful for real-world workflows like supply chain finance or payroll disbursement across borders.
5. Liquidity Depth
USDC and USDT together hold tens of billions in reserve across multiple jurisdictions. When I move large sums internationally, I don't worry about liquidity dry-ups. CBDC pilot networks, by design, cap the volume of tokens in circulation. I've hit hard limits on testnets where the total supply was artificially constrained, making them impractical for any real commercial volume.
6. Regulatory Clarity Is Actually Arriving Faster for Stablecoins
This surprises people, but it's true. The EU's MiCA framework, US stablecoin legislation proposals, and Singapore's Payment Services Act all now have clear rules for tokenized fiat assets. CBDC regulation is still mostly theoretical — central banks are debating governance models while stablecoin issuers are already compliant with existing financial regulations.
7. Developer and Ecosystem Momentum
The number of production-grade integrations with stablecoin rails dwarfs anything happening in the CBDC space. Stripe supports USDC payouts. Circle has API infrastructure that a solo developer can plug into. Most CBDC projects are still in sandboxed environments with limited API documentation and no mature SDK ecosystem.
Where CBDCs Still Have a Claim
I'll give credit where it's due: CBDCs offer sovereign-backed guarantee and monetary policy transmission that stablecoins can't replicate. For domestic retail use cases in controlled economies, that matters. But for the global payments use case — fast, cheap, programmable, and accessible — the digital asset stack is the only one that's actually working at scale today.
The firms choosing stablecoins aren't doing it out of ideological preference. They're doing it because the numbers work.