Mashreq and Citi trial tokenised deposits on Swift's ledger

Mashreq and Citi have completed a live cross-border payment using bank-issued tokenised deposits, with Swift's new blockchain-based shared ledger coordinating and validating the interbank commitments between the two banks. Mashreq disclosed the transaction on 2 October 2026 in a post describing it as a step towards "always-on" cross-border payments; The Paypers reported it a day earlier, on 1 October 2026.

Neither bank nor Swift has disclosed the amount, currency, originating and destination countries, the legal entities involved, or how final settlement was completed. The transaction sits inside a wider pilot programme, not a commercially available payment service, and it does not establish that corporate customers can now use this route, what it would cost, or which currencies it supports.

That matters for UK readers because both banks run regulated banking operations in London, and because UK treasury teams already rely on Swift-connected banks for cross-border cash management; Swift's new shared ledger is a pilot that could extend that role, not an infrastructure UK banks are generally using yet. If this technology eventually reaches production, it could be relevant to UK corporate treasury teams that manage payments across time zones. It has not reached that point yet.

What actually happened

Mashreq said it worked with Citi and Swift to complete a live transaction using Swift's digital-ledger infrastructure and bank-issued tokenised deposits. The Paypers described the transaction as cross-border and as part of Swift's shared-ledger pilot. Both descriptions can be true at once: "live" distinguishes a real transaction from a simulated test, but it does not mean the service is open to customers generally.

A tokenised deposit, as the Bank of England describes it, is a claim on a commercial bank represented on a programmable platform. It remains a bank liability, not a freely issued cryptoasset. In Swift's pilot model generally, participating banks each issue their own tokenised deposits on their own systems, and the ledger does not merge those into one shared token. Instead, it acts as an orchestration layer: it records and validates interbank payment commitments as tokenised deposits are used, while each bank keeps control of its own assets, keys, funding and settlement decisions. The sources available for this article do not establish exactly what moved in the Mashreq-Citi transaction itself — a transferable deposit claim, coordinated entries on each bank's own ledger, or only an interbank payment commitment.

Final settlement between the banks is then completed through existing systems, such as real-time gross settlement or correspondent-banking arrangements, rather than on the ledger itself. Swift's model allows the commitment to be created and processed continuously, including overnight and at weekends, ahead of that final settlement step. The sources available for this article do not disclose which settlement mechanism was used for the Mashreq-Citi transaction specifically.

Tokenised deposits are not stablecoins

The distinction matters because the two instruments carry different claims and different regulatory treatment.

The Bank of England draws this line explicitly: tokenised deposits are deposit claims represented on programmable platforms, while stablecoins seek to maintain a stable value against a reference asset by holding backing assets or using another stabilisation arrangement. HM Treasury's stated approach follows a "same risk, same regulatory outcome" principle: tokenised deposits fall within the established legal definition of a deposit, while issuing a qualifying stablecoin is set out as a separate regulated activity under the UK's 2026 framework. This article has not independently verified that every provision of that framework has yet commenced.

This is not a minor technical point. Deposit protection, insolvency treatment and who bears the loss if an issuer fails can all depend on whether a holder has a bank deposit claim or a stablecoin claim, and on the specific issuing entity, the holder's location and their eligibility under the relevant scheme. The sources reviewed for this article do not establish what protection, if any, would apply to the tokenised deposits used in the Mashreq-Citi pilot, and readers should not assume Financial Services Compensation Scheme cover extends to a pilot transaction of this kind without confirmation.

Why Swift built a ledger at all

Swift declared its shared ledger ready for initial use on 9 July 2026 and named 17 banks across six continents, including Mashreq and Citi, as preparing to pilot live transactions on it. Swift says more than 40 financial institutions contributed to the ledger's design, and that the project moved from concept to initial activation in nine months. The minimum viable product uses an Ethereum Virtual Machine-compatible architecture built on Hyperledger Besu.

The problem Swift is addressing is interoperability. If each bank issues its own tokenised deposits on its own platform, those tokens cannot easily move between banks without a coordinating layer that both sides trust. Swift's pitch is that its existing position, connecting more than 11,500 institutions across more than 200 countries and territories over more than 40,000 active payment routes, makes it a plausible neutral party to provide that coordination. Those figures describe the scale of Swift's existing messaging network rather than transaction volumes on the new ledger, which remains at pilot stage.

What "always on" does not yet mean

Swift's stated aim for the ledger is to support real-time, 24/7 cross-border payments. That aim is a design goal for the pilot, not a demonstrated outcome of this one transaction. Continuous processing of a payment commitment on the ledger is a different thing from continuous final settlement in central bank money, which still depends on the operating hours and rules of real-time gross settlement systems and correspondent-banking arrangements. Swift's own description of the model is explicit that funds can move overnight and at weekends before final settlement through existing systems, which is a way of saying the two stages are not the same.

Several other questions are unresolved on the public record. It is not known whether a corporate customer initiated or received the Mashreq-Citi payment, or whether it was a bank-funded proprietary test. The token lifecycle, including how each bank's tokenised deposit is created, transferred and redeemed, has not been published. There is no published figure for processing time, fees, foreign-exchange spread or any liquidity saving, so claims about efficiency remain prospective rather than measured. And Swift's July announcement described the 17 named banks as "preparing to pilot" live transactions; a secondary report's suggestion that all 17 have been actively piloting since July is a stronger claim than Swift's own wording supports.

What this means for UK treasury teams

Mashreq's London branch has operated in the UK since 1978 and is regulated by the Prudential Regulation Authority and the Financial Conduct Authority. It focuses on wholesale banking, transaction banking, trade finance and treasury services for corporate and institutional clients. Citibank, N.A., London Branch is authorised in the UK by the Prudential Regulation Authority and is subject to Financial Conduct Authority regulation and limited Prudential Regulation Authority regulation. Both banks therefore already serve the kind of UK corporate treasury client who manages cross-border cash positions and relies on Swift-connected banking relationships to do it.

If a ledger like this reaches production, the plausible benefit for a UK treasury team is longer payment-initiation and commitment windows across time zones, and better visibility of what is owed and when, which could in turn support more efficient use of working capital. That is a reasoned read of the pilot's stated design, not a result anyone has measured. Nothing in the public record establishes general customer access, supported currencies, pricing, service-level commitments, or whether Mashreq's or Citi's London branches specifically would participate in any future service. Tokenised deposits also remain bank liabilities: like any deposit, their value depends on the issuing bank's standing, and a treasury team would need to understand the specific protections attached to a given arrangement before relying on it, rather than assuming blanket deposit-protection cover.

What to watch next

The next useful signals will be which currencies and payment corridors Swift and its pilot banks test, whether and when customer access begins, how final settlement is integrated into the ledger model, and any measured figures on processing time or liquidity benefit rather than stated aims. UK readers wanting the primary detail on tokenised deposits and their regulatory treatment can consult the Bank of England's published work on innovation in money and payments and HM Treasury's consultation on modernising payment services regulation, both of which set out how tokenised deposits are treated as deposits under UK law and HM Treasury's stated approach to regulating qualifying stablecoin issuance as a separate activity.