8 min read
Swift’s blockchain ledger could weaken XRP’s broad case for bank payments, but it has not proved that XRP’s cross-currency role is obsolete. The first live transaction showed that banks can connect tokenized deposits without using a public cryptocurrency, yet it did not settle every part of the payment on-chain.

Swift proved that two major banks could coordinate tokenized deposit obligations through its new blockchain-based ledger. HSBC and Standard Chartered completed the first announced live cross-border transaction on the platform in August 2026.
The banks exchanged payment messages through Swift while recording obligations on their own tokenized deposit systems. Swift’s ledger matched and netted those obligations, creating a shared record between systems that had previously operated.
That setup matters because tokenized deposits remain liabilities of the banks that issue them. An HSBC tokenized deposit and a Standard Chartered tokenized deposit are not automatically the same asset, even when both represent conventional money.
Swift served as a secure coordination layer between those separate bank records. According to the official transaction announcement, the banks completed final settlement through existing systems after their obligations were matched and netted.
The distinction limits what can be concluded from the milestone. It was not proof that money traveled from beginning to end entirely on a blockchain or that conventional settlement infrastructure was removed.
Important performance details also remain undisclosed, including the amount, currencies, corridor, fees and total processing time. Without those numbers, readers cannot determine whether the system was cheaper or faster than Ripple Payments or another digital payment route.
Swift’s greatest advantage is its established position inside regulated banking, not simply its blockchain technology. The cooperative connects more than 11,500 institutions across more than 200 countries and territories, giving it relationships that a newer network must build gradually.
Banks already rely on Swift’s standards, messaging tools and compliance processes for international payments. Adding a ledger to that environment may require less operational change than adopting XRP, opening crypto-market accounts and creating new custody arrangements.
The platform also allows banks to issue their own tokenized deposits instead of holding a volatile bridge asset. Those tokens remain linked to commercial bank money and can operate within familiar balance-sheet, liquidity and regulatory frameworks.
Swift said 17 banks across six continents were preparing to pilot live transactions when the ledger became available for initial use. That level of participation gives the project credibility, but it does not mean all Swift members have adopted the platform.
The ledger’s technical design may also ease institutional concerns about public networks. Swift says the system uses an EVM-compatible architecture based on Hyperledger Besu, which is different from conducting payments on Ethereum’s public blockchain.
Swift is not starting with a slow payment network, either. Its 2025 speed data said 75% of payments reached beneficiary banks within 10 minutes, although delays could still occur before recipients received their funds.
Fun fact: SWIFT is essentially a traditional messaging network used by global banks to send payment orders, whereas XRP is a blockchain-based digital asset designed to settle those payments.

No, the first transaction did not show that Swift’s ledger solves every stage of an international payment. It coordinated tokenized obligations, while conventional systems still handled final settlement between the participating banks.
Cross-border payments require more than sending a message or updating a shared record. Banks must manage foreign exchange, available balances, legal finality, sanctions screening, anti-money laundering controls and delivery through each country’s domestic infrastructure.
The announced transaction was cross-border, but that description does not confirm that it involved two currencies. If the transfer used one currency across two locations, it did not test the same foreign exchange problem that XRP supporters emphasize.
Tokenized deposits can also create separate pools of money tied to individual banks and currencies. Swift must make those pools interoperable without weakening the legal claims, compliance controls and convertibility that make bank deposits useful.
The Bank for International Settlements argues that tokenization could combine instructions, settlement and monitoring more efficiently. Its research also shows that effective cross-border systems still need coordination among commercial bank money, central bank money and different legal jurisdictions.
Swift’s test therefore marks progress rather than a finished replacement for correspondent banking. The larger question is whether its ledger can move from one transaction to high-volume, 24-hour service across many banks, currencies and regulatory systems.

XRP could remain useful where banks need to exchange currencies that lack a direct, liquid market. A bridge asset can provide an intermediate trading route without requiring every institution to keep money parked in accounts across numerous countries.
For example, a provider could convert one currency into XRP, transfer the asset over the XRP Ledger and sell it for the destination currency. Ripple says XRPL transactions settle within seconds, limiting the time that a payment provider must hold the asset.
That model becomes less attractive when two currencies already have deep and efficient markets. Banks may prefer direct foreign exchange, tokenized deposits or regulated stablecoins when those choices offer sufficient liquidity without exposure to XRP’s changing price.
Ripple recognizes that different payment corridors may need different assets. Its own payment explanation says XRP can support complex, less-liquid flows, while RLUSD can serve dollar-based payments where XRP is not required.
XRP must also overcome costs that transaction-speed comparisons often ignore. Banks would consider trading spreads, slippage, custody, exchange access, hedging expenses, compliance obligations and the capital treatment applied to crypto-asset exposure.
The bridge argument therefore needs evidence from real payment corridors rather than theoretical speed alone. XRP’s strongest case would be verified savings after every conversion, regulatory and liquidity costs are included, especially in markets where existing routes remain expensive.
Fun fact: XRP remains one of the top 10 cryptos by market capitalization, and it had enormous potential when it launched in 2012.
Swift is better positioned for broad bank adoption because it works through infrastructure and relationships institutions already trust. Its ledger could reduce the need for XRP when tokenized bank deposits can move efficiently between participating institutions and currencies.
That conclusion should not be confused with proof that Swift has already won. Only two banks completed the first announced live transaction, while the wider group of 17 banks was preparing for pilots rather than operating a mature global service.
Ripple is also changing its strategy as regulated digital money gains ground. The company has integrated RLUSD into Ripple Payments and expanded its stablecoin capabilities through Rail, giving customers routes that do not depend on XRP for every transfer.
Those moves create an uncertain outcome for XRP holders. A larger Ripple payment network might create more bridge opportunities, but stablecoin and direct fiat routes could also handle transactions that once formed part of XRP’s expected market.
Public XRPL activity cannot settle the debate by itself. Transaction counts, XRP-denominated payment volume, exchange trading volume and Ripple’s customer payment volume measure different behavior, so claims that XRP usage is rising or falling need a defined metric and period.
Swift’s ledger is a credible challenge to XRP’s broad institutional story, but the decisive test has not happened yet. The winner will be the option that delivers reliable cross-currency liquidity at the lowest total cost while meeting banks’ requirements for regulation, finality, and scale.
This article was made with AI assistance and human editing.
If you liked this, you might also like:
We appreciate you taking the time to share your feedback about this page with us.
Whether it's praise for something good, or ideas to improve something that
isn't quite right, we're excited to hear from you.
Lucky you! This thread is empty,
which means you've got dibs on the first comment.
Go for it!