Synchronisation Lab

A platform for industry to demonstrate use cases and understand business models for synchronisation, helping us validate design choices and progress towards delivery into production of a new synchronisation capability for the renewed RTGS service.
Michael Jones, our Director of Payment Operations, shares more in a video about what synchronisation is, and what we are looking to achieve in the Synchro Lab. This provide context for the videos, linked in the table below, from certain organisations participating in the Synchro Lab explaining more about their propositions and how these will use the synchronisation functionality.

This video requires third-party analytical cookies to play. Read our cookie policy for more information.

Areas of focus for Lab Participants

Organisation
Proposed areas of focus
Detail of use cases
Further information
Demo video
Atumly
Multi-money issuance and redemption
Atumly will test how digital money (e.g. stablecoin) issuance and redemption can be coordinated with fiat payment settlement.
About Atumly
 
Baton Systems
Delivery vs Payment - tokenised securities, and Payment vs. payment cross-border spot fx
Baton Systems will test FX transactions, and intra-day repo, integrating with a collateral platform and bank/payment service providers.

FX Settlement with Core-FX: Collaborative, Flexible and Secure

Real-time Payment Control Across Settlements

 
Chainlink
Decentralised solution provider
Chainlink will test a decentralised solution to execute synchronised settlement between central bank money and securities issued on a DLT ledger
Automated compliance for digital assets
Synchro Lab Use Case - Chainlink
Cleartoken
Collateral optimisation: Secured Financing
Cleartoken will test an auto collateralised repo facility and integrate with its activities in the Bank's Digital Securities Sandbox.
About Cleartoken
 
Ctrl Alt
Delivery vs Payment - tokenised securities
Ctrl Alt will test settlement of a Digital Gilt and integrate with its Tokenised Asset Processing system (TAPs) and banks/PSP partners.
About Ctrl Alt
 
GBTD
Multi-purpose orchestration platform, and Delivery vs Payment - tokenised securities
GBTD will test settlement of a bond or gilt and integrate with GBTD's orchestration layer.
GBTD tokenised sterling deposits
Great British Tokenised Deposit project – UK Finance
LSEG
Multi-purpose orchestration platform, securities vs payment - tokenised securities, and Payment vs Payment - cross-border spot FX
LSEG will test multi-bank FX Transactions and repo, and PVP transactions, integrating with LSEG's Digital Settlement House (DiSH) platform, and other banks and payment service providers.
LSEG Launches Digital Settlement House
 
Monee
Delivery vs Payment - tokenised securities
Monee will test settlement of HM Treasury's Digital Gilt instrument (DIGIT), and cross currency settlement, integrating with Monee's activities in the Digital Securities Sandbox.
About Monee
 
NPTN (LMS)
House purchase
NPTN (LMS) will test a housing remortgage transaction alongside title registration, and integrating with its NPTN sandbox and HM Land Registry  to show synchronisation within an end-to-end transaction flow.
About NPTN by LMS
 
Nuvante
Multi-money issuance and redemption, and securities vs payment - tokenised securities
Nuvante will test issuance and redemption flows for new forms of digital money (e.g. stablecoins) and settlement of tokenised-security transactions (e.g. bonds).
Nuvante's participation in the Bank of England Synchronisation Lab 2026
BoE Synchronisation Lab – Nuvante
OSTTRA  Collateral optimisation: Conditional Margin Payments
OSTTRA will test coordination of variation margin release with confirmed cash flow payments, integrating with OSTTRA’s triResolve Margin settlement service  and other banks and payment service providers.
About OSTTRA
 
Partior
Collateral Optimisation: Secured Financing, Payment vs Payment cross border spot FX, and delivery vs payment - tokenised securities
Partior will test intraday repo and FX swaps integrating with a collateral platform and bank/payment service providers.
Partior FX Settlement
 
PEXA
House purchase
PEXA will test a housing purchase or remortgage transaction integrating with transaction stakeholders and HM Land Registry to show an end to end transaction flow.

About PEXA

Bank of England's Synchronisation Lab

