We manage your security to weather the AI storm →

← Resource Hub

DBS and Kinexys Launch 24/7 Tokenized Deposit Transfers

By Owen ThurmPublished 5 min read

Part of our guide to digital asset security for banks

DBS and Kinexys Launch 24/7 Tokenized Deposit Transfers

Quick answer. On November 16, 2026, DBS and Kinexys by J.P. Morgan launched instant USD transfers between US and Singapore tokenized deposit accounts. Ant International is the first client and Partior orchestrates settlement. A Saturday window still blocks moves to and from traditional accounts.

Watch: DBS and Kinexys Launch 24/7 Tokenized Deposit Transfers 1:40
Video transcript

DBS and Kinexys by J.P. Morgan now move US dollars between US and Singapore tokenized deposit accounts. The open question is how it is controlled.

The service launched November 16, linking DBS Token Services with the Kinexys deposit network. Ant International is the first named client, and Partior orchestrates settlement.

The MAS case study says no token crosses ledgers. Instead, the liability transforms between banks. Guardian's view: no bridge custody, but three systems must agree on one payment's state.

Moves to and from traditional accounts still have a three-hour outage every Saturday, three to six p.m. Eastern Time. DBS has published no schedule for its enhancement.

On November 19, MAS used this link as a case study in its BLOOM field guide, which asks for records of transaction states, operating windows, reconciliation and recovery. MAS says it is neither regulation nor endorsement.

As of November 20, limits, fees, replay controls, signing keys, rollback authority and the discharge point were all undisclosed. Ant International remained the only named client.

In Guardian's view, get these answers in writing: who holds the authoritative record, how duplicate messages are rejected, who can roll back, how keys are held, and the fallback route.

Read the full article for the checklist, or talk to Guardian about its Digital Asset Assurance Pilot for tokenized deposit corridors.

What DBS and Kinexys Launched

On November 16, 2026, DBS and Kinexys by J.P. Morgan announced a live service for instant USD transfers between blockchain-based accounts in the US and Singapore.[1, 2]

The banks say it runs around the clock, including weekends and outside traditional banking hours.

It connects DBS Token Services with the Kinexys account-based, permissioned tokenized deposit network. The users are institutional clients and corporate treasury teams.[3]

Ant International is the first named client. It uses the link for treasury and liquidity management across its entities in both markets.

Partior provides settlement orchestration. DBS and Kinexys describe themselves as founding Partior shareholders.

The launch puts into operation an interoperability framework the two banks first announced on November 11, 2025.[4]

The two banks also co-lead the token interoperability workgroup of BLOOM, a Monetary Authority of Singapore initiative.

That moves the question for other banks. It is no longer whether two deposit ledgers can connect, but how the connection is controlled.

How a Transfer Moves

No token crosses between the two ledgers. The MAS case study says deposits stay separately issued liabilities of each bank.[3]

Instead, the liability transforms. The sender's claim on its own bank becomes the beneficiary's claim on the other bank.

Partior coordinates the interbank obligation that results. MAS describes it as a common orchestration and settlement layer, linked to the underlying correspondent banking arrangements.

The case study's figure lists payment messaging, payment pre-validation and atomic interbank settlement. MAS says pre-validation and coordinated settlement give greater certainty that a payment completes.

Each bank keeps responsibility for the controls in its own tokenized deposit environment, payment and blockchain systems, and customer relationships.

Our permissioned vs permissionless blockchain comparison explains why, on a permissioned network, operator keys and access control become the perimeter.

Guardian analysis: this design avoids a bridge holding tokens in custody. It does not remove the boundary, because three systems must agree on one payment's state.

Our tokenized deposits vs stablecoins comparison explains why a deposit token stays a bank liability, and who holds its admin keys.

The Saturday Gap

The 24/7 claim has a limit. Transfers inside the Kinexys Blockchain Deposit Account network run 24/7/365.[1]

Moving funds between traditional demand-deposit accounts and blockchain accounts has a three-hour outage every Saturday, from 3 to 6 p.m. Eastern Time.

DBS says an enhancement is under development. As of November 20, no schedule for it had been published.[5]

For a Singapore treasury team, that window falls in the early hours of Sunday.

Guardian analysis: a scheduled outage is a pause with transfers in flight. A funding request sent just before 3 p.m. can start on one side and stall on the other.

