Bank Impersonation Scams: How to Protect Your Business
Payments News

Bank Impersonation Scams up 124% at Surveyed Banks: Protect Your Business

Bank impersonation scams rose 124% at surveyed banks. See what the FCC robocall plan changes and the call-back rule that protects your business.

Businessman in a dark suit and red tie talking on a mobile phone by an office window, city tower behind him

Photo: Pixabay

On this page 7 sections
  1. What Happened: Bank Groups Ask the FCC to Tighten the Robocall Mitigation Database
  2. The Numbers Behind the Rise in Spoofed Bank Calls
  3. How Bank Impersonation Scams Reach Your Business
  4. What the FCC Robocall Proposal Could and Couldn't Fix
  5. Your Call-Back Rule for Any "Bank" or "Processor" Contact
  6. Lock Down Payout Changes, Admin Users and Alerts
  7. If You've Been Hit: First-Hour Steps With Your Bank and Processor

Key takeaways

  • Caller ID proves nothing. Two banks in BPI's survey found that 40% of calls showing their own numbers were spoofed.
  • The FCC's robocall database proposal goes after carriers that pass spoofed voice calls. It doesn't cover texts, it can't get stolen money back, and it isn't final yet.
  • No one should be able to change a payout account, payee or wire instruction without a second person who calls back on a number you already had.
  • In the illustrative restaurant example, checking deposits every day shrinks a possible $60,000 loss to about $8,000.

Bank impersonation scams by phone and text more than doubled in a year at the banks that tracked them, and the same scripts can be aimed at a business owner's phone. A Bank Policy Institute survey of 14 member banks found that the average number of identified bank-impersonation scams that started with a call or text rose 124% from 2024 to 2025. The defense that protects your business costs nothing. Hang up on any "fraud department" caller, call back on a number you already had, and make sure no payout or bank-account change can happen because of one phone call.

What Happened: Bank Groups Ask the FCC to Tighten the Robocall Mitigation Database

On Nov. 9, 2026, the Bank Policy Institute (BPI) and 10 other financial services and payments trade associations filed joint reply comments with the Federal Communications Commission. The signers included America's Credit Unions and the Defense Credit Union Council. They backed the FCC's proposal to strengthen the Robocall Mitigation Database. BPI recapped the filing, including its own survey data, in its Nov. 14 BPInsights newsletter.

The FCC Robocall Mitigation Database (RMD) is the federal registry where phone carriers describe what they do to keep illegal calls off their networks. Other carriers rely on those filings when deciding whether to accept a provider's calls.

The FCC's proposal is a Further Notice of Proposed Rulemaking (FCC 26-49), adopted July 22, 2026, and published in the Federal Register on Sept. 9. It would:

  • let FCC staff put new filings in "pending" status or reject them when they look deficient or tied to a provider that was already removed;
  • set out the grounds for removal, with a faster two-step process that gives a provider five days to respond to a serious violation;
  • consider one-step removal for egregious conduct, plus a bar that keeps removed operators from coming back under new names;
  • extend filing duties, in certain cases, to dialing platforms, cloud phone providers, private branch exchanges (PBXs) and call centers.

The trade groups asked for more, according to BPI's recap and Credit Union Daily's report on the joint filing. They want providers to disclose how long they have been operating, which could help spot a removed provider that comes back as a successor company. That isn't hypothetical. The groups cited information given to the American Bankers Association showing that traffic tied to a provider removed in March 2026 moved the next month to what appeared to be a successor company.

The groups also want intermediate carriers, the ones that pass calls along, to check the database when vetting the providers that send them traffic. They want faster enforcement against bad actors. And they asked the FCC to make clear that a company's own in-house phone system or call center doesn't have to register. That matters to merchants who run a phone-order line.

Reply comments were due Nov. 9. Nothing changes until the FCC votes to adopt final rules.

The Numbers Behind the Rise in Spoofed Bank Calls

The 124% rise isn't the only number in the BPI survey cited in the filings. The second one matters more at your front counter: two of the surveyed banks reported that 40% of calls appearing to come from bank-owned numbers had been spoofed.

