Two payments of the same size, sent an hour apart, can cost different amounts and arrive on different days. Cross-border payment economics are shaped by the clock: cut-off windows, scheme hours and settlement cycles decide whether money moves now or waits until tomorrow — and sometimes until Monday.
Why the hour matters
Each rail keeps its own hours. A local instant scheme may run continuously; a correspondent chain may close in the early afternoon of the sending currency; a card network settles on its own cycle. When a payment misses a window, it does not simply slow down — it may fall to the next business day, tying up liquidity in the meantime. Across several time zones, the windows overlap in ways that are easy to misjudge by hand.
Routing around the clock
Intelligent routing treats timing as a first-class criterion, alongside cost, reliability and regulatory fit. For a given payment, it compares the paths actually available at that moment — hub participants, card networks, local instant payments, SWIFT, stablecoins, agent protocols — and picks the one that best balances arrival time against price. Where offsetting flows can be settled internally, the question of windows may not arise at all, because the money never has to leave.
Designing for cut-offs
Treasury can plan around windows rather than discover them. Note the cut-off of every corridor you use, and the days it does not operate. Keep a small buffer aligned to the widest gap in your schedule. And where an operation crosses a limit or a window, treat it as a human decision: limits and thresholds sit below the model, and over-limit operations become approval requests rather than rejections.
In short
- Timing, not just price, decides when a payment lands.
- A missed cut-off can push settlement to the next business day.
- Routing weighs arrival time against cost and reliability.
- Internal netting can remove the window question entirely.
See how routing handles timing → /protocol/