The Biggest Problem in Cross-Border Payments Isn’t Speed - It’s Uncertainty

Last week we asked whether faster is actually better, and landed on a more useful question: how fast can a payment arrive and still be one a bank is confident should have been sent? That’s the first G20 goal, speed, done right. This week we move to the second, and it’s the one customers feel every time they send money abroad, regardless of how quickly it actually settles: where is it, right now?

“Where is my payment?”

It’s the most common cross-border support question there is, and for years banks have had no good answer to give in the moment. A payment leaves an account and then disappears into the correspondent network. The customer waits, unable to see anything until it either arrives or bounces back with no or limited explanation of what went wrong or when.

That experience gap is jarring because customers already know what good tracking looks like. A €10 parcel gets a live map and a two-hour delivery window. A €10,000 wire gets a debit confirmation and silence. Swift’s gpi network solved the underlying data problem years ago; payment status genuinely is trackable end-to-end. But knowing something is trackable in the correspondent network and a customer being able to see it themselves in their banking app are two different things. For a lot of banks, that front-end gap is still open. Plenty of cross-border payments also still move outside gpi-participating rails altogether, where even the back-office visibility isn’t there yet.

Why this matters for banks

Every “where is my payment” call is expensive in a way that’s easy to underestimate. It’s not just handling time. It’s a manual back-and-forth between the bank’s ops team and a correspondent bank to chase down a status the system already knows, relayed to a customer who’s now had two touchpoints of friction on a single payment. Do that at volume and it becomes a real, recurring cost line, not an occasional service exception.

It also compounds the trust problem we’ve been building toward all series. A customer who can’t see their payment moving assumes the worst, that it’s stuck, misdirected, or gone, well before there’s any evidence that it is. Visibility isn’t just a service nicety; it’s what keeps a normal, on-time payment from feeling like a crisis in progress. Regulators are pushing in the same direction as customer expectation: the EU’s broader PSR/PSD3 agenda treat predictable, visible cross-border payments as the standard banks are expected to reach, not a differentiator some banks might offer.

What transparency actually requires

A settlement confirmation email isn’t transparency. Transparency is a customer being able to open their banking app mid-transfer and see where the payment is in its route, what’s happened so far, and roughly when it’ll land, the same shape of information a parcel-tracking page gives, updated as the payment actually moves rather than reconstructed after the fact from a phone call.

That bar doesn’t get cleared by tracking data existing somewhere in the correspondent chain. It gets cleared when that data reaches the customer’s own screen, inside the channel they already use, without them having to ask.

Our view

This is the gap we built Payment Tracking to close. It combines Swift’s GPI APIs with the Swift Front-end Tracker API and SwiftRef to deliver a unified, real time tracking experience, regardless of a bank's GPI readiness or the readiness of each individual branch. Instead of fragmented visibility, banks get a single, consistent view across all payments. It drops into a bank’s existing channels as a UI Rendering API or a ready-built widget, status language and branding matched to the bank, so it reads as the bank’s own feature rather than a bolted-on tracker. Because it sits next to Exceptions & Investigations, a customer who spots something that actually looks wrong can raise a case from the same screen instead of picking up the phone.

The question to sit with

Speed and transparency aren’t competing priorities. The G20 is asking for both from every bank, and neither substitutes for the other. Of the two, though, transparency is the one a bank can improve without touching a single settlement rail. The infrastructure to know where a payment is already exists in most cases. The only question is whether that answer reaches the customer before they have to call and ask for it.

Next in this series: speed and transparency both cost money to get right, but so does not getting them right. Next week: what cross-border payments really cost, and who’s actually paying for it.