Guardian's Citrea Stablecoin Bridge review records this pattern in finding L-03 (Low, acknowledged). A pause during the confirmation window would make in-flight transfers fail at the destination until an explicit retry, and could prevent reconciliation.[6]

The controls are a cutoff ahead of the window, a register of pending items, and a defined state for each item at restart.

What Has Changed Since

On November 19, three days after the launch, MAS published version 1.0 of its BLOOM field guide on extending settlement capabilities. It uses the DBS and Kinexys link as a case study.[3]

Its implementation profile is a template covering transaction context, participants and functions, the transaction journey, settlement and connectivity, controls, operating conditions and evidence.

The records it calls for include interfaces, transaction states, operating windows, reconciliation, exceptions, fallback, recovery, and change and access management. Technical completion, discharge and legal finality are recorded separately.

It separates intended design from capabilities implemented, tested or observed, and assesses normal operation, exceptions and recovery.

The guide is descriptive: MAS says it is not legislation, regulation, regulatory guidance, supervisory expectations or advice. Its examples do not imply MAS or BLOOM approval, recommendation or assurance.

As of November 20, Ant International remained the only named client. No follow-on client, usage figure or payment volume had been published.[5, 7]

Our searches through November 20 found no incident, completed-transfer loss, recovery event or enforcement action tied to the corridor, and no corridor-specific supervisory statement.

What Is Not Disclosed

The public launch materials leave most operating details out. Until they are published, do not assume a particular message design, key model or exception process.[1, 2, 3]

ItemStatus on November 20
Transfer limits and feesNot disclosed
Message format, idempotency and replay controlsNot disclosed
Signing keys, quorum and rotationNot disclosed
Emergency rollback authorityNot disclosed
Trigger that discharges the customer obligationNot disclosed

Checks for Banks and Treasury Teams

Treasury teams onboarding to this corridor should get these answers from their bank in writing. Banks building a similar link should answer them before launch.

Then map each answer onto a register with owners, limits and restart evidence. Our stablecoin settlement risk framework provides one, and most of its rows carry over to deposit tokens.

  • Which system holds the authoritative record for each payment state, and who signs off reconciliation.
  • How a duplicate, replayed or reordered message is detected and rejected.
  • Who can pause, roll back or settle an exception, under what quorum, who funds a leg left open, and how unseen reversals are caught.
  • How keys that sign payments or change limits, allowlists and routing are held, rotated and revoked at each bank and Partior.
  • Which treasury user roles can instruct payments, which limits need a second approver, and what a stolen portal or API credential could do.
  • The legal point at which the customer's payment obligation is discharged.
  • The fallback route when the corridor, Partior or a correspondent link is down.

Threat-model your tokenized deposit corridor

Guardian's Digital Asset Assurance Pilot maps liability states and control owners, writes invariants for message uniqueness and reconciliation, and pentests the consoles, APIs and signing services behind treasury permissions.

Frequently Asked Questions

Does the launch use a public blockchain?

No public-chain transfer is announced. The November 2025 framework was exploratory and contemplated both public and permissioned chains, including J.P. Morgan's JPMD deposit token on Base. The live service links two permissioned bank networks.[1, 4]

Why does it cover only US dollars?

The release describes USD transfers only and gives no reason. Separately, Ledger Insights questioned why Singapore dollars were left out of the launch.[1, 2]

Why route settlement through Partior?

Ledger Insights describes transactions as synchronized through Partior and calls it a more neutral venue. It says the model is repeatable across different banks and currencies.[2]

Sources

  1. DBS Group: DBS and Kinexys by J.P. Morgan launch industry-first 24/7 interoperability solution for cross border tokenised deposit transfers
  2. Ledger Insights: DBS, JP Morgan interlink tokenized deposits for 24/7 USD payments
  3. Monetary Authority of Singapore: BLOOM: A Field Guide to Extending Settlement Capabilities
  4. DBS Group: DBS and Kinexys by J.P. Morgan to develop framework for interbank tokenised deposit transfers across multiple blockchains
  5. InvestX: DBS et Kinexys lancent des transferts 24h/24 de dépôts tokenisés
  6. Guardian Security: Citrea Stablecoin Bridge security review, finding L-03
  7. ACIS Research: DBS and J.P. Morgan open a US–Singapore deposit corridor, giving companies a bank channel for on-chain dollars