FedNow is getting a cross-border feature, and three outlets have told that story three ways. Payments Dive wrote about the missing start date, The Paypers wrote about how the model works, and PYMNTS wrote about sanctions screening. Read together, they describe a plan with a clear design and no launch date.
What the Fed has put on the record
The Federal Reserve Board’s April 8 press release invited public comment on a proposal that would let U.S. banks and credit unions use intermediaries to transfer funds through FedNow. The Board gave one example of what that allows: U.S. banks could use FedNow to transact with correspondent banks that handle the international portion of a cross-border payment. The release also states the current limit: “a transfer of funds sent through the FedNow Service can include only two U.S. banks.”
On September 23, Federal Reserve Financial Services followed up with a post on the FedNow website. As Payments Dive quoted it, the service “is on the verge of unlocking a new frontier within the FedNow Service: cross border transaction support.” Those two documents are the primary record. Everything else below is how the trade press read them.
Advertisement
Three accounts of one plan
Payments Dive’s Lynne Marek, writing on September 29 under the headline “FedNow tiptoes into cross-border,” put the open questions first. She wrote that the Fed “stopped short of saying how and when.” The post’s own wording carries a footnote, she noted: any enhancement depends on “Federal Reserve governing bodies,” and a Fed spokesperson declined to say when the Board might vote on the cross-border proposal. Her piece also records that FedNow has drawn upwards of 1,800 banks since its mid-2023 launch, and that feedback on the April proposal from Visa, Wise and Stripe has been largely positive.
The Paypers’ Sinziana Albu, writing on September 28, put the mechanism first. FedNow would process the U.S. domestic leg of a payment, and the international portion would keep moving through established correspondent banking arrangements, the same model the Fedwire Funds Service uses. FedNow would not replace those networks. Participants would choose which cross-border arrangement to pair it with. Albu reports that a group of organisations will test updated FedNow message formats, that all participants can adopt them afterward, and that no date for broader availability has been disclosed. She lists international payroll, corporate payments, property transfers, insurance claims and treasury management as the use cases Federal Reserve Financial Services identified.
PYMNTS covered an earlier stage. Its June 18 piece read the comment letters on the April proposal, and it put compliance first. It reports that banks and fintechs broadly support the proposal but disagree on how quickly operational, sanctions-screening and residency barriers can be addressed. Stripe told the Board the change “closes a consequential gap in U.S. payment infrastructure.” The Clearing House and the Bank Policy Institute backed the goal and asked for a pilot: “During an initial pilot period, depository institutions should have the ability to opt-in to receiving and sending cross-border transactions over FedNow.” They also pointed out that receiving institutions have only seconds to respond to an incoming FedNow message, which leaves little room for a sanctions review.
The accounts agree on the design. All three describe FedNow as the U.S. leg and correspondent banks as the rest. They differ on what is unsettled. Payments Dive treats timing as the open question. The Paypers treats the plan as a first step with early adopters already named, and says further capabilities are expected. PYMNTS treats screening speed and who carries the compliance burden as the open questions. Part of the difference is chronology. PYMNTS wrote before the September post, and the other two wrote after it. The rest is editorial choice about which unanswered question matters most.
The early adopter and what it says
The one company the Fed’s post named is Payall Payment Systems, a Miami Beach firm that supports bank transfers in 130 countries, according to Payments Dive. Its CEO, Gary Palmer, said in the post: “As commerce increasingly demands instant execution across borders, we’re proud to support the infrastructure that makes this possible for our clients and their customers.” The Paypers adds that Palmer’s company points to compliance benefits, including un-nesting complex payments and screening each party in real time. That framing matches the concern PYMNTS surfaced in June. Speed and screening arrive together in that pitch, and both fall to the receiving bank inside the same short window.
The stablecoin route is moving in parallel
Payments Dive tied the FedNow story to a second one. Its FedNow piece says companies are racing to improve cross-border payments as stablecoins open new options, and its October 2 Q&A with Latitude Global CEO Cyril Mathew shows what that race looks like from the stablecoin side. Mathew said the company settles payments in less than two minutes and reaches about 50 countries. He said two or three stablecoins make up 80-plus percent of Latitude’s volume, and he expects the field to narrow: “I do believe it consolidates more, and maybe that’s by vertical.”
The two routes differ in who holds the risk. A FedNow cross-border payment keeps the domestic leg inside a Federal Reserve service and hands the foreign leg to a correspondent bank. A stablecoin payment converts dollars to a token, sends it to a bank partner abroad, and converts again. Our own coverage has followed the stablecoin side closely, including Fiserv’s digital asset platform going live with Roughrider Coin and the plan for banks to test USDC inside their existing payment systems. On the cross-border fintech side, Payments Canada added six members, among them Remitly Canada and Nium.
Our read: a design a bank can plan around, a date it cannot
This section is our analysis, not a finding from any of the three outlets. The through-line across their coverage is that the Fed has settled what FedNow would do and has not settled when. A U.S. bank can now sketch the architecture: FedNow for the domestic leg, an existing correspondent for the rest, a new message format in between. It cannot put a go-live date in a project plan, because the Board vote, the test group’s results and the sanctions-screening question are all unresolved on the public record.
No one in the three accounts claims FedNow will compete head-on with stablecoin rails. Payments Dive puts them side by side as options, and Mathew’s own comments describe pricing converging over five to ten years under clear regulation. That is a timeline longer than any FedNow pilot, which suggests the two approaches will coexist for planning purposes. No source we fetched gives usage or volume figures for FedNow cross-border, so any claim about which route wins would be a guess.
What it means for the finance leader
For a treasurer or head of payments at a company that pays suppliers, staff or claimants abroad, the announcement changes what to ask rather than what to buy. Four questions are worth putting to your bank this quarter.
- Is the bank in the early adopter group that will test the new FedNow message formats, and when does it expect to offer the option to clients?
- Which correspondent arrangement would carry the international leg, and how would it be priced against what you pay today?
- How will the bank screen parties inside the seconds-long response window that The Clearing House and the Bank Policy Institute described?
- If your use case is international payroll or time-sensitive disbursements, which of the use cases Federal Reserve Financial Services named does it match?
If you already use a stablecoin provider for emerging-market payouts, keep that arrangement and add the FedNow answers to your vendor review. Neither route has a published volume record you can benchmark against yet. Check the Board’s announcements for a vote on the Regulation J proposal, and treat that vote as the date that turns this plan into something to schedule.
Source: Federal Reserve Board
