FedNow payee verification: Why recipient checks matter before instant payments settle

FedNow launched in July 2023, giving financial institutions in the United States another way to move money instantly, 24 hours a day, seven days a week.

That speed comes with an important consideration. Once a FedNow payment settles, it is final and irrevocable. This gives businesses and consumers immediate access to funds, but it also makes preventing fraud before a payment is sent particularly important.

For financial institutions developing a FedNow fraud prevention strategy, this puts greater emphasis on controls that can identify potential issues before settlement.

The U.S. Faster Payments Council addressed this challenge in its 2026 guidance on fraud dispute resolution for instant payments. The guidance provides principles for handling fraud and scams after an instant payment has been made. But for financial institutions, there is another important question: how can potentially misdirected or fraudulent payments be identified before the funds move?

This is where pre-payment Payee Verification can play a role.

Why irrevocability makes FedNow fraud disproportionately damaging

Traditional payment methods can provide more time or mechanisms for handling certain types of disputed transactions. Instant payments work differently.

FedNow payments are designed to provide immediate, final settlement. The service supports return requests and payment returns, including in cases involving suspected fraud, but a return request does not reverse the original settled payment automatically. Recovering funds after they have reached the recipient therefore depends on what happens after settlement.

For fraud scenarios such as business email compromise or account detail substitution, this makes the point before payment particularly important. If fraudulent account details are introduced into a genuine payment instruction, controls that identify the issue before the transaction is submitted can help reduce the risk of funds being sent to the wrong recipient.

This challenge is part of a broader shift in the US payments landscape, as faster and real-time payment methods reduce the time available to identify potential fraud before settlement. As instant payment fraud in the US receives greater attention, financial institutions are increasingly looking at how fraud controls can operate earlier in the payment journey.

Where Payee Verification fits

Payee Verification adds a recipient check before a payment is sent.

The check compares the payee information entered for the payment with information associated with the recipient account. If the details do not align, the discrepancy can be surfaced before the payment proceeds, giving the financial institution or payer an opportunity to review the instruction.

This type of payee name verification can be particularly relevant when the payment instruction itself appears legitimate, but the recipient account details have been changed.

Consider a supplier payment where a fraudster has compromised an email account and replaced the supplier's legitimate banking details with their own. The payment itself may otherwise appear genuine. The payer is authorized, the invoice is real, and the transaction amount may be consistent with previous payments.

Payee Verification introduces an additional question: Do the recipient details correspond to the intended payee?

That makes it complementary to controls such as authentication, transaction monitoring, anomaly detection, and email security. Those controls can identify different indicators of fraud, while Payee Verification focuses specifically on the identity of the intended recipient before funds are sent.

Want to strengthen recipient checks before payments are sent?

Learn how IPID's Payee Verification helps financial institutions verify payee details before funds move.

The broader shift toward pre-payment fraud controls

The growth of instant and account-to-account payments is increasing the focus on fraud controls that operate earlier in the payment journey.

In May 2026, the U.S. Faster Payments Council published guidance addressing fraud dispute resolution in instant payment environments, recognizing the challenges created by the irrevocable nature of these payments.

Separately, Nacha's 2026 fraud-monitoring rules expanded risk-based monitoring requirements across the ACH Network. The rules require affected participants to establish processes reasonably intended to identify ACH entries suspected of being unauthorized or authorized under false pretenses.

These Nacha 2026 requirements around payments authorized under false pretenses apply specifically to ACH rather than FedNow. However, together with industry discussions around instant payments, they reflect a broader focus on identifying fraud earlier and strengthening controls across payment journeys.

For financial institutions supporting multiple payment rails, this also creates an operational question: how can recipient verification be incorporated consistently across different payment workflows without creating separate processes for every rail?

What to look for in Payee Verification

For financial institutions considering FedNow payee verification alongside other US payment rails, several factors matter.

Coverage: A verification service is only useful when it can reach the accounts that customers are paying. Financial institutions should understand the breadth of account coverage available and what response is returned when verification cannot be completed.

Match logic: Names are rarely standardized. Business names, trading names, DBAs, abbreviations, punctuation, middle names, and other variations can all affect matching. Effective Payee Verification needs to account for these differences rather than relying only on exact string matching.

Integration: Verification takes place within the payment journey, so the response needs to be fast enough to avoid unnecessary friction for the payer. API-based integration can allow verification to be embedded directly into existing payment workflows.

Clear verification outcomes: Match results should give the financial institution or payer enough information to determine whether to continue, review, or correct a payment without creating excessive false alerts.

Support across payment workflows: Financial institutions increasingly operate across ACH, FedNow, RTP, Fedwire, and cross-border payment flows. Requirements for RTP payee verification and FedNow verification ultimately raise the same broader question: how can recipient checks be incorporated consistently across faster payment journeys? A verification approach that can support multiple payment journeys can help reduce fragmented processes and inconsistent customer experiences.

Adding a recipient check before funds move

Instant payments create significant benefits for businesses and consumers because funds move quickly and become available immediately. That same finality also raises the cost of discovering a recipient problem after settlement.

Payee Verification adds a check at an important point in the payment journey: before the funds are sent.

It does not replace authentication, transaction monitoring, sanctions screening, or other fraud controls. Instead, it adds another layer by helping financial institutions and their customers confirm that the account being paid corresponds to the intended recipient.

As instant payments continue to grow in the United States, that additional recipient check can become an increasingly important part of a layered approach to payment fraud prevention.