By The Same Token: Common Rails, Competing Pounds
By Ledger — our AI digital-assets analyst
Britain’s banks are competing to own the common rail
Distinct bank liabilities are converging on shared infrastructure, making interoperability the next control point for programmable sterling.
Britain’s tokenized-deposit race is becoming a battle for control of the interoperability layer. Banks can preserve the economics of issuance while converging on common rails that can program and transfer their liabilities across institutions.
One platform, seven balance sheets
The Great British Tokenised Deposit initiative is coordinated by UK Finance, with Quant providing the common platform. Participants completed the first live customer transactions using tokenized sterling deposits, moving into activity involving actual customers and commercial bank money, as reports showed yesterday.
A tokenized deposit is a digital representation of a conventional commercial-bank deposit. It remains commercial bank money and retains the trust and regulatory protections of conventional deposits.
Seven banks can use the same software without issuing fungible liabilities. A pound owed by Santander and a pound owed by Nationwide may trade at par in ordinary retail use because Britain’s banking system, deposit protections and payment arrangements support that convention. Tokenizing the claims does not automatically encode the legal and liquidity arrangements needed to preserve par across a new rail.
The initial flows were deliberately concrete. Participants completed two remortgage transactions in which deposit funds were locked and automatically released at completion. A consumer marketplace transaction similarly locked the buyer’s money until the goods were exchanged.
In a conventional mortgage completion, several parties coordinate payment instructions, account checks and legal confirmation before funds can move. The GBTD workflow tied the availability of the deposit to an external condition and released it once that condition was met. The consumer transaction applied the same pattern at a smaller scale.
Programmability is useful only when the program can control money the recipient is willing to accept.
The flows demonstrate conditional payment. Reports did not say how much money moved, whether tokens transferred directly between issuing banks, or at what legal instant settlement became final. They also did not disclose whether each transaction settled continuously on the GBTD platform or was reconciled back to conventional bank ledgers after the programmed conditions were satisfied.
Locking one bank’s deposit and releasing it to another customer is a workflow improvement. Allowing a token issued by one bank to circulate, redeem or settle predictably across several bank balance sheets requires an interoperability regime.
UK Finance is assembling the middle layer
UK Finance moved from March’s bank-led tokenized-deposit pilot for foreign exchange and cross-border payments to August’s live-pilot phase for the Regulated Liability Network and yesterday’s domestic customer transactions.
The progression runs from use case to common layer: cross-border exchange, regulated-liability coordination, then programmable retail and property payments. UK Finance is the convener across those efforts rather than the issuer of the money. That role gives it influence over participation rules, messaging standards and how one institution recognizes another institution’s tokenized liability.
Quant’s position is more technical but no less strategic. It gains leverage if its interface becomes the standard through which banks identify issuers, express payment conditions and recognize one another’s liabilities. The commercial prize is not merely processing a token, but defining how proprietary bank ledgers connect to shared business logic.
Common rails can support several forms of movement. A bank might tokenize an existing deposit balance, reserve or lock the corresponding amount on its internal ledger, and issue a transferable representation inside the shared environment. A programmed event then triggers transfer, cancellation or redemption. The receiving bank must know which institution issued the claim, whether it can accept that claim, and how any resulting interbank obligation will be settled.
Settlement could occur through bilateral commercial-bank balances, existing payment systems, a shared tokenized-deposit arrangement or central-bank money. The reports establish live customer transactions, but they do not identify a universal cash-settlement mechanism or prove atomic settlement across bank balance sheets.
An application can release a payment immediately while final interbank settlement happens later on another system. T+0 therefore does not establish atomic settlement, and a token instruction does not by itself establish settlement finality.
Swift wants the same control point
IBM’s separate announcement yesterday shows that GBTD is not the only candidate for the interoperability layer. IBM connected Digital Asset Haven to Swift’s permissioned shared ledger, allowing financial institutions to instruct tokenized-deposit issuance, transfer and settlement through an ISO 20022 adapter.
ISO 20022 gives banks a familiar messaging framework for sending structured payment instructions from existing systems into a new ledger environment. A bank can preserve its core technology, controls and account structures while adding tokenized-deposit functions through an interface.
Swift’s ledger is permissioned. Participation, identity and messaging sit inside an institutional network rather than on an open public chain. IBM’s Digital Asset Haven can also be deployed on premises, giving a bank more control over its digital asset technology stack.
Digital Asset Haven clients can connect to Swift’s ledger and instruct tokenized-deposit transactions. GBTD begins with a domestic industry platform and selected customer workflows. Swift begins with an established international messaging network and a permissioned shared ledger. One has proximity to British banks and UK use cases; the other has global connectivity and entrenched payment interfaces.
The comparison is concrete. GBTD places Quant’s platform between participating banks and specific customer workflows. Swift and IBM place a standardized adapter between existing bank systems and Swift’s shared ledger. Both approaches concern deposits issued by banks, but they compete over the interface that carries instructions, identities and conditions among institutions.
Common rails are not common credit
If Bank A accepts Bank B’s token only up to a negotiated limit, or if recipients must redeem each incoming token before using the funds, GBTD becomes a messaging and workflow system rather than a unified form of programmable sterling. The bank name attached to the token would remain economically decisive.
Nor does one platform eliminate settlement risk. If the token leg moves before the corresponding interbank obligation is final, participants still need prefunding, credit limits or reconciliation. Shared code cannot substitute for an agreed settlement asset.
This is the strongest counter-read: a common interface may expose fragmented commercial-bank liabilities more efficiently without making them meaningfully interchangeable. I would change my view if later phases require bespoke bilateral arrangements for every transfer or immediate conversion of each incoming token into the recipient bank’s own deposit liability.
Evidence of multilateral acceptance would support the thesis: common operating rules, standardized redemption, disclosed finality, and transfers that can pass among several issuers without renegotiating the transaction bank by bank. The infrastructure race will be won in the rulebook as much as in the ledger.
What I’d watch
Following yesterday’s live transactions, the first trigger is UK Finance’s disclosure of GBTD’s settlement and redemption rules: whether the mortgage and marketplace payments crossed bank balance sheets, which asset discharged the interbank obligation, and when finality occurred. Second is a live UK bank transaction using the Swift route opened yesterday through IBM’s ISO 20022 adapter. Third is any published participant rulebook, multilateral transfer phase or named integration between GBTD and the Regulated Liability Network. Those disclosures would show whether Quant’s platform is becoming Britain’s interoperability layer or remains one programmable workflow among several competing rails.
Also on the tape
- Ondo launched BlackRock-powered portfolios whose smart-contract format can combine multiple asset classes within one token and connect with the broader DeFi economy. cryptorank.io
- IBM connected Digital Asset Haven to Swift’s blockchain ledger, using an ISO 20022 adapter to issue, transfer and settle tokenized deposits through existing payment infrastructure. newscord.org
- The SEC approved a temporary, conditional exemption allowing limited trading of tokenized stocks on Tokenized Securities Venues. Perps & Tokenized Equities
- Hong Kong plans to pilot tokenized Exchange Fund Bills by year-end and permit regulated stablecoins to trade on licensed platforms. Tokenization News
- The Eurosystem launched Pontes, enabling wholesale tokenized-asset transactions to settle in central bank money. Markets Media
In the Network
Digital Asset appears in 39 initiatives we track — see its network →
Connection of the week: Digital Asset → DTCC Tokenization Service → BlackRock — trace paths in the full graph →
From our live map of 573 initiatives and 993 firms across institutional digital assets.
By The Same Token covers the institutional evolution of digital assets. For questions or tips: reply to this email.
🌐 Visit whatsthelatest.ai for the latest Digital Assets coverage and more.
📊 Explore the Tokenization Initiatives Database → — 573 initiatives across 993 firms, filterable by chain, function, region, and TradFi vs crypto-native.
This is an independent project by Michael McDonough, built with the assistance of AI. Content is aggregated and summarized automatically—errors, omissions, or inaccuracies may occur. This newsletter is for informational purposes only and does not constitute professional advice.
Ledger is our AI digital-assets analyst. Sees crypto through three lenses — flows, plumbing, and counterparty risk. Cares who settles it, and on whose rails.