Executive Summary

Domestic instant payment systems have raised the bar for speed and convenience. But when money crosses borders, the experience often slips. The reason is simple: when two countries connect, the overall experience usually falls to the lowest common denominator—the weaker system’s limits on speed, transparency, or customer support.

Global initiatives such as the BIS Nexus project are attempting to solve this problem by creating common rules, APIs, and standards across multiple countries. But whether through Nexus, bilateral links, or commercial networks, the challenge for providers remains the same: how to design a user experience that isn’t dragged down by the weakest link.

The Weakest-Link Problem

Imagine two corridors: one country with a modern, ISO 20022-based instant payment system, and another with legacy rails, limited proxy addressing, and inconsistent dispute resolution. When the two connect, the ‘modern’ side is forced to slow down and simplify to match the weaker one. This weakest-link effect erodes user trust and undermines the promise of ‘instant and transparent’ cross-border payments.

Nexus, and similar projects around the world, aim to harmonize standards so users don’t notice these differences. But until that vision is fully realized, providers must actively design solutions that smooth over these inconsistencies.

Pain Points from the End-User’s Lens

1. User Experience (UX)
For most customers, sending money abroad is stressful. They often don’t know the exact cost or how much the recipient will actually get. Exchange rates shift, fees are unclear, and charges sometimes appear ‘in-flight’ during the transfer. Worse, many users worry whether the money will land in the right account at all. Status updates are patchy—was the payment successful, or is it ‘stuck in review’?

2. Options and Flexibility
Payment addressing is inconsistent. In some countries, a phone number works; in others, users need an IBAN, a national account number, or a proxy ID. Customers may want to specify either “I want to send $500” or “I want my recipient to receive exactly €500,” but not all systems allow this choice. Even basic features like pull requests or merchant payments are not consistently available across borders.

The IBAN vs. non-IBAN problem illustrates this clearly. In Europe, an IBAN is mandatory. But in other regions, users only have local account numbers, bank codes, or even proxy identifiers like a phone number. When such corridors connect, the stronger system cannot enforce IBAN without confusing or excluding users on the other side.

The result is sender frustration (“Why am I being asked for an IBAN when my relative in India doesn’t even know what that is?”), higher transaction failure rates, and hesitation to complete payments.

A better model is a country-aware interface: when the destination is Europe, the app requests an IBAN; when the destination is elsewhere, it asks only for identifiers that are valid there. Behind the scenes, APIs and resolution services can handle the translation so the experience remains simple and trustworthy for the user.

3. Bank Support
Not all banks can offer the same level of cross-border service. Smaller players often lack the technical or operational capacity to deliver instant payments at parity with larger ones. Fees and margins are also opaque: users rarely know which party takes what cut. And when disputes arise, processes differ widely by country, forcing customers to chase multiple parties to resolve an issue.

The Future Users Expect

Providers can deliver a better cross-border experience by building solutions that smooth over the weakest-link effect, rather than being limited by it or letting it dictate the journey. That means setting clear expectations, transparent pricing, and consistent support regardless of which two systems are talking to each other.

  • Users should always see, before they send, the total cost, the exchange rate applied, and the exact amount the recipient will receive.
  • Addressing should be country-aware: the system only shows the valid options for that corridor, whether it’s a proxy ID, phone number, or account number.
  • Status updates should be honest and timely—either ‘payment successful within 60 seconds’ or ‘payment under compliance review,’ with an estimated resolution timeline.
  • Disputes should be managed through a common portal with agreed timelines, instead of ad-hoc processes across banks and countries.

Business Solution: Turning Weakness into Advantage

A smooth user experience is not just a design goal—it’s a business opportunity. Providers who eliminate cross-border friction can capture trust, loyalty, and volume in a crowded market. Three areas stand out:

1. Premium Cross-Border UX

Banks can create a premium service tier that guarantees upfront transparency: all fees, FX rates, and the exact credit amount shown before sending. This matches customer expectations shaped by domestic instant payments. Customers will pay—or switch providers—for this peace of mind.

2. Smart Choice and Flexibility

A Choice Engine allows users to enter either the send amount or the receive amount, with the FX quote adjusting in real time. Addressing should be dynamic: the app only shows the addressing methods valid for that corridor, whether it’s a phone number, proxy ID, IBAN, or local account number. This removes confusion and builds confidence.

3. Consistent Support and Trust

Commercial models should eliminate hidden in-flight deductions by intermediaries. Destination PSP fees and FX margins should be disclosed upfront. Disputes and complaints can be managed through a common portal with agreed timelines—exactly the kind of standardization Nexus is aiming for. The payoff: lower operational friction and higher customer satisfaction.

Technical Solution: Building for Consistency across Borders

Delivering this experience requires a robust technical stack that bridges mismatched domestic systems without exposing the gaps to the customer. Some of the key enablers include:

1. API Gateways with ISO 20022 Support

Standardized APIs can be used to handle payment initiation (pacs.008) and proxy resolution (acmt.023). These ensure that addressing (phone number, proxy ID, IBAN) is translated correctly across systems. When one IPS still runs on legacy ISO 8583, middleware can normalize data to avoid information loss.

2. FX Quote and Transparency Service

An FX integration layer connects to multiple FX providers (FXPs) via API to fetch real-time quotes. Quotes are locked with a short validity window, and if a user changes the send/receive amount, the quote refreshes instantly. Apps should display either the effective exchange rate or “rate after fees”, as per rules of cross-border enablers like Nexus, so there are no surprises.

3. Smart Addressing and Name Check

A smart addressing engine ensures that users only see the fields valid for the destination corridor—such as an IBAN in Europe, a mobile number in Asia, or a bank account plus code elsewhere. If a user enters a proxy like a phone number, the system resolves it to the correct account using proxy resolution APIs.

To reduce errors, the system provides a masked name confirmation before the payment is sent, helping the sender verify the recipient while meeting data protection rules. From the user’s perspective, they simply enter what they know—the system handles the translation and complexity behind the scenes.

4. Real-Time Status and Exception Handling

A status orchestrator provides consistent, corridor-independent updates: “submitted,” “credited,” or “under compliance review.” If the payment is held, users see the reason and the expected resolution timeline—reducing anxiety and calls to support.

5. Fraud and Risk Controls

Mandatory multi-factor authentication, proxy lookup rate-limiting, and pre-transaction risk scoring can reduce fraud. Over time, these controls can be extended to network-level fraud intelligence, where data is shared across corridors.

6. Dispute and Case Management

All disputes should be integrated into a single case-management layer that connects to the Nexus Dispute Portal (or equivalent). Evidence capture, SLA timers, and ISO 20022-based message exchange ensure consistent treatment across countries.

7. Policy Guardrails

Business logic must automatically apply corridor-specific constraints—such as value caps, currency restrictions, or unsupported features (e.g., P2M or pull payments)—so that users don’t run into silent failures.

Conclusion

Cross-border payments will always reflect the differences between domestic systems. Initiatives like BIS Nexus are an important step toward greater harmonization, but the real differentiator will be how providers design around today’s weakest-link effect.

Adding the level of business and technical rigor outlined above makes it possible to deliver on global policy goals such as the G20 roadmap and the UN Sustainable Development Goal of reducing remittance costs below 3%: fast, cheap, transparent, and inclusive cross-border payments. More importantly, it positions providers as leaders who don’t wait for all systems to modernize but design around weaknesses today to give customers the experience they expect. By anticipating the gaps—whether in transparency, choice, or support—and delivering a consistent, customer-first experience, financial institutions can win trust while aligning with global policy.

The winners will be those who move first, creating cross-border journeys that feel as smooth and predictable as a domestic instant payment.