Skip to main content

Software, apps, websites, networks and AI automation

Technology Insights

Vendor Payment Fraud in 2026: Why a Hijacked Email Thread Can Redirect a Real Invoice, What Callback Verification and Nacha’s New Fraud Rules Actually Stop, and How to Get a Wire Back in the First 72 Hours

Vendor Payment Fraud in 2026: Why a Hijacked Email Thread Can Redirect a Real Invoice, What Callback Verification and Nacha’s New Fraud Rules Actually Stop, and How to Get a Wire Back in the First 72 Hours

  • Internet Pros Team
  • November 21, 2026
  • Networking & Security

The email looks completely normal. It comes from the real address of a supplier you have paid for years, it replies inside an existing thread about a real invoice, and it says the company has moved banks, so please send this month’s payment to the new account. Accounts payable updates the record, the money goes out, and three weeks later the real supplier calls asking why they have not been paid. By then the money has passed through several accounts and is very hard to get back. This is vendor payment fraud, the most expensive kind of business email compromise (BEC), and it beats spam filters because nothing in the message is technically fake.

Why This Scam Costs More Than Ransomware

The FBI’s Internet Crime Complaint Center (IC3) recorded about .77 billion in reported BEC losses in 2024, more than any other type of cybercrime except investment fraud. The real figure is higher because many businesses never report. Each loss is usually one large transfer, often five or six figures, and that can wipe out a small company’s cash.

The attack works because it goes after your process, not your computers. Nobody installs malware on the payment system. The attacker gets an employee who is doing the job correctly to send money somewhere new.

Every request to change bank details is a request to move your money. Handle it like one, no matter how familiar the sender looks.

How the Thread Gets Hijacked

Most of these scams start with a mailbox that someone else controls, either yours or your supplier’s. The usual steps:

  • Account takeover. A phishing page, a stolen session cookie or a malicious app consent gives the attacker quiet access to a real mailbox, usually the supplier’s, since smaller suppliers tend to have weaker security.
  • Reconnaissance. The attacker reads weeks of email to learn who pays whom, how much, how often and how people normally write.
  • Hiding rules. An inbox rule moves any reply containing words like “invoice”, “payment” or “bank” into an obscure folder, so the real owner never sees the conversation.
  • The switch. Right when a real invoice is due, the attacker sends updated bank details, sometimes with a convincing letterhead PDF, from the real account or from a lookalike domain that takes over the thread.
  • Urgency. A follow-up says the old account is frozen, an audit is underway or a late fee applies, which pushes the payer to skip the usual checks.

Because the first message often comes from a real, authenticated mailbox, SPF, DKIM and DMARC all pass. Email security helps a lot against lookalike domains, but it cannot catch a request sent from a mailbox the attacker has legitimately logged into.

Why the Bank Often Cannot Help

Many owners assume the bank would notice that the account name does not match the supplier. In the United States it usually does not have to. Under UCC Article 4A, the rules that govern commercial wire transfers, a receiving bank can generally credit a wire based on the account number alone, even if the beneficiary name on the instruction is different. Once the money lands, criminals move it on within hours.

That is starting to change. Europe now requires Verification of Payee, a name check before most euro transfers, and the UK has had Confirmation of Payee for years. In the US, Nacha’s new fraud monitoring rules, phased in during 2026, require businesses and banks that send and receive ACH payments to have risk-based processes for spotting payments made under false pretenses, a category that explicitly includes vendor impersonation and BEC. Some US banks also offer account validation services that confirm an account is open and belongs to the named payee before you pay it. Ask your bank which of these you can use.

The Controls That Actually Stop It

ControlWhat it stopsWhere it fails
Callback verificationFake bank detail changes, since you confirm by phone using a number you already hadCalling the number printed in the suspicious email reaches the attacker
Dual approvalOne rushed or tricked employee releasing a payment aloneApprovers who rubber-stamp without looking at what changed
Change cooling-off period“Pay today” pressure on a brand-new accountExceptions made for “urgent” requests
Bank payee checks and positive payPayments to accounts that do not match the payee, and altered checksOnly works if you enroll and act on the alerts
Phishing-resistant MFATakeover of your own mailboxesDoes nothing about a supplier’s hacked account
Inbox rule alertsHidden forwarding and auto-delete rules on your accountsNeeds someone to review the alerts

A Bank Detail Change Policy You Can Adopt This Week

Six written rules for accounts payable

  1. No change by email alone. A request to change remittance details, from any sender, starts a verification process. It never updates the record directly.
  2. Call back on a known number. Use the phone number in your vendor file or on an old contract, never one from the request. Speak to someone you have dealt with before and confirm the new details out loud.
  3. Two people, two steps. One person verifies the change, a different person approves it in the payment system, and the system logs both.
  4. Wait before the first payment. Hold the first payment to a changed account for a few business days, or send a small test amount and have the vendor confirm it by phone.
  5. Watch for the pattern. Urgency, secrecy, a new country or bank, a personal-looking account name, or a request to “keep this between us” means stop and escalate.
  6. Protect the people who pause. Tell staff in writing that no one, including the owner, will ever be upset by a delay caused by verifying a payment. Attackers count on fear of the boss.

The same rules apply inside your company. Payroll diversion, where a “staff member” emails HR to change their direct deposit account, uses the same trick. Require changes to go through your HR portal with MFA, or confirm them in person.

If Money Already Went Out: The First 72 Hours

Speed matters more than anything else. Money that is still sitting in the first receiving account can often be frozen. Money that has been moved on usually cannot.

  • Call your bank’s fraud line immediately and ask for a wire recall or ACH reversal. Ask them to contact the receiving bank directly.
  • File at ic3.gov the same day. The FBI’s Recovery Asset Team works with banks to freeze funds, and its Financial Fraud Kill Chain covers qualifying international wires reported quickly.
  • Secure the mailboxes. Reset passwords, end all active sessions, remove unknown inbox rules and app consents, and check who else was emailed from the account.
  • Tell the real vendor on a known number so they can clean up their own systems and warn other customers.
  • Notify your insurer. Many cyber policies exclude social engineering fraud or cap it at a small sublimit unless you bought specific coverage. Check yours now, not after a loss.

The Bottom Line

Vendor payment fraud works because the email is real, the invoice is real and the employee is trying to do the right thing. Filters and MFA reduce how often attackers get in, but the control that actually saves the money is boring: no bank detail change without a callback to a known number and a second approver. Write it down, train on it, and make pausing the safe choice.

Want help hardening your email, setting up inbox rule alerts or writing a payment verification policy? Contact Internet Pros for a business email security review.

Share:
Tags: Networking & Security Business

Related Articles