Community
In my blog "The Missing Link in Fraud Prevention: Real-Time Customer Dialogue" (https://bankloch.blogspot.com/2025/06/the-missing-link-in-fraud-prevention.html) I argued for moving fraud checks earlier in the payment flow. Rather than waiting until a customer has signed and submitted a payment, banks should interact during the initiation phase. This not only allows for blocking fraudulent transactions sooner but also serves to educate customers in real time.
With Authorized Push Payment (APP) fraud on the rise, early-stage interaction is a step in the right direction. But what if we could go even further?
To truly understand how we can intervene more effectively, we need to break down a typical scam into four distinct stages:
Currently, most banks concentrate their fraud detection efforts at Stage 3. In my previous blog, I proposed extending that effort into Stage 2. This post explores why we also need to address Stage 1.
Of course, Stage 4 remains essential - recovering stolen funds, investigating fraud cases, improving earlier controls, and sharing threat intelligence (see my blog "Fighting Financial Crime Together: The Role of Data Sharing" - https://bankloch.blogspot.com/2025/03/fighting-financial-crime-together-role.html). But shifting focus to the very beginning of the scam process - before a transaction is even considered - could be transformative.
It’s tempting to say Stage 1 falls outside the banking domain. After all, most scams originate on social media or via SMS, which puts the responsibility on tech giants and telecom providers. These players should be the first line of defense, using AI moderation, account verification, and platform monitoring to prevent scam content from spreading. Governments, too, must step up public education and law enforcement responses to digital crime.
But here’s the problem: these actors often fall short.
Social media platforms continue to scale back moderation efforts. Governments struggle to keep pace with the speed and adaptability of scam networks. That leaves banks - who are increasingly on the hook for compensating APP fraud losses - with a growing incentive to get involved earlier.
Preventing fraud before a payment is initiated offers several advantages:
And some banks are already stepping up.
CommBank recently launched the Scam Checker, a Gen AI-powered tool that allows customers to paste suspicious messages or links into their banking app for instant analysis. The tool cross-references known scam language, user-reported content, and actual fraud data. As CommBank puts it: "When you upload a suspicious text to Scam Checker, you’re not just protecting yourself. You’re also helping keep others safe by sharing valuable information that can be used to help protect them too."
The app also provides real-time alerts when a user’s identity is misused at major merchants (e.g. impersonation at telcos and banks) or when their personal information is exposed in a data breach (i.e. Dark web monitoring). Customers are then guided step-by-step on how to respond.
Here’s a range of actions banks can take - some already in use, others emerging - to intervene earlier:
Stage 1 might not be the traditional domain of banks, but the line is blurring. As fraud becomes more sophisticated - and the burden of losses shifts - banks are not just protectors of funds, but partners in prevention.
By stepping in sooner, banks not only defend their bottom line - they become trusted digital allies in their customers’ daily lives.
For more insights, visit my blog at https://bankloch.blogspot.com
This content is provided by an external author without editing by Finextra. It expresses the views and opinions of the author.
Alex Malyshev CEO, Co-founder at SDK.finance, FinTech software provider
30 September
Erica Andersen Marketing at smartR AI
28 September
Anurag Mohapatra Director of Fraud Strategy and Marketing at NICE Actimize
26 September
Anil Kollipara Vice President, Product Management at Spirent
Welcome to Finextra. We use cookies to help us to deliver our services. You may change your preferences at our Cookie Centre.
Please read our Privacy Policy.