Nostro/Vostro Accounts: The $10 Trillion Problem DLT Is Solving
Correspondent banks park trillions in pre-funded foreign accounts just to enable the possibility of cross-border payments. This capital sits idle, earns nothing useful, and costs the global financial system billions annually. On-demand liquidity via the XRP Ledger eliminates this requirement entirely.
This article is for informational purposes only and does not constitute financial, legal, or investment advice.
THE DEAD CAPITAL PROBLEM
Before a bank in Mexico can receive a wire from a bank in Japan, both institutions need a trusted intermediary — or a chain of intermediaries — who can vouch for and settle the transaction. Because direct relationships between every pair of banks globally are impractical, the correspondent banking system evolved: large "hub" banks maintain accounts in each other's names across dozens of currency jurisdictions.
These accounts — nostro accounts (foreign currency accounts a bank holds at another bank) and vostro accounts (the same accounts from the other bank's perspective) — are a necessary feature of the correspondent banking model. But they come with a structural cost that has no clean workaround under the traditional system: pre-funding.
To ensure they can settle a payment request from a customer at any time without waiting for funds to arrive, correspondent banks must maintain balances in their nostro accounts in advance. This capital is immobilized. It's not being deployed in loans, investments, or yield-generating activities. It simply sits there, waiting to be used as a settlement buffer.
McKinsey's research on global correspondent banking has estimated the total capital trapped in nostro/vostro pre-funding at roughly $10 trillion globally. This figure is routinely cited by SWIFT, the Bank for International Settlements, and industry working groups studying payment modernization.
THE CORRESPONDENT BANKING CHAIN
The scale of this problem becomes clearer when you map an actual cross-border payment. A small business in Thailand wiring funds to a supplier in Brazil might touch four to six institutions before the payment clears:
- Originating bank (Thailand) → debits sender's account, initiates SWIFT message
- Thai correspondent bank → routes through regional hub
- U.S. dollar clearing bank → most international payments clear through USD intermediaries
- Brazilian correspondent bank → converts USD to BRL
- Beneficiary bank (Brazil) → credits supplier's account
Each hop in this chain introduces latency (typically adding 1–2 business days per institution), fees (averaging 2–6% of transaction value for small businesses per World Bank Remittance Prices Worldwide data), and the requirement for pre-funded nostro balances at each institution in the chain.
The World Bank's Remittance Prices Worldwide database consistently shows global average remittance costs of 6–7% of transaction value, far above the UN Sustainable Development Goal target of 3%. Correspondent banking fees are the primary driver of this gap.
WHY THE TRADITIONAL SYSTEM CAN'T SELF-FIX
SWIFT has existed since 1973 and connects over 11,000 financial institutions across 200+ countries. SWIFT GPI (Global Payments Innovation), launched in 2017, meaningfully improved payment tracking and speed — same-day settlement in many corridors is now common. But GPI doesn't solve the nostro pre-funding problem. It still requires pre-funded balances at each correspondent institution.
The structural constraint is this: without pre-funded capital, a correspondent bank cannot guarantee it can settle on demand. Every efficiency improvement in messaging speed still rests on the same capital immobilization foundation. SWIFT GPI speeds up the notification layer; it doesn't change the settlement economics.
ISO 20022, the new messaging standard that SWIFT is migrating to (with a deadline of November 2025 for the core MT-to-MX transition), improves data richness and compliance screening. But again: richer messages traveling through the same correspondent chain with the same pre-funded accounts doesn't eliminate the dead capital cost.
THE ODL ARCHITECTURE: CAPITAL-FREE SETTLEMENT
Ripple's On-Demand Liquidity (ODL) product — built on the XRP Ledger — takes a fundamentally different architectural approach. Instead of pre-funding accounts in destination currencies, ODL uses XRP as a real-time bridge asset.
A simplified ODL flow for a U.S.-to-Mexico payment looks like this:
- A payment provider (originating institution) converts USD to XRP on a U.S. crypto exchange
- XRP is transmitted across the XRP Ledger in 3–5 seconds
- A market maker or exchange in Mexico receives the XRP and converts it to MXN
- MXN is deposited into the beneficiary's account
The key difference: no capital needs to be pre-positioned in Mexico. The liquidity is sourced from XRP markets on demand, at the moment of transaction. If XRP markets in a given corridor are sufficiently liquid, the payment originates, crosses, and settles in under 30 seconds — without the originating institution having maintained a single dollar of nostro balance in Mexico.
Ripple has confirmed publicly that ODL was processing an estimated $15 billion in annualized volume by 2024 across 40+ currency corridors. Live corridors include USD/MXN, USD/PHP, GBP/EUR, USD/BRL, and others. The number of active corridors has been expanding as XRP liquidity deepens.
WHAT THIS MEANS FOR CAPITAL EFFICIENCY
For a financial institution running cross-border payments at scale, the capital efficiency difference between correspondent banking and ODL is substantial:
| Model | Pre-Funded Capital Required | Settlement Time | Typical Cost |
|---|---|---|---|
| Correspondent Banking | Millions per corridor (must cover daily volume) | 1–5 business days | 2–6% (SMB); 0.5–2% (wholesale) |
| SWIFT GPI | Same pre-funded requirements | Same day to 1 day (improved) | Improved tracking, similar fees |
| Ripple ODL (XRPL) | Zero pre-funded nostro required | 3–30 seconds | <1% (including FX spread) |
The freed capital can be redeployed into revenue-generating assets — loans, investments, or simply higher reserve yields. For a mid-size payments provider maintaining $50 million in nostro balances across five corridors, shifting to ODL could unlock all $50 million for productive use.
LIQUIDITY DEPTH: THE REMAINING CHALLENGE
ODL's effectiveness is directly dependent on XRP market liquidity in each currency corridor. For major corridors — USD/MXN, USD/PHP, EUR pairs — XRP liquidity is now deep enough to support institutional settlement volumes. Kaiko Research rated XRP's global liquidity an AA score (95/100 in 2025), tied with Ethereum and second only to Bitcoin.
For smaller or exotic corridors (e.g., USD/NGN, USD/KES), liquidity is thinner. Large trades in low-liquidity corridors can create slippage — price impact that erodes the cost advantage. This is the primary reason ODL adoption has concentrated in major currency pairs first, with expansion to emerging market corridors following as XRP volume grows.
Ripple addresses this through three mechanisms:
- Market maker agreements — Ripple has arrangements with major crypto market makers to provide consistent two-sided liquidity in priority corridors
- RLUSD integration — Ripple's own USD stablecoin on XRPL can serve as an intermediary asset alongside XRP, improving route efficiency
- XRPL DEX and AMM — The native on-ledger DEX allows for automated liquidity routing, and the AMM (deployed November 2024) provides passive liquidity depth
THE REGULATORY DIMENSION
Post-SEC settlement in August 2025, XRP is no longer considered a security on public exchanges under U.S. law. This removes a major compliance barrier for U.S.-regulated financial institutions that had been cautious about touching XRP in their payment flows. The Ripple case outcome — a judicial finding that programmatic secondary sales of XRP are not securities transactions — gives compliance officers a clear legal basis for approval.
The inclusion of XRP in the U.S. Strategic Crypto Reserve (March 2025 executive order) provides additional de facto government endorsement. No FBO or money services business is going to face regulatory pressure for using an asset held in a U.S. government reserve.
WHAT INSTITUTIONS ARE ACTUALLY DOING
Ripple has reported over 300 financial institution partnerships globally, with approximately 40% actively using XRP for ODL settlement (not just messaging). SBI Holdings (Japan), Tranglo (Southeast Asia), and FlashFX (Australia) are among the publicly confirmed ODL users.
SBI Remit's corridor from Japan to the Philippines is one of the highest-volume ODL routes, driven by the large Filipino migrant worker population in Japan. Remittance to the Philippines has historically been one of the most expensive major corridors globally — ODL has measurably reduced costs in this corridor.
The trajectory suggests that ODL adoption follows a predictable pattern: high-volume corridors with deep XRP liquidity adopt first, then the liquidity that comes from ODL volume enables expansion to the next tier of corridors in a self-reinforcing loop.
THE MACRO PICTURE
The BIS (Bank for International Settlements) has published multiple working papers on cross-border payment modernization, consistently noting that the pre-funding problem is the central structural inefficiency in the correspondent banking system. Its G20 Cross-Border Payments Roadmap targets reducing costs to below 1% and improving speed to near-instant for all major payment types by 2027.
ODL's architecture is the only production-scale solution that addresses this problem structurally rather than incrementally. Messaging improvements (SWIFT GPI, ISO 20022) don't eliminate pre-funded capital requirements. CBDCs could, in theory, create real-time settlement without pre-funding — but CBDC interoperability infrastructure is still years away from global deployment. ODL is working today, at scale, in 40+ corridors.
The $10 trillion in trapped nostro capital is not a fixed constraint. It's an artifact of a technology limitation that is now being removed.
Build on XRPL Payment Rails
OnrampDLT gives developers and institutions the tools to issue tokens, manage on-chain liquidity, and integrate with XRPL settlement infrastructure.
Explore OnrampDLT →