Payee verification is the practice of confirming that the bank account you are about to pay actually belongs to the payee you intend, before the payment is sent. It has moved from a nice-to-have to an expectation in 2026. The Federal Reserve now offers Payee Name Verification, part of its FedDetect services, letting institutions verify a payee’s name against an account before issuing a payment1, and it is piloting a FedNow pre-check so institutions can screen a receiver before an instant payment settles2. Nacha, separately, expects originators to validate accounts and screen for payments made under false pretenses. The category is arriving. This guide defines payee verification, explains why the Fed and Nacha are standardizing it, and covers the distinction that decides whether it actually stops fraud: matching an account to a name is not the same as proving the payment was authorized.
What payee verification is and how it works
Payee verification, also called payee name verification or confirmation of payee, checks that the account details you are about to pay belong to the party you intend to pay. In its common form it matches the payee name you entered against the name on the receiving account, and flags a mismatch before the payment goes out. The Federal Reserve describes its own service as the ability to verify an intended payee’s name with an account, routing and account number, prior to issuing a payment1, and notes it is payment-rail-agnostic. The goal is to catch a misdirected or fraudulent payment at the one moment it is still preventable: before release.
The idea is not new internationally. The United Kingdom introduced Confirmation of Payee years ago as a name-checking scheme across its banks, and it became a model other markets studied. What is new is the United States standardizing it at the rail level, through the Federal Reserve and Nacha, rather than leaving it to individual banks. For a business, the practical version is the same regardless of who provides the check: before money leaves, confirm that the account on the payment belongs to the vendor, employee, or counterparty the payment is actually for.
Why it is becoming standard: the Fed and Nacha
Two forces are turning payee verification from optional into expected. The first is the Federal Reserve. Payee Name Verification is now part of the FedDetect suite, and the Fed is piloting a network intelligence tool that lets institutions pre-check a receiver account before sending an instant FedNow payment2, specifically to help combat authorized push-payment fraud. When the central payment operator builds verification into the rails, it stops being a differentiator and starts being a baseline.
The second is Nacha. Its rules increasingly expect ACH originators to validate accounts and, under the 2026 fraud-monitoring changes, to screen for payments made under false pretenses3, which is the regulatory language for exactly the fraud payee verification targets. Together, the Fed and Nacha are making some form of payee verification a standard expectation for businesses that send payments, and the FBI’s $3.046 billion in 2025 business email compromise losses4 is the reason. For a finance team, the takeaway is that this is arriving whether or not you seek it out, so the useful question is what kind of verification actually protects you.
The limit of name-matching: an account match is not an authorization
Here is the distinction that decides whether payee verification actually stops fraud, and it is the one most coverage skips. Name-matching answers a narrow question: does this account belong to this name. That genuinely catches typos, stale details, and payments aimed at the wrong account by mistake. What it does not answer is the question a deceived business gets wrong: should I be paying this name at all. In a vendor-impersonation or business email compromise attack, the fraudster supplies a real account that matches a plausible name, often the supplier’s name spelled correctly or a lookalike entity opened for the purpose. The name-to-account check passes, because the account really does belong to that name; the deception is one layer up, in whether you should be paying that payee.
This is why name-matching alone, including the Fed’s and the banks’, narrows the risk without closing it. It confirms the account matches the name; it does not confirm that a human with authority actually intended this payment, to this payee, for this reason. Those are two different controls: account validation answers "does this account match this name," and payment authorization answers "did someone authorized decide to pay this." A business that treats a green name-match as full protection has verified the destination without verifying the decision, which is precisely the gap authorized-payment fraud lives in.
Payee verification for a business, in practice
Whoever provides the underlying check, the operational discipline for a business is consistent, and it extends name-matching into something that actually holds. Confirm any new or changed banking detail out of band, through a phone number or contact you already had on file, never the one in the email or invoice carrying the change, because the most common attack is a switched account on a real payee. Hold the first payment to any new or changed account until that confirmation is complete. And keep a named person on record as having approved the payee and the amount, so the decision is attributable later. Name-matching supports the first step; it does not replace the others.
This is the same practice the guides on payee verification versus Positive Pay and the wire fraud prevention buyer’s guide come back to, because it is what works across every fraud type. The point of naming it here is that as the Fed and Nacha make payee verification standard, the businesses that benefit are the ones that treat it as a decision to verify, not just a name to match. A check that runs before release, confirms the account and the approval, and leaves a record is the version that survives an audit and a determined impersonation alike.
From payee verification to verified intent
RankShield Financial starts where name-matching stops. It verifies the payee and the account, and then it verifies the part name-matching cannot: that a named human authorized this specific payment, to this payee, for this purpose, before it settles. It holds anything that does not match, and it seals a signed, tamper-evident record of the decision, so what you have afterward is not a green checkmark you have to trust but a verdict you can independently check. This is the honest distinction the site is built on, applied to the category term the Fed and Nacha are standardizing: a shared verdict you can verify rather than a shared score you must trust.
The boundaries stay explicit. RankShield is a verification and attestation layer in the authorization path, not a bank, a payment rail, or a custodian of funds; it does not replace the Fed’s Payee Name Verification or your bank’s account validation, it completes them by adding the authorization layer they leave open. It is a design-partner-stage product and claims no network it has not built. As payee verification becomes a baseline, the differentiator is no longer whether you match a name but whether you can prove the payment was intended, which is the layer worth having. If you want that in front of your payments, you can see how it works or request access.
What to take from this as the category arrives
Payee verification is becoming a standard expectation, and that is good: catching a misdirected payment before it settles is exactly the right instinct, and the Fed and Nacha standardizing it will prevent real losses. The one thing to carry out of this is the distinction, because it decides how much protection you actually get. Matching an account to a name catches mistakes and some fraud; proving that a named person authorized the payment catches the deception that name-matching cannot see. As the category matures, aim past the name match to verified, provable intent, and you will have the version of payee verification that holds when the payee looks exactly right and the payment is still wrong.
