Domestic payments settle in seconds. Cross-border payments still settle in days. The gap is no longer a technology problem  it’s an engineering backlog. Here’s what closing it actually takes.

Somewhere in your bank, a customer just sent a domestic payment that settled before they closed the app. The same customer’s cross-border payment possibly initiated the same afternoon is now moving through a chain of correspondent banks, batch cutoffs, sanctions queues and nostro accounts, and will arrive in one to three business days, minus fees that nobody can fully itemize in advance.

That contrast is the defining customer-experience gap in payments today. And it’s now a measured one: the G20 set explicit targets for cross-border payments on speed, cost, transparency and access most of which are set for end-2027 and the industry reports its progress against them every year.

The message is instant. The money isn’t.

A cross-border payment today can carry beautifully structured ISO 20022 data and still crawl, because speed is set by the slowest link in a chain the sender doesn’t control:

• Correspondent hops. Each intermediary bank adds processing time, a compliance check, a fee and a potential exception. The message format changed; the chain didn’t.
• Batch thinking in a streaming world. Many banks still process cross-border flows in batch windows cutoffs, end-of-day runs, next-morning repairs while their domestic rails run 24×7.
• Sanctions and compliance friction. Screening every hop, often with poorly structured legacy data, generates false positives that stall payments for hours or days. Ironically, the structured party and address data CBPR+ mandates is exactly what reduces those false positives for banks whose screening engines actually use it.
• Nostro liquidity. Money can only move as fast as the funding behind it. Pre-positioning liquidity across correspondent accounts, with only end-of-day visibility, forces a choice between trapped capital and failed payments.
• Opaque tracking. When a payment stalls, finding where still too often means emails between operations teams despite the tracking infrastructure now available end-to-end.

None of these is a standards problem. Every one of them is an engineering problem.

What “engineered for real-time” actually looks like

Banks closing the gap are converging on a recognizable architecture:

1. Event-driven payment processing – Every payment is a stream of events initiated, screened, funded, sent, confirmed that downstream systems react to in real time. Exceptions surface in seconds, not at the end-of-day run. This is the single largest departure from batch-era cross-border architecture, and it’s the foundation everything else sits on.

2. ISO 20022 as data, not payload –The structured fields in CBPR+ messages precise party data, purpose codes, remittance information should feed screening engines, reconciliation matching, liquidity forecasting and client reporting directly. Banks that truncate, flatten or ignore this data in transit are running a real-time message format at batch-era intelligence.

3. Screening built for structure – Sanctions and AML screening tuned to structured party and address data produces dramatically fewer false positives than name-scanning free-text fields. Fewer false positives means fewer stalled payments, smaller investigation queues and faster corridors compliance and speed improving together, which batch-era intuition says is impossible.

4. Real-time nostro visibility – Intraday increasingly continuous awareness of correspondent account positions, with forecasting that lets treasury fund corridors just-in-time instead of parking buffers everywhere. This is where faster payments stop being a cost (more liquidity pressure) and start being a strategy (less trapped capital).

5. Exception automation. At real-time speed, the repair queue is the customer experience. Auto-triage, data-enriched investigations and standardized repair workflows keep the exception tail from swallowing the speed gains everywhere else.

6. Observability end-to-end. Corridor-level dashboards, per-payment tracing and SLA alerting. If your operations team learns about a stuck corridor from a client email, the architecture isn’t done.

The strategic point: speed is a byproduct

Here’s what the banks leading on this have figured out: engineering for real-time cross-border isn’t really about speed. Speed is the visible result. The underlying assets are structured data flowing through automated operations with continuous liquidity intelligence and those assets pay out in ways that show up on the P&L well before every corridor hits the G20 targets:

• Lower cost per payment (fewer manual touches, fewer investigations)
• Lower trapped liquidity (just-in-time nostro funding)
• Lower compliance cost (fewer false positives, automated evidence)
• New revenue (corporate clients will pay for speed, certainty and visibility — and the data products that come with them)

That’s also why “wait for the network to get faster” is a losing strategy. The banks that engineered their own side of the chain are the ones positioned to win corridors, correspondent relationships and corporate mandates as the network catches up and the ones for whom every incremental network improvement translates directly into product advantage.

Where to start

The honest starting point is a diagnostic, not a program: map your corridors against four questions. Where do payments actually stall network, compliance, funding or operations? How much of your CBPR+ data survives end-to-end? What does a false positive cost you, and how many are structured-data-preventable? And what is your real intraday nostro position not the report, the reality?

The answers usually surprise banks, and they turn a vague “we should modernize cross-border” into a sequenced engineering roadmap with a business case attached.

Altimetrik engineers cross-border payment modernization end-to-end event-driven payment platforms, ISO 20022-native data enablement, sanctions-screening optimization, nostro liquidity intelligence and exception automation, built on delivery experience across 80+ payments programs. Our free 2-week CBPR+ Diagnostic maps exactly where your corridors lose time and money. 

Author:

Vibhanshu Sharma

Senior Client Partner –  Business Development