SWIFT – Tokenized Payments/Deposits – Parsing the Hype

Posted on by

Last week SWIFT announced that 17 of its member banks tested its new blockchain ledger, positioning the network for “tokenized cross border payments” (SWIFT press release). Cue the headlines. My view: this is a me too announcement from an incumbent that is meaningfully behind, and it does not change the trajectory of where tokenized money is actually settling.

The real story is that the big banks are not waiting for SWIFT. They are building their own tokenized deposit networks, joining Canton, integrating with commercial customer platforms like Fireblocks, and quietly redrawing the settlement map. SWIFT gets to be one option among many, useful when a correspondent bank leg or a customer requirement forces its inclusion. It is no longer the default.

Regular readers will recognize this thesis from prior posts. See JPMorgan, Citi and TCH: Tokenized Deposits ON Chain, Augustus Protocol and Emerging Settlement Standards, and the 101 Update on CBDCs, Stablecoins and Tokenized Deposits for the underlying architecture and taxonomy. This post extends the thesis by explaining what the SWIFT announcement actually tells us and what it does not.

What SWIFT Actually Announced

Seventeen banks. A ledger. Tokenized cross border payments. It sounds transformative until you read the fine print. SWIFT’s model is a messaging overlay evolved into a blockchain overlay, still positioned as a network of networks for correspondent banking. The pitch to member banks is essentially, keep using SWIFT, we will make it tokenization compatible.

That framing is exactly the problem. The banks that matter most are not looking for a tokenization compatible SWIFT. They are building tokenized deposit rails that settle without SWIFT.

Three Examples

  • Citigroup and SCB Thailand. Siam Commercial Bank became the first non Citi financial institution to go live on Citi’s integrated 24/7 USD Clearing and Citi Token Services platform. This is a bank to bank tokenized deposit corridor operating on Citi’s platform, not on SWIFT.
  • Lloyds and Canton (January 2026). Lloyds Bank completed the UK’s first public blockchain transaction using tokenized sterling deposits on the Canton Network, instantly purchasing a digital UK government gilt. Settlement was atomic. No SWIFT leg.
  • HSBC and Canton (April 2026). HSBC piloted its Tokenized Deposit Service on Canton, simulating transfer and settlement of tokenized deposits against other digital assets. First time HSBC’s deposit system touched a public blockchain.

Notice the pattern. Two of the three are on Canton. The third is a bank owned platform (Citi Token Services). SWIFT is nowhere in this picture.

Canton Versus SWIFT, in Concrete Terms

Canton is not a public blockchain in the Ethereum sense. It is a privacy preserving institutional DLT with a very different design assumption. As I described in Augustus Protocol, Canton solves what I have called the SWIFT challenge: banks can maintain private ledgers while enabling universal connectivity. The technical mechanics matter, so let me be precise.

Canton settles transactions on the network using a split validation and ordering system.

  1. Local Validation. Only the participant nodes (the specific banks) involved in a trade see and validate the contract details. Everyone else sees nothing.
  2. Blinded Ordering. A Sequencer component timestamps and orders transactions to prevent double spending. The Sequencer only sees encrypted hashes, meaning it orders the transaction without knowing what asset or amount is moving.
  3. Atomic Finality. A Mediator collects the validation votes from participating banks. If all parties approve, the Mediator issues a Commit verdict. At that millisecond, the transaction becomes legally and technically final on the participating nodes’ books simultaneously.

For assets native to Canton, like the tokenized deposits used by HSBC and Lloyds, settlement is entirely on ledger. For hybrid cases, Canton supports off ledger legs. A bank wanting to buy a digital bond on Canton but pay with legacy fiat can lock the digital bond on ledger while an API bridge triggers a traditional payment over an off-ledger network like SWIFT. Once the off-ledger network confirms cash has cleared, Canton automatically releases the digital bond. In that scenario, SWIFT is the plumbing for one leg. It is not the settlement layer, and it is not the network of record.

Contrast this with SWIFT’s traditional architecture. Payments take one to five business days because they rely on multiple intermediaries operating across time zones with batch processing, and manual or semi-automated compliance checks (Higginson and Spanz, McKinsey, “The Stable Door Opens,” July 2025). Global daily money transfer volume through legacy rails is roughly $5 to $7 trillion per day, and the average cost of remitting from a G20 country is 6.47%, reaching 13.18% for South Africa (Jindal et al., Autonomous Research, “Digital Assets, Floodgates Open,” August 21, 2025).

Canton’s participants (and commercial customers) are the ones who would otherwise be paying those rail costs. Citi, Goldman Sachs and UBS are named participants (McKinsey, July 2025). Visa serves as a Super Validator. JPMorgan is the primary anchor via Kinexys migration. That is not an experiment. That is a settlement utility being built by the incumbents SWIFT depends on.

The US Picture, Kinexys and TCH

Within the US (domestic, not cross-border), expect the tokenized deposit ecosystem to organize around two poles.

Kinexys. JPMorgan’s Kinexys platform (formerly JPM Coin and Onyx) processes approximately $3 billion per day in transaction volume, with over $1.5 trillion cumulative volume, sub-second latency, and transaction costs under 1 cent. Its token, JPMD, is a tokenized deposit, meaning funds remain a direct liability on JPMorgan’s balance sheet. Kinexys is now migrating to Canton.

