RWA Infrastructure11 min read
MB
Editorial Team
·August 16, 2026

How Does a Cross-Border Tokenized Redemption Settle?

On 6 May 2026, Ripple redeemed part of its Ondo Short-Term US Government Treasuries position on the XRP Ledger, and the asset leg completed in under five seconds. The cash leg took a different path entirely: Ondo initiated a payout instruction through the Mastercard Multi-Token Network, which routed it to Kinexys by J.P. Morgan, which debited Ondo's Blockchain Deposit Account and settled US dollars to Ripple's Singapore bank account through correspondent banking. That asymmetry is the substance of the transaction. It was the first cross-border, cross-bank redemption of a tokenized Treasury, and what it demonstrates is not atomic settlement but reliable coordination across a settlement gap that still exists. This guide walks the flow step by step and sets out what an issuer needs before they can replicate it.

TL;DR — Key Takeaways

  • ✓The Transaction: 6 May 2026 — Ripple redeemed OUSG on the XRP Ledger; the asset leg completed in under five seconds.
  • ✓The Cash Leg: Mastercard MTN routed a payout instruction to Kinexys by J.P. Morgan, which debited Ondo's Blockchain Deposit Account and settled dollars to Singapore via correspondent banking.
  • ✓Not Atomic: Two legs settling separately under coordinated instruction. Principal risk is managed across the gap, not eliminated by the mechanism.
  • ✓What Was Hard: Not the chain. The bank with a blockchain-addressable deposit account, the routing layer, and correspondent reach into the destination jurisdiction.
  • ✓The Lesson for Issuers: Cross-border redemption capability follows banking relationships. Chain selection is the easy part and the part most programmes over-weight.

Ready to get started?

Join others who are already using our platform.

How Does a Cross-Border Tokenized Redemption Settle?

Five Seconds on One Side, Correspondent Banking on the Other

The asset leg of the first cross-border, cross-bank tokenized Treasury redemption completed in under five seconds on a public ledger. The cash leg travelled through a card network's routing layer, a commercial bank's deposit infrastructure, and a correspondent banking chain into Singapore.

Read quickly, this is a story about speed. Read carefully, it is a story about the distance between the two legs — because a redemption is not complete when the token is burned, it is complete when the holder has the money. The five-second figure describes one half of a transaction whose other half runs on infrastructure built in the twentieth century, and the engineering that mattered was in connecting them.

Ripple redeemed a portion of its OUSG holdings on the XRP Ledger; the associated fiat settlement was triggered via the Mastercard Multi-Token Network, with Kinexys debiting Ondo's Blockchain Deposit Account and settling dollar proceeds to Ripple's bank account in Singapore.

— Ondo Finance, Kinexys by J.P. Morgan, Mastercard and Ripple, 6 May 2026

Four named institutions appear in one sentence describing a single redemption. That count is the finding.

The Flow, Step by Step

Five steps across four institutions, with the boundary between on-chain and banking crossed exactly once — at the point where an on-chain redemption becomes a payment instruction a bank can act on.

StepWhoWhat happens
1RippleRedeems part of its OUSG position on the XRP Ledger — under five seconds
2OndoInitiates a fiat payout instruction through the Mastercard Multi-Token Network
3Mastercard MTNRoutes the instruction across the chain-to-bank boundary to Kinexys
4Kinexys by J.P. MorganDebits Ondo's Blockchain Deposit Account
5Correspondent networkSettles US dollar proceeds to Ripple's Singapore bank account
◆

Key Insight

Step 1 and step 5 are separated by three intermediating steps, and the token is gone after step 1. Between the burn and the credit, Ripple holds neither the asset nor the cash — it holds a claim on Ondo, and Ondo's performance depends on MTN routing correctly and Kinexys executing. That exposure is short and was plainly acceptable to the parties, all of whom are large regulated institutions that know each other. It would not be equally acceptable between counterparties who do not, which is why this design generalises through relationships rather than through technology.

Why This Is Not Atomic Settlement

