A Faster Rail Still Needs a Border Crossing
The clock, the access path and the domestic rail are three different parts of a cross-border payment, and their interaction gives us a more useful judgment than any one speed claim. The practical task is to diagnose where a payment can wait, who must carry it onward, and whether a genuine connection exists between jurisdictions. Once those questions are separated, “instant” becomes a condition to test rather than a label to trust.
This checkpoint is not a catalogue of the mechanisms already introduced. It brings them into one path. A domestic FPS can process an instruction quickly. An RTGS system may not yet be open. A bank or payment provider may not qualify for direct access. An intermediary may be available, but only for a specific responsibility. And even when the timing and participants line up, the domestic rail still needs an arrangement that can carry the payment across the border. The point is to see how one missing condition can dominate the whole result.
Read the path, not the timestamp
Start with the moment a payer presses “send.” The sending PSP may accept the instruction and pass it to a domestic fast payment system. That is a meaningful event: the domestic rail has done its job. But it is not yet enough to conclude that the cross-border payment is complete. The instruction must still reach the institutions responsible for the other side, and the relevant settlement obligations must be processed under their operating conditions.
The first diagnostic question is whether the necessary systems are open at the same time. If the next settlement system is closed, the payment can wait even though the sending FPS is available. If it is open, the second question is whether the relevant participant has the right kind of access. A receiving institution may be reachable only through a direct participant. A foreign bank or non-bank PSP may have technical access without its own settlement account, or no access at all. Each variation changes the route and the responsibilities along it.
Only after those two questions can we ask about the border connection itself. A payment system that can process domestic transactions is not automatically able to process cross-border transactions. In the 2025 CPMI survey, 47% of the reported FPS and 48% of the RTGS systems were described as capable of processing cross-border payments. Even among those systems, restrictions remained, including limits on outbound initiation and on converting inbound messages into domestic formats. The survey figures do not measure every payment or every customer experience, but they make the diagnostic point clear: a fast domestic rail does not imply a usable international route.
The flowchart is a diagnostic, not a promise. “Potential end-to-end completion” still leaves room for data checks, legal requirements and receiving-side actions that will be developed later. But it prevents a common error: treating a successful first step as evidence that every later gate has already been passed.
The three gates also create different explanations for the same visible symptom: a payment that has not arrived. If the domestic rail is not configured for cross-border processing, the payment has made progress locally but has no international route. If the route exists but the settlement system is closed, the cause is timing. If the system is open but the sending or receiving institution cannot participate in the required way, the cause is access. A customer may experience all three as “slow,” but the remedy for each is different.
A fourth case is possible. The systems may be open, the institutions may be eligible, and a cross-border route may exist, yet an intermediary may still be needed for a particular responsibility. That is not the same as a blocked payment.