What is payee verification? A guide for US payment and finance teams

Payee verification is a pre-payment check that confirms whether the name on a payment instruction matches the owner of the destination bank account. It helps banks, fintechs, and businesses identify incorrect or manipulated payment details before funds are sent.

For US payment teams, that distinction matters. A routing number and account number can be valid while still belonging to someone other than the intended recipient. This is the gap exploited in fraud such as Business Email Compromise (BEC), where legitimate payment instructions can be replaced with an attacker-controlled account. According to the FBI's Internet Crime Complaint Center, BEC accounted for approximately $3 billion in reported losses in 2025.

As payments move through ACH, FedNow, RTP, and cross-border networks, payee verification adds a check at the point where there is still time to act: before the payment is sent.

What does payee verification mean?

In simple terms, payee verification checks whether you are paying who you think you are paying. It is different from simply checking whether a bank account exists. An account can be open, active, and capable of receiving money while belonging to a different person or business from the one named in the payment instruction.

Payee verification checks the relationship between the account details and the account owner. Depending on the service and available data, the result can indicate a match, a close or partial match, or a mismatch before the payer proceeds.

Know Your Payee (KYP) provides a broader framework for this control. While Know Your Customer (KYC) establishes who an institution is serving or sending money on behalf of, KYP addresses the other side of the transaction: who will receive the payment.

How does payee verification work in the US?

A payee verification check takes place during payment preparation, before the transaction is submitted to the payment rail. For a US bank payment, information such as the recipient's name, account number, and routing number can be sent to a verification service, which checks those details against available bank, account, or network data.

The result typically falls into three categories:

• Match: The recipient name and account details correspond.

• Close or partial match: The details are similar but may require correction or review.

• Mismatch: The account does not correspond to the named recipient.

The result can then feed into a bank, fintech, treasury, accounts payable, or payment-provider workflow. A matching payment can proceed, while a close match or mismatch can prompt additional review before funds leave the sender's control.

The key is timing. Rather than discovering incorrect recipient details after a rejection, dispute, or fraud investigation, payment teams have an opportunity to act before the transaction is submitted.

What is the difference between payee verification and account validation?

Account validation can include different checks depending on the provider. At its most basic, an account existence check confirms whether a bank account exists and can receive funds, while payee verification checks whether that account belongs to the person or business the payer intends to pay.

That distinction matters because a fraudulent payment can be directed to a perfectly valid account. The problem is not that the account does not exist, but that it belongs to someone other than the intended supplier, customer, employee, or beneficiary.

Payee verification is also separate from payer authentication. Multi-factor authentication, biometrics, and one-time passwords can establish that the person initiating a transaction is authorized to do so, but they do not establish who owns the destination account. Authentication helps confirm who is sending, while payee verification helps confirm who is receiving.

What types of payment fraud can payee verification help prevent?

One of the clearest US use cases is Business Email Compromise. The FBI describes BEC as a scam in which criminals compromise or impersonate trusted business communications to facilitate fraudulent transfers. A common scenario is a payment request that appears to come from a legitimate supplier but contains replacement bank details controlled by the attacker.

Payee verification introduces another checkpoint. Even if the invoice, email, or payment request looks legitimate, the payment team can check whether the destination account actually belongs to the supplier named in the instruction.

The same principle applies to invoice and vendor payment redirection, where bank details are changed in an invoice, email thread, or vendor master record. Payee verification can also help in some authorized payment scams, where a customer or employee genuinely initiates a transfer after being deceived about the recipient. It cannot prevent the social engineering itself, but a mismatch can provide an additional warning before funds are released.

Not every mismatch is fraud. Incorrect account details, outdated records, and manual data-entry errors can also send payments in the wrong direction. This means the same verification step can support both fraud prevention and payment accuracy.

Is payee verification required in the US?

The US does not currently have a nationwide equivalent to the UK's Confirmation of Payee or the EU's Verification of Payee that requires payment providers to perform a standardized name-to-account check.

However, US payment rules and industry initiatives are placing greater emphasis on identifying fraud across account-to-account payments. Nacha's fraud-monitoring rules expanded significantly in 2026, requiring covered participants in the ACH Network to establish risk-based processes and procedures reasonably intended to identify entries suspected of being unauthorized or authorized under false pretenses.

Nacha defines false pretenses to include cases where a person misrepresents their identity, authority to act for another person, or ownership of the account being credited. The definition captures scenarios such as Business Email Compromise, vendor impersonation, payroll impersonation, and other forms of payee impersonation.

The rules do not mandate payee verification as a specific control or prescribe a particular fraud-monitoring method. Instead, institutions determine the processes appropriate to their risk-based approach. Payee verification can complement these processes by checking account ownership before payment.

Instant payments create a related challenge. In May 2026, the U.S. Faster Payments Council published 11 guiding principles for fraud dispute resolution in instant payments. The guidance is directional rather than regulatory, but it reflects the difficulty of responding to fraud once money has moved through an irrevocable payment environment.

This makes prevention and post-payment response complementary. Dispute processes address what happens after a fraudulent payment occurs, while payee verification creates an opportunity to identify a problem before the payment is sent.

How does payee verification work across ACH, FedNow, and RTP?

US payment teams operate across multiple rails, from ACH to instant payments through FedNow and RTP. Each has different operating characteristics, but the recipient-verification question is the same: does this account belong to the person or business we intend to pay?

Because payee verification happens before payment submission, the verification step can sit upstream of the payment rail. This gives financial institutions, fintechs, and payment providers a way to apply recipient checks during payment preparation rather than relying solely on controls built into an individual rail.

The same principle becomes particularly useful for organizations that handle both US domestic and cross-border payments. Instead of treating recipient verification as a country- or rail-specific requirement, payment teams can use it as a broader pre-payment control to improve confidence in who is receiving the funds.

iPiD's US Payee Verification helps financial institutions and payment providers verify recipient account details before money moves, supporting payment flows both domestically and globally.

As US payments become faster, there is less time to correct a fraudulent or misdirected payment after it has been sent. Payee verification moves an important question earlier in the process: does this account actually belong to the recipient we intend to pay?

Want to see how payee verification could fit into your payment flows?