Spoofing means the caller faked the number on your screen. Caller ID showing your bank's real phone number proves nothing.

FCC enforcement shows how those calls get in. In an action against the carrier Voxbeam, reported by American Banker, the FCC said the company carried robocalls impersonating financial institutions. The calls came from Axfone, a provider based in Czechia that wasn't listed in the database. Voxbeam carried nearly 61,000 calls from Axfone between March 31 and April 3, 2025, and about 80% of them showed caller IDs linked to Chase or Bank of America. That's the gap the RMD proposal targets.

Read the survey for what it is. It covers 14 banks, it counts only the scams those banks identified, and it doesn't separate business customers from consumers. It shows the trend, not your odds.

How Bank Impersonation Scams Reach Your Business

Vishing (voice phishing) aimed at a business usually ends in one of three ways, and none of them requires breaking any technology. The scammer needs one person to do one thing.

The fake fraud alert. A text says a large charge or wire was flagged and asks you to reply or call. Then a "fraud department" agent calls from what looks like your bank's number. The agent says they need to "verify your identity" with the one-time passcode your bank just texted you. That code usually exists because the scammer is signing in as you or approving a new payee at that moment. Reading it aloud is a direct route to business account takeover. That means a criminal controls your online banking or processor portal and can move money or change settings.

The processor imposter. The caller claims to be from your card processor's risk or support team. Your account is "about to be frozen," your terminal "needs an update," or a "test transaction" is required. They might ask you to install remote-access software, read off a login, or key a refund on the terminal or virtual terminal. A refund keyed to the scammer's card is real money leaving your batch.

The deposit change. This is the quietest version. Someone with portal access, or someone who talks a support agent into it, swaps the bank account where your card deposits land. Sales run normally. The deposits just stop reaching you.

Each version hits a different person in the business. Restaurant and bar managers get the call mid-rush, when "just read me the code" sounds quicker than arguing. Retail cashiers get asked to run the "test refund." In professional-services firms, the target is the bookkeeper who handles vendor changes. E-commerce stores often have several admin logins, and any of them may be able to edit payout settings.

What the FCC Robocall Proposal Could and Couldn't Fix

If the FCC adopts the rules, it could get harder for fly-by-night carriers to push spoofed bank calls into the network. New providers would be screened before going live, and repeat offenders could be cut off faster. Fewer spoofed calls reaching your phone is a real benefit.

The limits are real too. The RMD covers phone calls, so bank impersonation text scams fall outside it. In September comments on a separate FCC robocall scorecard, many of the same groups asked that text messages be included in that scorecard. The proposal doesn't stop a scammer who gets you to call them, or one who reaches you by email. It won't recover a dollar after you approve a transfer. And it's still a proposal.

So whatever happens in Washington, your controls should assume the caller ID is lying.

Your Call-Back Rule for Any "Bank" or "Processor" Contact

Give this to everyone who handles money:

  1. Hang up on any call you didn't make about your money. Be polite, end the call, and say you'll call back. A legitimate caller can wait for that.
  2. Call back only on a number you already had. Use the back of your business debit card, your bank statement, your processor agreement or the support number inside your processor portal. Never use a number from the call, the text, a voicemail or a search ad.
  3. Keep one-time passcodes to yourself. Those codes are for you to type, not to read to anyone.
  4. Refuse remote-access installs, "test" refunds and transfers to a "safe account" that anyone requests by phone, text or email.
  5. Require two people for any change to payout accounts, payees or wire instructions, with the second person making the call-back.

Keep a one-page list of known numbers at the register and in the office: your bank's fraud line, your business banker, processor support, and your sales agent if you signed up through one. If you bought through an ISO (a company that resells a processor's services), you may hear from either the ISO or the processor behind it. That's why the number has to come from your paperwork. Our explainers on how a processor, acquirer and gateway differ and buying from an ISO, a PayFac or a direct processor help sort out who could legitimately call.

Lock Down Payout Changes, Admin Users and Alerts