TCH Consortium. The Wall Street Journal reported in early June 2026 that JPMorgan, Citigroup, and The Clearing House are planning a shared tokenized deposit system. This mirrors the TCH governance model, a private, bank owned utility that captures the efficiency of new technology while keeping the customer relationship, the governance, and the economics firmly within the banking system. Interoperability between JPMorgan tokenized deposits and Citi tokenized deposits on a shared ledger is the network effect that turns individual bank infrastructure into a settlement utility.

A Word on Where SWIFT Still Matters

SWIFT still matters when a correspondent bank leg is required, when a commercial customer specifically requests SWIFT, or when a corridor lacks tokenized rail coverage. In hybrid Canton transactions, as noted above, SWIFT can be the off ledger cash leg. That is a real, revenue generating role for years to come.

But there is a difference between being one of the pipes and being THE pipe. SWIFT’s positioning has quietly shifted from the latter to the former. And even where SWIFT does clear a transaction, the bank’s own compliance and controls procedures (regulatory reporting, fraud controls, sanctions screening) still apply. Operational approval on SWIFT’s blockchain does not exempt the transaction from the bank’s own risk framework. It never does.

Tokenized Deposits Versus Stablecoins, Because It Keeps Coming Up

The SWIFT announcement gets conflated with the broader tokenization story, and within that story, tokenized deposits and stablecoins are treated as interchangeable. They are not. As I laid out in the 101 Update, the single most important distinction is that a tokenized deposit never leaves the bank’s balance sheet. A stablecoin does. When Circle mints USDC or PayPal issues PYUSD, the tokens represent a claim on the issuer, not on the customer’s bank. The funds have left the banking system.

For the banks joining Canton, that distinction is everything. They are not adopting blockchain to become stablecoin issuers. They are adopting blockchain to make their existing deposit franchise programmable, faster, and cheaper to settle, while keeping the customer relationship, the balance sheet, and the interest-bearing economics intact. The GENIUS Act, by explicitly prohibiting stablecoin issuers from paying interest to holders, is a powerful shield for the bank deposit franchise (see 101 Update). Tokenized deposits can pay interest. Stablecoins cannot. The competitive asymmetry is deliberate.

The IMF Reads This the Same Way

The IMF’s April 2026 policy note on tokenized finance frames tokenization as a structural reallocation of trust within the financial system, and specifically endorses tokenized commercial bank deposits as the mainstream path (Adrian, IMF Notes No. 26/01, “Tokenized Finance,” April 7, 2026). The IMF’s three scenarios for the future architecture are, a coordinated public anchored scenario built around safe settlement assets, a fragmented scenario with incompatible platforms and trapped liquidity, and a private money dominated scenario where innovation outpaces regulation. The IMF explicitly recommends anchoring settlement in safe money (wholesale CBDC or regulated tokenized deposits) and enforcing global standards of same activity, same risk, same regulatory outcome.

Read that alongside the Canton and Kinexys picture. The banks joining Canton, and the JPMorgan / Citi / TCH consortium, are exactly the institutions the IMF envisions as the trust anchors. SWIFT’s blockchain, by contrast, is a messaging network chasing a settlement future that has already been chosen by others.

Verdict

The SWIFT announcement is a defensive move, not an offensive one. It signals that SWIFT knows it is losing settlement volume to bank owned networks, Canton, and, on the crypto side, to platforms like Fireblocks and to crypto native clearing banks. Seventeen banks doing a test is a headline. Citi, HSBC, Lloyds, and JPMorgan going live on their own tokenized deposit rails is the market.

Where I would push back on my own thesis is the timing. SWIFT still connects thousands of banks that will not migrate quickly. Some of those banks will use SWIFT’s blockchain rather than build or join their own, because they do not have the balance sheet, the technology budget, or the customers to justify Canton membership. For the long tail of correspondent banking, SWIFT’s blockchain is a real product. For the top of the market, where 80% of the volume sits, it is not the destination.

What to Watch

  • Consortium interoperability. Can JPMorgan tokenized deposits settle against Citi tokenized deposits, and against HSBC and Lloyds tokenized deposits on Canton, in a way that turns individual bank infrastructure into a shared utility? That is the metric that matters.
  • Kinexys migration to Canton. Timeline, participant onboarding, and whether Visa’s Super Validator role expands to governance beyond validation.
  • TCH consortium launch details. Governance, participation criteria, and whether smaller US banks are invited or shut out.
  • Central bank integration. Project Agorá and mBridge already point to how tokenized commercial bank deposits and tokenized central bank reserves will share settlement infrastructure. The banks building consortium rails today are positioning themselves as the settlement nodes of tomorrow’s digital monetary system.
  • SWIFT’s next move. A second wave of participant banks and specific corridor pilots would signal SWIFT is serious. A quiet retreat into hybrid off ledger cash legs would signal the market has priced in reality.

Sources and Further Reading

Prior Starpoint blog posts (hyperlinked inline above):

Third party research cited (subscription):

  • Tobias Adrian, IMF Notes No. 26/01, “Tokenized Finance,” April 7, 2026
  • Rahul Jindal et al., Autonomous Research, “Digital Assets: Floodgates Open,” August 21, 2025
  • Matt Higginson and Garry Spanz, McKinsey, “The Stable Door Opens: How Tokenized Cash Enables Next Gen Payments,” July 2025
  • Justin Forsythe et al., UBS, “The Institutionalization of Blockchain and Stablecoins,” November 25, 2025

Primary sources:

Please Login to Comment.