Braun sees potential for banks to match attackers’ ability to scale, supported by substantial computing resources. Realizing the opportunity depends on investment and priorities alongside banks’ other service commitments.
Fraud prevention starts before the bank sees a payment. Bottomline fraud expert John Braun explains how banks can help customers verify urgent requests and spot risks early.
An unfamiliar caller interrupted a typical day for the payments team with a request to change payment instructions. They said the usual contact at one supplier was out, some bank details had changed, and the payment needed to go out that day.
Nothing about the explanation seemed wrong. For the employee handling it, the job is to keep money moving. Questioning a proper-looking payment feels like creating friction.
That moment is when commercial fraud prevention succeeds or fails. Before a bank even has a transaction to assess, someone inside a business may have already decided to trust those instructions. And in many cases, they've let the fox into the coop.
For John Braun, senior product manager of CFRM at Bottomline, detecting risk before it becomes fraud starts with understanding a customer’s abilities and priorities. Companies need to make payments, but studying payment threats isn't their primary business.
“If I’ve got a customer that’s a manufacturer, their business is not payments. Their business is not stopping fraud,” Braun says. Even though that company is responsible for taking precautions, they are likely unprepared to defend against impersonation fraud, deep fakes, and other exotic threats.
At times like this, banks can bring expertise that helps corporates recognize danger earlier. Combining that guidance with informed payment decisions creates opportunities to interrupt fraud before money leaves corporate accounts.
When Being Helpful Can Also Make You Vulnerable
Braun says urgency is such a durable fraudster tactic because it's human nature to want to help. An employee who believes a supplier/customer is in difficulty may prioritize resolving the problem, particularly if the caller suggests a delay will bring consequences.
Fraudsters can exploit that instinct with a straightforward story. A substitute contact, an unexpected account change, and an appeal for immediate assistance may discourage questions that would otherwise seem reasonable.
“We want to meet customer needs, and we want to do it urgently because we want to be good partners. We want to help them,” Braun explains, illustrating the thought process.
Customer education needs to address that pressure directly. Employees should understand which departures from an established relationship require confirmation, however convincing and emotionally moving the explanation.
Noting how widespread and effective “impersonation fraudsters” are, Braun says the appropriate response is to reach out to a known contact through a trusted channel before submitting payment instructions. Using contact information supplied in the questionable communication leaves verification exposed to the same deception.
“Urgency can’t replace verification,” Braun says, underscoring a central point.
Banks can make fraud discipline easier to apply by connecting fraud education to the decisions customers face in their daily work. General warnings about scams have less practical value than explaining what to do when a supplier requests a sudden deviation.
Banks must take the lead in helping customers recognize when they should be skeptical and dig deeper into details before submitting those payment instructions, Braun adds.
That intervention occurs upstream from transaction monitoring. In other words, a request challenged inside the business may never become a payment instruction at all.
Give Investigators Better Reasons to Intervene
Once instructions reach the bank, the task changes. A new beneficiary, changed destination, or unusually large amount can warrant scrutiny even when the payment details appear correct.
The bank needs to determine whether a departure from normal patterns justifies contacting the customer and/or delaying the payment. It must make that judgment while fraud attempts multiply, and as customers grow impatient over resolution of delays.
Braun draws an analogy with artisanal products versus the mass produced. Individual attention may be desirable when making sourdough bread, he says, but when we're talking about B2B payments fraud at scale, teams need all tools at their disposal to hit back hard.
“You want something that’s industrialized to meet the industrialized nature of what’s attacking you,” he says.
The challenge involves the quality of decisions as well as processing capacity. Pausing a legitimate payment can frustrate a customer and consume investigative resources. Allowing a fraudulent one through can cause financial loss. Banks need a clear understanding of their risk tolerance to decide when intervention is justified.
A broader view of the beneficiary can help. For example, an account unfamiliar to one institution may have an established payment history elsewhere.
Bottomline’s Fraud Intelligence Exchange applies consortium-level intelligence to that assessment. Braun describes indicators including how long a beneficiary has been observed within the consortium, how many banks and originating accounts have paid it, payment volume, and reports of suspicious or fraudulent activity.
Together, those attributes provide evidence beyond a name match. They help investigators assess the observed history and determine whether further examination is necessary.
Payment history across multiple banks and vendors supports judgment rather than guaranteeing safety. Its operational value lies in helping investigators distinguish unfamiliar activity from activity that merits closer attention.
Using the consortium view, “I’m not investigating something that I don’t need to investigate,” Braun says. “That allows me to apply my resources to things that are riskier.”
Explain the Protection Before Customers Need It
A bank can invest in detection and still leave one consequential gap in the relationship: what the customer believes will happen if a scam succeeds.
Responsibilities, recommended controls, and expectations about potential losses deserve discussion before an incident. Leaving them unspoken allows assumptions to persist until money goes missing.
Braun advocates an explicit explanation of what each party contributes to prevention. Think of it as saying, “Here’s what we do to protect your money, and here’s what you need to do to protect your money,” he says.
That conversation should cover the bank’s safeguards, best practices it recommends to customers, and why suspicious activity may prompt a call or payment hold. Customers should understand how protective intervention fits into the service levels they receive.
A discussion like this also establishes the limits of what either party can observe. The customer knows the business relationship and the circumstances surrounding a request. The bank can assess payment patterns and bring additional intelligence to the decision. Effective prevention depends on both parties contributing their own anti-fraud resources.
Keeping those responsibilities visible requires attention throughout the relationship. Commercial customers remain occupied with serving their markets, and fraud prevention can slip down the list of priorities. That’s not good. “When fraud happens, two things can disappear: your customers’ money, and your customers’ trust,” Braun says.
The opportunity for 2027 is to strengthen that relationship while there is still time to act. A customer who understands why verification matters is better prepared to question urgent requests. A customer who understands the bank’s controls is better prepared for a call that interrupts a payment.
FAQs
Specialist providers and PSPs such as Bottomline can contribute market research, testing, and technology development. That expertise helps banks assess innovative approaches while internal teams manage broader operational and product responsibilities.
The measure Braun describes is the earliest payment to that beneficiary recorded within the consortium. It establishes how long the network has observed the account, which may differ from the account’s actual age.
Share