Do these this week:

  • Turn on alerts with both your bank and your processor for any change to your deposit account, login email or phone number.
  • Turn on multifactor authentication for every bank, processor, gateway and online-store login. Use an authenticator app where one is offered.
  • Review admin users. Remove former employees and contractors, and give managers only the access their job needs.
  • Limit who can issue refunds on POS terminals and virtual terminals, and set a refund cap where your system allows one.
  • Ask your bank which payee and ACH controls it offers for your operating account, such as positive pay or debit blocks.
  • Match card deposits against sales every day. A deposit that doesn't arrive is your earliest warning.

Our guides to how long credit card deposits take and why your merchant deposit doesn't match your sales explain normal timing and the fees behind smaller gaps. If a bank outage is behind a late deposit, see our merchant playbook for delayed payments after the Chase outage. Our payments news roundup for November 17, 2026 covers what Monday's Chase outage means for your deposits.

And don't assume the fraud protection on a personal card carries over to a business account. Read the unauthorized-transfer section of your deposit agreement and ask your banker what your liability would be.

Worked Example: What a Missed Deposit Change Costs

These numbers are illustrative. Assume a restaurant nets $2,000 a day in card deposits after fees and is open seven days a week. Each day's batch is deposited one to two business days later. A scammer changes the payout account on a Friday afternoon.

If nobody checks deposits until the monthly bookkeeping review, about 30 days of sales could be redirected: 30 × $2,000 = $60,000. If a manager checks deposits daily, the missing Friday deposit shows up Monday or Tuesday. At that point the Friday through Monday batches are at risk: 4 × $2,000 = $8,000, and there's still a chance to recover it. A change alert can flag the problem before any deposit moves, if someone acts on it right away.

If You've Been Hit: First-Hour Steps With Your Bank and Processor

  1. Call your bank's fraud line using the number on your known-numbers list. Ask the bank to stop or recall any outgoing wire or ACH transfer, lock online banking and flag the account. Minutes matter, because stolen money tends to be moved again quickly.
  2. Call your processor using the support number on your known-numbers list. Ask it to lock account settings, restore your deposit account and hold pending deposits until the account is verified. MannyPay merchants can also reach our team through the MannyPay contact page.
  3. Change passwords and sign out of all active sessions on your bank, processor, gateway, online-store and email accounts. Uninstall any remote-access tool a caller talked you into.
  4. Write down the times, the numbers that called or texted, the names used, what was shared and what money moved.
  5. File a police report and report the scam to the FTC and the FBI. Your bank may ask for report numbers.
  6. Tell your staff the same day, so a second call with a new story doesn't work.

This is general information, not legal advice. Talk with your bank, an attorney and your insurance agent about recovery options and whether your policy covers social-engineering fraud.

Start with the cheapest fix: print the known-numbers list and turn on payout-change alerts before your next batch closes. After that, watch two things. One is the FCC's vote on the RMD rules. The other is whether the FCC's separate robocall scorecard ends up covering text messages, as the bank groups asked.

Sources

  1. BPInsights: November 14, 2026 (Bank Policy Institute)
  2. Answer This Call, America's CUs, DCUC and Other Trade Groups Tell FCC in Urging Stronger Robocall Mitigation Database (Credit Union Daily, Nov. 10, 2026)
  3. DCUC Urges FCC to Strengthen Robocall Database and Stop Credit Union Impersonation Scams (Defense Credit Union Council, Nov. 9, 2026)
  4. Improving the Effectiveness of the Robocall Mitigation Database, Proposed Rule, 91 FR 57454 (Federal Register, Sept. 9, 2026)
  5. FCC Opens Comment Window on Sweeping Robocall Mitigation Database Overhaul (CommLaw Group)
  6. FCC Proposes Sweeping Changes to Robocall Mitigation Database (Wiley)
  7. FCC Hits Telecom Firm That Enabled Bank Impersonation Calls (American Banker)
  8. BPI, Financial Services Trades Comment on FCC Robocall Scorecard Proposal (Bank Policy Institute)

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading