Why an Instant International Transfer Needs Money Waiting Abroad

The speed sits in a funded local account

A provider promising rapid pounds-to-pesos delivery cannot wait for every wholesale currency trade and cross-border settlement to finish before paying the family. It keeps pesos in a destination account or funds a payout partner. When the customer's pounds arrive, the local pool releases the matching amount.

This is prefunding. The money sits ready before a particular customer appears. It reduces the chance that a payment stalls for lack of settlement cash, and it lets the final bank leg use domestic infrastructure. The cost is the return forgone on idle balances and the operational effort of maintaining accounts across markets.

The buffer is never just one average day. Weekends, paydays and holidays change demand. A sudden migration payment or business batch can drain a pool. Treasury teams model those patterns and leave a safety margin. Too little liquidity breaks the service; too much turns working capital into expensive furniture.

Two-way customer flow saves treasury work

Suppose customers send £1 million to India while other customers move the equivalent of £400,000 back to Britain. The provider does not need to replace the full outward amount wholesale. It can offset the opposing flows and rebalance the net £600,000, subject to its legal entities and account structure.

When opposing flows cancel out, less money needs settling. The provider can trade a smaller FX amount and send fewer wholesale transfers. That makes a corridor with useful two-way traffic attractive. A heavily one-directional remittance route keeps draining the destination pool, forcing more frequent funding and a larger buffer against disruption.

Timing can make an apparently balanced corridor unhelpful. Business receipts may arrive on weekdays while families send money on Sunday evening. The totals offset over a month, yet the payout account can still run short at the exact moment ordinary customers need it. Useful netting depends on compatible currencies, legal entities and settlement windows, not only matching numbers in a spreadsheet.

The customer does not normally see that imbalance as a separate line item. It can appear inside the FX margin or available route. This is one reason a provider prices the same currency differently depending on where the beneficiary account sits. Currency is only half the problem; liquidity has a location.

Nostro balances buy certainty and tie up cash

Banks have long held foreign-currency balances with correspondents. The home bank calls its overseas account a nostro; the bank holding it views the same balance as a vostro. Those funds make payments possible where the sender lacks direct settlement access. The cash ends up scattered between banks just when one timezone closes and another opens.

BIS research describes the trade-off plainly. Prefunding reduces delays and failures but creates idle buffer costs or credit exposure elsewhere. A provider must also consider the bank holding the balance, limits on withdrawing currency and what happens when markets close while retail payments continue.

Foreign exchange adds settlement risk. One party can deliver the sold currency before receiving the bought one. Payment-versus-payment arrangements make both legs conditional on each other. The 2025 BIS survey still found that only 36% of average daily FX settlement used PvP to eliminate that risk, evidence that the old timing problem remains large.

New rails still need money at the far end

Project Nexus proposes linking domestic instant-payment systems with standard messages and competing FX providers. Its technical design requires those providers to hold sufficient balances in the systems where they quote. Instant connectivity does not remove prefunding; it makes liquidity monitoring more immediate and exposes a provider that quotes without enough money.

Project Rialto tested a more ambitious design combining automated FX with payment-versus-payment settlement in tokenised central-bank money. The experiment addressed FX and settlement friction, including routes that need a third vehicle currency. It is a proof of concept, not a retail network that has replaced today's accounts.

For customers, the lesson is practical. An instant badge describes the expected retail experience under normal liquidity and screening conditions. Before trusting it, ask two blunt questions: is the delivery time guaranteed, and who fixes a failed payout? For industry buyers, ask how balances are forecast, where funds sit and how weekend shortfalls are covered. The attractive API call is merely the last inch of a very liquid machine.