Atomic delivery-versus-payment means the settlement mechanism itself guarantees that both legs complete or neither does. Here the legs settle on separate systems under coordinated instruction, which means the guarantee is contractual and operational rather than mechanical.

This is a design choice with an argument behind it. Atomic settlement removes principal risk and destroys multilateral netting in the same movement, converting a credit exposure into an intraday liquidity requirement — the trade examined in what atomic settlement actually changes. A flow that keeps the cash leg inside the banking system keeps netting, keeps correspondent reach, and keeps the settlement gap. For a cross-border redemption into a jurisdiction where the paying bank has no direct presence, that may be the only structure available.

What This Model Keeps

  • Multilateral netting inside the banking system
  • Correspondent reach into jurisdictions without direct presence
  • Commercial bank money as the settlement asset
  • Existing sanctions and payment screening at the bank

What It Does Not Remove

  • The gap between asset extinguishment and cash credit
  • Dependence on each intermediary performing
  • Banking-hours and holiday constraints on the cash leg
  • Correspondent chain latency into the destination market

Neither column is a criticism. The transaction did what it set out to do, and the parties describe it accurately as a first for cross-border, cross-bank redemption. The misreading to avoid is treating a five-second asset leg as a five-second settlement, because the holder's position is not resolved until the cash arrives — a distinction with legal consequences set out in settlement finality for tokenized assets.

What an Issuer Needs to Replicate It

Four prerequisites, and only one of them is technical. The public ledger leg is available to anyone; the rest is banking relationships, and that is where a programme either can or cannot do this.

A bank with a blockchain-addressable deposit account

The cash leg started from Ondo's Blockchain Deposit Account at Kinexys — commercial bank money movable by blockchain-triggered instruction. Without an account of this kind, an on-chain redemption event has no way to reach into the banking system, and the issuer is left funding payouts manually.

An interoperability layer willing to route the instruction

Mastercard's Multi-Token Network carried the payout instruction across the boundary between an on-chain event and a bank payment. This is a message-and-routing function, and access to it is a commercial relationship rather than a public API.

Correspondent reach into the destination jurisdiction

Dollars settled into a Singapore account through Kinexys's correspondent network. An issuer whose bank lacks reach into where the holder banks does not get a faster redemption; it gets the same redemption plus a chain leg.

Counterparties large enough to accept the gap

Between token burn and cash credit, one party carries exposure to the other. Institutions of this size, with existing relationships and documentation, absorb that easily. A smaller programme must either shorten the gap or collateralise it, and neither is free.

Listed together, the prerequisites describe an incumbent advantage rather than a technological one. That is worth stating plainly, because the common framing of tokenized settlement is disintermediation, and this transaction ran through a card network, a global bank, and a correspondent chain to reach a bank account. It did not remove intermediaries; it made them interoperate.

Where This Design Breaks

The failure modes cluster at the boundary and in the cash leg, because the on-chain leg is the part with the fewest dependencies. A redemption that burns the token before the cash path is confirmed is the specific structure to avoid at smaller scale.

Robust

  • The asset leg — public ledger, seconds
  • Bank-side screening and controls
  • Settlement asset quality — commercial bank money
  • Netting inside the correspondent system

Fragile

  • The instruction hop across the boundary
  • Weekend and holiday cash settlement
  • Exposure between burn and credit
  • Any intermediary having an outage

Ask before relying on it

  • What unwinds a burn if cash fails?
  • Who bears the gap exposure, in writing?
  • Which jurisdictions have correspondent reach?
  • What is the cut-off in the destination market?

The first question in the third column is the one that most often has no good answer. On-chain burns are hard to reverse and cash failures are ordinary, so a programme needs a defined remedy — reissuance, an indemnity, or a hold on the burn until the cash path confirms. Deciding that after the first failure is considerably more expensive than deciding it now.

How Blockmaze Handles Two-Leg Settlement

Where settlement spans a chain and a banking system, the compliance question is which record is authoritative and what state the position is in between the legs. Both need to be explicit rather than inferred from whichever system is queried first.

