Two completed remortgages 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 executed through the Great British Tokenised Deposit initiative (GBTD), a project involving Barclays, HSBC UK, Lloyds Banking Group, Monzo, Nationwide, NatWest and Santander. Smaller groups of those banks carried out the individual transactions. The results were announced in a press release by UK Finance.

The deposit remained bank money throughout

A tokenised deposit is a digital representation of money owed to a customer by a commercial bank. Tokenisation changes how a payment can be recorded and instructed; it does not convert the underlying deposit into a freely circulating cryptocurrency.

Customers' money remained inside the regulated banking system throughout the transactions. The GBTD platform controlled when a 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, with the holder's rights depending 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.

That contrast extends to central bank money. The Bank of England has separately carried out design work on a possible 'digital pound', which would be a claim on the central bank rather than on a commercial bank; tokenised deposits leave the existing structure of bank liabilities in place.

UK Finance describes the model as a way to give conventional deposits programmable functions while preserving the safety and trust associated with bank money.

Two use cases, two payment problems

Speed is not the point of these tests. Britain's Faster Payments scheme has carried near-instant account-to-account transfers since 2008; what the pilots add is conditionality — funds that move only when an agreed external event is confirmed, something a standard payment instruction cannot enforce on its own.

Remortgages: releasing funds at completion

Barclays, Lloyds and NatWest carried out the two remortgage transactions. The required amount was reserved in the customer's account and released once the platform received confirmation that the completion condition had been satisfied.

The announcement does not identify which party or system supplied that confirmation. That detail would matter in a commercial service, because payment code can act only on the information it receives; it cannot independently decide that a legal property transaction has completed.

Keeping funds in the customer's account until release could remove the need to transfer them early into a separate holding account. UK Finance said the design can also allow customers to keep earning interest until completion, although it did not disclose whether or how much interest was earned in these specific transactions.

The pilot additionally explored a future digital connection with HM Land Registry. Such an integration could reduce manual coordination, but it was examined as a concept rather than demonstrated in a publicly available system.

Marketplace payment: reserving funds until exchange

Three banks, including HSBC UK, took part 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 resembling an escrow arrangement.

The unresolved problem is how a future service would establish that an item was 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 adopt. A production service would also need rules for damaged products, false delivery claims and transactions disputed after the money has been released. Programmability can enforce an instruction; it cannot determine whether the underlying commercial dispute is legitimate.

A deposit at one bank cannot simply become another bank's liability

Creating a digital representation of a deposit inside a single 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 who banks with 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 a single public blockchain. Quant has previously said its infrastructure could operate 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, rather than simply representing pounds as tokens, is the project's central achievement.

Three transactions do not make a national payment network

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:

• Which organisation will operate and supervise the production network?
• When will a conditional payment become legally final?
• Who is responsible when an external confirmation is incorrect?
• How will mistaken payments and customer disputes be reversed?
• What fallback process applies during a platform or bank outage?
• How will the system perform under national payment volumes?
• What will banks or customers pay to use it?

The banks have not announced when customers could access the service through their normal banking apps.

Even so, the UK has 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 already processed live customer payments.

Three digital bonds will test the institutional case

The next phase is expected to connect tokenised deposits with digital assets. The participating banks plan to issue digital debt instruments that can be traded and settled through the same wider infrastructure, with bond coupons paid in 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 never sends money without receiving the security, and a seller never surrenders 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 establish 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 pose 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 holds authority when payment conditions are disputed, system inputs are wrong or one participant cannot complete its side of a transaction.

This article is provided for informational purposes only and does not constitute financial or legal advice.

: Coindoo