Where do stablecoin rails add the least value?
Where existing rails already work well. Consumer payments are served by cards, wallets and instant payment schemes, and in corridors such as Singapore, London or New York, Swift transfers arrive quickly. Jordan Lawrence sees the clearest case in markets where correspondent banking is slow and costly, and in B2B flows such as settlement, payouts, escrow and treasury.
In detail
Where existing rails already work well. Consumer payments are served by cards, wallets and instant payment schemes, and in corridors such as Singapore, London or New York, Swift transfers arrive quickly. Jordan Lawrence sees the clearest case in markets where correspondent banking is slow and costly, and in B2B flows such as settlement, payouts, escrow and treasury.
Where existing rails already work
Consumer payments in Europe and North America are served by cards, wallets and instant payment schemes that settle in seconds and carry dispute rights. Between major financial centers, Swift transfers with modern tracking arrive the same day. A stablecoin adds nothing there except novelty, and it removes consumer protection.
Where the case is clearest
- Corridors where correspondent banking is slow, expensive or unreliable.
- B2B settlement between companies in different currencies.
- Payouts to contractors, sellers or creators in many countries.
- Escrow and treasury flows that benefit from programmable release.
Jordan Lawrence's view
The value of a stablecoin is the gap it closes. In Singapore, London or New York, the gap is small. In markets with capital controls, weak banking or volatile currencies, it is large, and that is where businesses adopt dollar stablecoins first. For an operator, this suggests a rail to activate per corridor and per use case, not a method to add to every checkout. Reporting it next to cards and transfers shows where it is used and where it is ignored.