TL;DR
- On April 10, 2026, the Federal Reserve proposed amending Regulation J to let FedNow participants route transfers through intermediary banks, including non-U.S. correspondent banks, extending real-time settlement to the U.S. leg of cross-border payments for the first time.
- On August 10, 2026, Stripe, Visa, Wise and a coalition of banking and fintech trade groups formally backed the proposal after the comment period closed June 9. The Fed has not set a timeline for a final rule, and the RTP Network is separately rolling out its own foreign-leg rule later in 2026.
- The change only fixes settlement speed on the domestic leg. It does nothing for authorization, where a cross-border card transaction still clears at lower approval odds than one processed locally, which is the problem orchestration and local-market infrastructure actually address.
What happened
FedNow, the Federal Reserve’s real-time payment rail, launched in mid-2023 and now counts more than 1,800 participating banks and credit unions, covering roughly half of U.S. checking and savings accounts. Its scope has stayed strictly domestic: a transfer can only move between two U.S. financial institutions.
On April 10, 2026, the Fed published a proposal to amend Regulation J, the rule governing Fedwire and FedNow funds transfers, to let participants route payments through intermediaries other than Federal Reserve Banks, including non-U.S. correspondent banks, letting a FedNow transaction settle the U.S. leg of a cross-border payment in real time instead of waiting on traditional correspondent banking.
The comment period closed June 9, 2026, drawing 37 broadly supportive submissions. On August 10, 2026, a coalition formally backed the change: Stripe, Visa, Wise, the American Fintech Council, the U.S. Faster Payments Council, the Financial Technology Association, the Electronic Transactions Association, Nacha, The Clearing House and the Bank Policy Institute. Stripe’s Jonah Crane called it “sound policy,” arguing “the Board has a direct and legitimate interest in ensuring that its own payment systems keep pace.” Visa’s Andrew Neeson said it would give “payment providers additional choice with how and where they can route payments reliably, efficiently and more cost effectively.” A Fed spokesperson has not given a timeline for a final rule.
The push isn’t confined to FedNow. The RTP Network, operated by The Clearing House, is separately implementing a rule change that would let one leg of a transaction involve a foreign bank, with rollout planned later in 2026, described as a phased buildout rather than a single cutover.
That pace reflects a real constraint. Irene Skrynova, CEO of Global Payments at the fintech Unlimit, told American Banker that real-time cross-border settlement changes what treasury teams have to do: “In the old model, you had overnight to fund a payment. In a world of connected instant systems, you don’t. Money has to be in the right place, in the right currency, around the clock. Treasury teams have to rebuild around that.”
Why this is a settlement fix, not an approval fix
Every cross-border card payment carries two separate frictions. The first happens at authorization: the issuing bank decides, in real time, whether to approve or decline the transaction, and issuers historically approve cross-border authorizations, where the card was issued in a different country than the transaction is processed in, at lower rates than domestically processed ones. The second happens at settlement: moving the approved funds from the acquiring side back to the merchant, often through a correspondent bank, an intermediary bank that handles cross-border transfers for banks that lack a direct relationship. Correspondent banking is reliable but slow, especially outside business hours, when a payment can sit until the next banking day.
The Fed’s Regulation J proposal, and the RTP Network’s parallel move, address the second friction only. They let a U.S. bank route the domestic leg of a cross-border payment through an intermediary or foreign correspondent bank on a real-time rail, a genuine improvement for cash flow and reconciliation timing.
They do nothing for the first friction. A subscription renewal from a customer whose card was issued by a bank in, say, Singapore or Brazil still gets scored and authorized as a cross-border transaction before any settlement rail touches it. For a subscription business, that distinction matters: a decline at authorization kills the renewal outright, while a delay at settlement just means the merchant’s own cash arrives a day later. One is a churn event. The other is a treasury inconvenience.
How orchestration architecture addresses this
Processing transactions locally, rather than making cross-border transactions faster, changes the outcome. SGW Payment’s role as the payments infrastructure layer for international expansion means that when a client enters a new market, SGW stands up the local setup on the client’s behalf: incorporating entities where required, opening banking and acquiring relationships, negotiating PSP contracts in the jurisdiction, and running the downstream finance operations, reconciliation, cash flow, reporting and local tax clearance, in every jurisdiction it processes in.
A renewal from a customer in a given market then gets authorized and processed inside that market, not across a border at all. There is no correspondent bank in the authorization path and no cross-border scoring penalty to work around, because the transaction was never cross-border. That local-processing effect lifts issuer approval rates on its own, and compounds with SGW’s routing layer, which connects clients to a network of payment providers and sends each transaction to the provider most likely to approve it, for top-of-market success rates across a client’s footprint.
For a business weighing whether to build this itself, the relevant benchmark is time: standing up local entities, banking, acquiring and finance operations in a new market from scratch typically takes 6 to 12 months, which orchestration compresses by handling the setup on the client’s behalf. That matters most for exactly the businesses Reg J’s supporters want to help: recurring or high-volume operations expanding into new geographies.
To be precise about scope: SGW does not operate a payment rail, is not a party to the Regulation J rulemaking, and this article claims no specific SGW approval-rate percentage, only the qualitative claims already documented about SGW’s model.
Takeaways you can act on this quarter
- Separate authorization risk from settlement delay in how you track cross-border cost. They are two different problems, and Reg J only fixes one of them.
- Don’t wait on Reg J to solve declines. Even after a final rule, faster settlement will not change how an issuer scores a cross-border authorization.
- If real-time cross-border settlement lands, check your treasury operations can support it. Instant rails require 24/7 currency positioning that overnight batch settlement never demanded.
- If you’re expanding into a new market, price the local-processing timeline against staying cross-border. Standing up local banking and acquiring from scratch typically takes 6 to 12 months.
Sources
- FedNow extension wins support (Payments Dive, August 10, 2026)
- What RTP and FedNow rule changes mean for cross-border payments (American Banker, August 10, 2026)
- FedNow Cross-Border Plan Tests Real-Time Payments Infrastructure (PYMNTS, 2026)
- Collection of Checks and Other Items by Federal Reserve Banks and Funds Transfers Through the Fedwire Funds Service and the FedNow Service; Regulation J (Federal Register, April 10, 2026)
About SGW Payment. SGW Payment helps online businesses capture more revenue and reduce processing costs. Through a single SDK and API, SGW connects merchants to a network of payment providers and routes each transaction to the provider most likely to approve it. On top of the technology, SGW acts as the payments infrastructure layer for international expansion, standing up the local payments stack (entity, banking, and finance operations) in every new market, so transactions process locally rather than cross-border. Learn more at sgw-payment.com.