In-Flight State Is Recorded

The interval between asset extinguishment and cash credit is a recorded state on the position, so a reconciliation run mid-flow reports a pending settlement rather than a discrepancy.

Authoritative Record Declared

Where a chain record and a bank record can disagree, which one governs is declared in advance — the same discipline the mirror-token model requires between chain and depository.

Redemption Path per Jurisdiction

Cash-leg reach and cut-off times are recorded per destination, so a holder's redemption expectation matches the corridor actually available to them rather than a global average.

Eligibility Checked Before the Burn

Because the asset leg is effectively irreversible, transfer and redemption eligibility is enforced before extinguishment rather than reconciled afterwards.

The third item is where most cross-border programmes underdeliver. A redemption promise that holds in one corridor and not another is not a defect of the token, it is a property of the banking path behind it — and holders learn which corridor they are in at the worst possible moment unless it is disclosed up front, as with the wider jurisdictional questions in navigating cross-border RWA regulatory challenges.

Settling Across a Chain and a Banking System?

Blockmaze records in-flight settlement state, declares which record governs, and enforces redemption eligibility before the asset leg is irreversible.

Frequently Asked Questions

What actually happened in the cross-bank tokenized Treasury redemption?

On 6 May 2026, Ripple redeemed part of its holding of Ondo Short-Term US Government Treasuries on the XRP Ledger. Ondo then initiated a fiat payout instruction through the Mastercard Multi-Token Network, which routed it to Kinexys by J.P. Morgan. Kinexys debited Ondo's Blockchain Deposit Account and settled US dollar proceeds to Ripple's bank account in Singapore through its correspondent banking network. The asset leg on XRPL completed in under five seconds; the cash leg travelled the conventional route.

Why does it matter that only one leg was fast?

Because the gap between the two legs is where the risk lives. When the asset is extinguished in five seconds and the cash arrives through correspondent banking, one party is briefly without either — the definition of principal risk, which atomic delivery-versus-payment is designed to eliminate. This transaction did not eliminate it; it coordinated across it. That is a real achievement in cross-bank plumbing and a different achievement from atomicity, and conflating the two overstates what has been solved.

What is the Mastercard Multi-Token Network doing here?

Acting as the interoperability layer between an on-chain event and a bank payment instruction. The redemption on XRPL is not something a correspondent banking network can observe or act on directly, so MTN takes the payout instruction and routes it to a bank that can execute it. It is a message-and-routing layer rather than a settlement layer — the money still moves through Kinexys and the correspondent chain, and MTN's contribution is that the instruction crosses the boundary reliably.

Is this different from atomic settlement?

Yes, materially. Atomic delivery-versus-payment means both legs settle or neither does, enforced by the settlement mechanism itself, which removes principal risk and destroys multilateral netting in the same move. This transaction has two separately settling legs coordinated by instruction — the asset leg on a public chain and the cash leg through bank rails. It preserves the banking system's netting and correspondent structure, and preserves the settlement gap along with it. Both models are legitimate; they trade different things.

What is a Blockchain Deposit Account in this flow?

A commercial bank deposit account whose balance can be moved by blockchain-triggered instruction rather than only by conventional payment messaging. In this transaction Ondo held one at Kinexys, and it was debited when the redemption instruction arrived. The significance is that the cash leg started from commercial bank money at a regulated institution rather than from a stablecoin or an on-chain balance — the redemption proceeds were bank deposits throughout, which is why the correspondent network could carry them.

What should an issuer take from this for their own programme?

That cross-border redemption capability is a function of banking relationships, not of chain selection. The fast leg required a public ledger, which is widely available; the slow leg required a bank with a blockchain-addressable deposit account, an interoperability network willing to route the instruction, and correspondent reach into the destination jurisdiction. An issuer without those relationships gets the five-second leg and then waits. Chain choice is the easy part of this problem and the part most programmes over-weight.

Ready to get started?

Join others who are already using our platform.