The Seam Where Instant Payments Stop Being Instant

FedNow made domestic settlement instant, but cross-border payments still run through correspondent banks, FX conversion queues, and overnight settlement cutoffs in foreign jurisdictions.

Domestically, it works. Over 1,800 banks and credit unions settle transfers in under five seconds, 24 hours a day, with finality guaranteed by the Federal Reserve. Average daily volume hit 55,000 transactions in Q2 2026, growing 80% quarter over quarter.

But dollars that need to become euros, or pesos, or yen, can't stay on those rails. The moment a payment involves a party outside the United States, it leaves the instant system and enters correspondent banking infrastructure that was designed decades before real-time settlement existed.

On April 8, 2026, the Fed proposed changing this. The proposal amends Regulation J so FedNow participants can route payments through intermediaries, including correspondent banks that handle the foreign leg. But FedNow only settles the U.S. portion. Everything past the intermediary still moves on the same correspondent rails it always has.

The handoff

Today, a FedNow transfer involves exactly three parties: a sending bank, a receiving bank, and a Federal Reserve Bank in the middle. The Reserve Bank debits the sender's master account and credits the receiver's master account, with settlement finality, in seconds.

The cross-border proposal adds a fourth party: an intermediary that sits between FedNow and the foreign payment system. The U.S. sending bank initiates a FedNow transfer to the intermediary. FedNow settles that leg, sender to intermediary, in seconds. The intermediary then routes the payment internationally through whatever channel it uses — SWIFT, a bilateral arrangement with a foreign bank, a foreign instant payment system. The Fed doesn't prescribe how.

So the instant portion of the transaction ends at the intermediary. From there, the payment is just another cross-border wire. FX conversion, compliance checks, correspondent routing, and settlement on the foreign system all happen outside FedNow's reach.

The FX window

Because the domestic leg settles instantly and the foreign leg doesn't, the exchange rate can move between the two settlements.

A U.S. company sends $100,000 to a supplier in Frankfurt. FedNow settles the dollar transfer to the correspondent bank in 4 seconds. The correspondent initiates the euro conversion and routes the payment through SEPA or TARGET2. If that leg settles in an hour, the FX exposure is manageable. If it settles overnight because the European system has a cutoff, the rate could shift by 20 or 30 basis points. On $100,000 that's $200 to $300. On a $10 million corporate treasury transfer, it's $20,000 to $30,000.

The BIS estimates that roughly one in three FX transactions globally carry settlement risk. That risk exists because one leg of the trade settles before the other. Making the domestic leg faster doesn't reduce this risk — it widens the gap between the two settlement times.

Under the current proposal, the intermediary bears the exposure. The correspondent bank received dollars with settlement finality. If the euro leg fails or the rate moves, the intermediary is holding dollars and owes euros at a rate it may not have locked. The Fed's proposal says nothing about FX risk allocation between participants.

The compliance checkpoint

Sanctions screening adds latency that instant settlement can't eliminate.

Every cross-border payment must be checked against OFAC's Specially Designated Nationals list before it can proceed. The intermediary, not FedNow, runs this check. A clean OFAC screen against a standard list takes milliseconds. But a fuzzy match, where the beneficiary's name is close to a sanctioned entity, requires human review. That review can take minutes, hours, or days depending on the intermediary's compliance team.

The domestic leg settled in 4 seconds, but the compliance review takes 3 hours and the beneficiary in Frankfurt sees nothing until the review clears.

AML checks layer on top. If the transaction amount, pattern, or destination country triggers the intermediary's transaction monitoring rules, the payment enters a separate queue. The intermediary's AML team reviews it. If they file a Suspicious Activity Report, they can't notify the sender or receiver. The payment sits.

FedNow's speed makes the compliance gap more visible, not smaller. When both legs of a cross-border payment took a day, the compliance review happened in parallel and nobody noticed. Now that the domestic leg takes 4 seconds and the compliance review takes 3 hours, the sender sees an instant debit and no corresponding credit abroad. The experience feels broken even though the process is working as designed.

Reconciliation at the boundary

A comment letter to the Fed's proposal warned about "inconsistent processing outcomes and reconciliation challenges at the boundary between FedNow and intermediary segments."

