Domestic instant payments have trained everyone to expect seconds. A transfer inside the same country can clear in under a minute, often around the clock. Then the same payment crosses a border and the experience collapses into hours or days. The immediate scheme did not fail — it simply ended at the frontier, where a different set of mechanisms takes over.

Where domestic immediacy stops

Local instant schemes are, by design, domestic. They settle between accounts at institutions inside one jurisdiction, under one rulebook and one supervisor. The moment a beneficiary sits in another country, the payment must leave that scheme and enter a correspondent relationship, a card network, a stablecoin rail or another local scheme abroad. Each of those has its own timetable.

The result is a gap: fast at both ends, slow in the middle. A payment can be debited instantly at origin and still wait on an intermediary's cut-off before it is credited at destination.

What actually closes the gap

Closing it is less about inventing a faster wire and more about removing the middle. Three mechanisms matter:

  • Netting. Offsetting flows between participants cancel internally, so only the residual amount needs to leave the network.
  • Local payout. Paying the beneficiary in their own currency on their own scheme avoids an extra conversion and an extra hop.
  • Routing across rails. Choosing, per payment, among hub participants, local instant schemes, card networks and other paths by cost, time, reliability and regulatory fit.

None of these requires a beneficiary to know which rail was used. The client stays the client of their own institution.

Why this is architectural

The open question is not which single rail wins. It is which layer connects the rails so that a domestic-grade experience can be assembled from several of them. That is a protocol problem: who governs it, how participants trust one another, and how compliance is handled once rather than everywhere.

In short

  • Domestic schemes stop at the border; the delay is in the middle, not the ends.
  • Speed at origin does not guarantee speed at destination.
  • Netting removes the need to move the full amount.
  • Local payout avoids an extra conversion and hop.
  • Per-payment routing across rails is what makes seconds possible.

See how these layers are structured at /protocol/.