Tokenised cross-border payments are international transfers that settle by moving tokenised money, such as deposit tokens or stablecoins, across ledgers rather than by sending payment messages through a chain of correspondent banks. The phrase entered mainstream banking coverage after Swift launched its blockchain shared ledger in pilot on July 9 2026 with 17 banks. This article defines the term precisely, before the definition gets blurred by competing marketing.
​

The core idea is that value is represented as a token whose ownership can transfer directly between parties, so a payment becomes a settlement event on a ledger both sides trust, not a set of instructions that intermediary banks reconcile after the fact. That distinction is what separates a tokenised payment from a faster version of the current system.
​

A tokenised cross-border payment means an international payment settled by transferring a token that represents money, on a distributed ledger, rather than by exchanging messages while value moves separately through correspondent accounts. The token can be a bank deposit token or a stablecoin, and the settlement is recorded once on a shared ledger instead of reconciled across several banks.
​

The word "tokenised" is doing specific work. It means the unit of value is a programmable token whose transfer is the settlement, not a database entry that a later reconciliation confirms. That is why the model can compress the multi-hop correspondent chain. For how this compares directly with the message-based system, see Cross-Border Stablecoin Payments vs SWIFT.
​

They work by having a sender's tokenised money transfer to a receiver on a ledger both parties can settle against, with a smart contract enforcing the transfer conditions and a messaging standard such as ISO 20022 carrying the structured payment data. When the token moves with finality, the payment is complete; no separate reconciliation step is required.
​

Under the correspondent model, a payment passes through several banks that each debit and credit accounts they hold for one another, adding fees and delay at every hop. A tokenised transfer collapses that into a single settlement event on a shared record. The ISO 20022 messaging standard supplies the common data model so compliance, sanctions screening, and reconciliation systems can read the payment the same way they read existing traffic.
​

Two token types dominate: bank deposit tokens and stablecoins. A deposit token is a claim on money at the issuing bank and stays inside the regulated banking system. A stablecoin is issued by a non-bank against reserves and settles on public chains. Both can carry cross-border value, but their issuer, backing, and supervision differ.
​

The choice matters for credit risk and regulation. Deposit tokens keep exposure on the issuing bank's balance sheet; stablecoins shift it to the issuer and its reserves. Swift's shared-ledger pilot uses tokenised deposits, while the broader market also settles in stablecoins such as USDC and USDT, which together anchor a stablecoin market of about 310 billion dollars as of July 2026 (DeFiLlama). For the deposit side, read What Is a Tokenized Deposit? and Tokenized Deposits vs Stablecoins.

The term surged because Swift, the messaging cooperative used by more than 11,000 institutions, launched a blockchain shared ledger in pilot on July 9 2026 with 17 banks settling tokenised cross-border payments. When the incumbent network adopts the phrase, it moves from crypto vocabulary into mainstream banking language almost overnight.
​

Before the pilot, tokenised cross-border payments mostly described stablecoin corridors run by fintechs. Swift's involvement reframed the term as something large banks do with deposit tokens on permissioned infrastructure. The pilot is built by Consensys on Hyperledger Besu with Chainlink CCIP as the interop layer; the full participant list is in The 17 Banks Piloting Swift's Blockchain Ledger, and the mechanics are in What Is Swift's Blockchain Shared Ledger?.
​

Not in the Swift pilot. Final settlement there still relies on Swift's traditional rails and existing correspondent relationships, so the token movement coordinates the payment while legal finality runs through established infrastructure. Public stablecoin transfers can achieve onchain finality today, but the bank-grade, cross-corridor version is still being tested.
​

This is the honest state of the term in 2026. Tokenised cross-border payments are real and live in pilot, yet "tokenised" does not automatically mean "settled onchain with finality end to end." Reading the phrase precisely, it describes how the payment is represented and coordinated, and the finality question is exactly what pilots like Swift's are built to resolve. Swift's program detail is on SWIFT, and the cross-chain interop layer at Chainlink.
​

Eco is cross-chain settlement infrastructure for stablecoins, which is the layer that moves tokenised value between ledgers rather than any single chain. Because tokenised cross-border payments will settle in many token types across many networks, the connective routing layer is where the practical value sits, and that is where Eco operates.
​

Swift's pilot uses an interoperability protocol to connect roughly 70 networks, which is the same recognition Eco is built on: the future of tokenised payments is multi-ledger. Eco Routes selects between rails such as CCTP, Hyperlane, and LayerZero on cost, speed, and finality, so stablecoin value can settle across chains the way deposit tokens settle across the Swift ledger.
​

Related reading

Methodology and sources: Term definition grounded in Swift's July 9 2026 shared-ledger pilot announcement (swift.com). Stablecoin market size from DeFiLlama, July 2026. Technical layer (Hyperledger Besu, Consensys, Chainlink CCIP) from primary documentation. Messaging standard from iso20022.org. Last updated July 2026.
​