FedNow uses ISO 20022 messages internally. The early cross-border adopters are testing enhanced message formats that carry additional fields for foreign beneficiary information. But the intermediary's outbound system may use a different message standard, a different character set, or different field mappings. The original remittance information, the "why" of the payment, can be truncated, reformatted, or lost.

A corporate payment includes a reference number in the FedNow message: INV-2026-4471. The intermediary maps it to a SWIFT MT103. The reference field in MT103 has different length limits and allowed characters. The reference arrives at the receiving bank in Frankfurt as INV2026447. The supplier's accounts receivable system can't match it. A human reconciles it manually the next morning.

This is not hypothetical. Remittance data truncation has been the single most common complaint in cross-border payments for decades. SWIFT gpi improved end-to-end tracking, and the migration to ISO 20022 on Fedwire (completed July 2025) aligned message formats. But the seam between FedNow and the correspondent system is a new boundary where data can be lost.

The Fed's proposal asks intermediaries to "pass through" remittance data but doesn't specify how to handle format mismatches, encoding differences, or field-length constraints between FedNow's ISO 20022 and whatever the downstream system uses.

The finality problem

FedNow provides settlement finality. Once the Reserve Bank debits the sender's master account and credits the receiver's, the transfer is irrevocable. No clawbacks, reversals, or conditional holds.

But finality on the domestic leg creates a problem if the foreign leg fails. The sending bank's customer has been debited and the correspondent has received the dollars, so if the correspondent can't complete the foreign payment, because the beneficiary's account is closed, or the receiving bank rejects the payment, or a sanctions screen flags it, the dollars are sitting with the intermediary and the original payment needs to be returned.

FedNow's return process handles domestic returns. Whether and how it handles the return of a cross-border payment that succeeded domestically but failed internationally is not specified in the proposal. The Fed acknowledged that "exception handling and participant responsibilities" need further definition.

In practice, the intermediary would initiate a separate FedNow credit transfer back to the sending bank. But that's a new transaction, not a reversal of the original. The sending bank's reconciliation system sees two entries: a debit and a later credit. The customer sees money leave and then return hours or days later, with no automated link between the two. Corporate treasury teams call this a "payment in limbo" event. It generates support tickets, manual investigation, and occasionally duplicate payments when someone retries before the return arrives.

What conditional settlement would look like

BIS Project Nexus takes a different approach to the same problem. Instead of making one leg instant and leaving the other on traditional rails, Nexus interlinks instant payment systems across countries so both legs settle together.

The design uses conditional settlement. The sending country's instant payment system holds the domestic leg in a pending state. The receiving country's system processes the foreign leg. Both legs settle simultaneously if the foreign leg succeeds, and neither settles if it fails. The target is under 60 seconds end to end.

Founding members are India (UPI), Malaysia (RPP), the Philippines (InstaPay), Singapore (FAST), and Thailand (PromptPay). A separate BIS initiative, Project Rialto, pairs interlinked instant systems with a wholesale CBDC layer for FX conversion, providing payment-versus-payment settlement in central bank money.

Nexus eliminates the FX risk window entirely, because no leg settles before the other. Finality becomes conditional on both legs completing. And because both systems use ISO 20022 end to end, remittance data survives the crossing intact.

It doesn't solve the compliance problem. Sanctions screening still has to happen. But screening happens during the conditional hold, before settlement, not after one leg has already settled with finality. A flagged payment holds both legs, not just one.

The tradeoff is that Nexus requires both countries to have operational instant payment systems and to agree on a shared protocol. FedNow's approach works with any country, because the correspondent bank handles everything on the other side. Nexus is faster and cleaner, but FedNow is more pragmatic and immediately deployable.

Where the seam stays

The Fed's proposal is the right first step. Connecting FedNow to cross-border flows means the U.S. leg of an international payment can settle in seconds instead of hours. For payroll companies, treasury operations, and insurance claim processors, faster access to the domestic settlement rail has real value even if the foreign leg still takes time.

But the seam will stay. The intermediary model means the instant portion of the transaction ends at the U.S. border. FX risk, compliance latency, reconciliation gaps, and finality mismatches all live at the handoff between FedNow and the correspondent system.

The regulatory comment period closed in June 2026. The Fed hasn't published a final rule. Early adopters are testing enhanced ISO 20022 message formats for the U.S. leg. The foreign leg, where most of the engineering complexity lives, remains the correspondent bank's problem — the same one it's been for 50 years, now with a faster clock on the front end.