PEXA - Synchro Lab Initiative
Quant
Liquidity optimisation for non-financial corporates
Quant will test liquidity rebalancing transactions across multiple bank accounts, integrating with Quant flow corporate orchestration.
Synchronised multi-Bank Treasuring rebalancing for Corporate Liquidity Optimisation
Quant - Synchro Lab Corporate Treasury Rebalancing
Swift
Payment vs Payment - cross-border spot FX, and delivery vs payment - tokenised securities
Swift will test FX transactions (non-CLS) and tokenised securities settlement integrating with participants in tokenised-assets markets.
Swift takes bold steps to unlock the benefits of digital finance on a global scale
 
Tokenovate
Collateral Optimisation: Conditional Margin Payments
Tokenovate will test automated workflows for derivatives and collateral asset transfers, integrating with its Novat protocol.
About Tokenovate
Atomic settlement for intra-day repo transactions by Tokenovate
Transpact
Delivery vs Payment - multi-purpose
Transpact will test a range of use cases, including sale/purchase of all types of financial securities, derivatives and assets, different deposit type situations, and property sale/purchases, amongst other use-cases.
Synchronisation using Transpact.com
 
UAC Labs AG
Decentralised solution provider
UAC Labs will test a decentralised approach to coordinated synchronised settlement between different external asset ledgers.  UAC Labs — Bank of England Synchronisation Lab Participation
 

What are the key timelines and processes?

We expect the Lab to launch in spring 2026 and to run for around six months.

Application stage

Applications closed on 28 November 2025. Information about successful applicants and their use cases can be found below.

Before the Lab is operational

Successful applicants will receive more detailed specifications. They will then have around two months to build or develop their prototypes. During this time, they will be able to iterate with us on their design and build to support quick integration when the Lab launches.

While the Lab is operational

Lab Participants will use the capabilities that we provide to test their use cases; demonstrate how they would (as a synchronisation operator) interact with RT2 and synchronisation users; and discuss their in-Lab activities and learnings with us and key stakeholder groups as appropriate.

After the Lab closes

Lab Participants will be invited to present their use cases and findings at an industry showcase. We will publish a report summarising the key learnings for the live functionality. We will use the Lab’s findings to support ongoing design and subsequent development work towards delivering an RTGS synchronisation capability into production.

What is the design of the Synchronisation Lab?

The Lab will enable its participants (prospective synchronisation operators) to simulate the basic interactions required to achieve synchronised settlement.

The Lab is designed to function as a platform. Our expectation is that Lab Participants will build the additional elements required to integrate with the Lab functionality and demonstrate their use cases when using the Lab. This could include elements required to integrate with their own test platforms; and to demonstrate how they would integrate with synchronisation users (RTGS account holders, asset ledger operators, and end-customers in relevant markets) to achieve an end-to-end synchronisation transactions.

Figure 1: Design of the Synchronisation Lab

The Synchro Lab infrastructure will contain a settlement engine, user interface and API layer that synchronisation operators can interact with.

The Lab will emulate selected key capabilities of RT2, at the basic level required to simulate synchronised settlement. These are:

  • Settlement engine: Houses the essential functions required to settle and manage a transaction.
  • User interface: Offers Lab Participants visibility on transactions that they orchestrate, along with other relevant information.
  • Application Programming Interface (API) layer: Provides a suite of APIs for Lab Participants to oversee and control the complete lifecycle of settling a transaction within the Lab.

The Lab will explore at least two different synchronisation models. These will help the Bank, RTGS account holders, and prospective synchronisation operators to evaluate different options for orchestration and information exchange across reliability, customer service, cost, and other parameters.

  • Proposed Model 1: Synchronisation operators send the earmarking instruction to RT2 and instruct the final settlement.
  • Proposed Model 2: RTGS account holders send the earmarking instruction, under direction from a synchronisation operator. Synchronisation operators instruct the final settlement. In the Lab, the earmarking instruction would be simulated from the Lab Participant.
  • Two further models will also be considered based on the feedback gathered during initial experimentation. These may test additional controls that RTGS account holders could apply.
  • In all models, it is envisaged that synchronisation operators will need the ability to request funds to be earmarked and released, and be able to cancel a transaction.

For more information on the proposed models, refer to Annex 3 of Synchronisation Lab – terms of participation.

Successful applicants will receive full specifications before the Lab launches to enable their design and build.

This page was last updated 05 August 2026