Key Takeaways Seven banks joined shared tokenised-deposit infrastructure. Live sterling funded two completed remortgages. Marketplace money moved, but goods were simulated. Deposits remained
Two remortgages completed and one marketplace payment moved between UK banks after preset conditions were met, using ordinary customer deposits connected through shared blockchain infrastructure.
The transactions were completed through the Great British Tokenised Deposit initiative, or GBTD. Barclays, HSBC UK, Lloyds Banking Group, Monzo, Nationwide, NatWest and Santander participate in the project, although smaller groups of banks conducted the individual transactions.
Transaction record Money transferred: Live customer sterling Completed uses: Two remortgages and one marketplace payment Property transactions: Real Marketplace goods: Simulated; no physical item changed hands Transaction values: Not disclosed Public availability: Still a pilot, not a customer banking serviceA tokenised deposit is a digital representation of money owed to a customer by a commercial bank. Tokenisation changes how the payment can be recorded and instructed; it does not convert the underlying deposit into a freely circulating cryptocurrency.
The customers’ money remained inside the regulated banking system throughout these transactions. The GBTD platform controlled when the payment could move, while the underlying funds continued to represent claims against the participating banks.
That differs from a public stablecoin, which is normally issued under a separate reserve and redemption arrangement. Its holder’s rights depend on the issuer and the product’s legal structure. A tokenised deposit instead begins with an existing bank account and is designed to retain the legal and regulatory treatment attached to commercial-bank money.
UK Finance describes the model as a way to give conventional deposits programmable functions while preserving the safety and trust associated with bank money.
Barclays, Lloyds and NatWest carried out two remortgage transactions. The required amount was reserved in the customer’s account and released after the platform received confirmation that the completion condition had been satisfied.
The announcement does not identify the party or system that supplied that confirmation. That detail would become important in a commercial service because the payment code can act only on the information it receives; it cannot independently decide that a legal property transaction has completed.
Keeping the money in the customer’s account until release could remove the need to transfer it early into a separate holding account. UK Finance said the design can also allow customers to continue earning interest until completion, although it did not disclose whether or how much interest was earned during these specific transactions.
The pilot additionally considered a future digital connection with HM Land Registry. Such an integration could reduce manual coordination, but it was explored rather than demonstrated as part of a publicly available system.
Three banks, including HSBC UK, participated in a separate customer-to-customer payment modelled on a marketplace purchase. The buyer’s money was reserved for the transaction and released to the seller after the agreed exchange condition was confirmed.
Real sterling moved between accounts, but no physical goods changed hands. The exchange was simulated to test whether a bank deposit could carry payment conditions that resemble an escrow arrangement.
The unresolved problem is how a future service would establish that an item had been delivered in the agreed condition. Buyer confirmation, courier data or a marketplace record could provide the trigger, but the banks have not disclosed which model they would use.
A production service would also need rules for damaged products, false delivery claims and transactions disputed after the money had been released. Programmability can enforce an instruction; it cannot determine whether the underlying commercial dispute is legitimate.
Creating a digital representation inside one bank is relatively straightforward. Moving it to another institution is harder because each deposit remains a liability of the bank holding the customer’s money.
A customer’s balance at Barclays is money Barclays owes that customer. If the customer pays someone at HSBC, the system must coordinate both the customer-facing transfer and the obligations created between the two banks.
The shared GBTD platform was developed by Quant to connect the participating institutions rather than replace their core banking systems with one public blockchain. Quant previously said its infrastructure could work across bank ledgers, Faster Payments, real-time gross settlement systems, open banking and tokenised-deposit platforms.
This common layer allowed different banks to apply the same conditional-payment logic while retaining their own accounts and internal systems. That interoperability—not simply representing pounds as tokens—is the project’s central achievement.
The tests demonstrate that the mechanism can process live customer money. They do not establish whether it can operate affordably and reliably at the scale of Britain’s existing payment infrastructure.
Several operational questions remain unanswered:
The banks have not announced when customers could access the service through their normal banking apps.
The UK has nevertheless moved further than the development work described in Canada’s Big Six banks’ tokenised-deposit initiative. The Canadian institutions have announced an interbank model they intend to explore, while the British consortium has processed live customer payments.
READ MORE:
XRP Ledger Nears Upgrade for Limited Account Access
The next phase is expected to connect tokenised deposits with digital assets. Participating banks plan to issue digital debt instruments that can be traded and settled through the same wider infrastructure, with bond coupons paid using tokenised bank money.
UK Finance said the project will examine delivery-versus-payment-versus-reserves settlement. The aim is to coordinate the asset and cash legs so that a buyer does not send money without receiving the security, and a seller does not surrender the security before receiving payment.
Reuters reported that the participating banks intend to test three digital bonds in the first quarter of 2027. The project also plans to create an operating company and develop the rulebook and governance framework needed to move toward production.
The retail transactions have shown that software can coordinate live payments across separate banks. The bond tests will ask a more demanding question: whether the same infrastructure can exchange money and regulated assets without leaving either side of the transaction exposed.
Technical interoperability is therefore no longer the only hurdle. A commercially useful network will depend on whether the banks can agree who has authority when payment conditions are disputed, system inputs are wrong or one participant cannot complete its side of the transaction.
This article is provided for informational purposes only and does not constitute financial or legal advice.
The post UK Banks Move Real Deposits Between Banks on Blockchain appeared first on Coindoo.
