A transfer to a new payee lands in a bank’s review queue. The customer used their usual phone and approved the payment in the app. Earlier that morning, though, they called the bank about a text linking to a page made to look like its sign-in screen. The text arrived after the customer contacted what they thought was the bank’s support account on social media. If the analyst reviewing the transfer has that call report, there’s a question to settle before the money goes out: did the person posing as bank support also tell the customer where to send it?
The FBI has documented both credential theft through bank impersonation and scams in which customers send the money themselves. The same impersonation can lead to either outcome. Someone who captures a password can try to sign in as the customer. Someone who convinces the customer that their savings are in danger can ask them to move the money to a supposedly safe account. In the second case, an additional authentication check may work exactly as designed: it can give the bank greater confidence that its customer approved the transfer. The customer can pass that check while following the scammer’s instructions.
What the First Report Can Tell the Bank
A customer who reports a suspicious text may be the first person to give the bank the address of a phishing site. The security team can use the link to investigate and pursue takedown, while the details of the call help the fraud team decide what to look for on the account. If the customer entered their password, the team needs to know roughly when. An unfamiliar device on its own could mean the customer bought a new phone. A sign-in from that device minutes after the customer entered their password, followed by a change to their contact details, gives the bank a reason to investigate the session and secure the account.
The bank can make that connection faster if the report reaches fraud operations while the account activity is still unfolding. The call handler can record which account is involved, the suspicious link and when the customer received it. If security later confirms the site is fraudulent, it can add that finding to the same case so the fraud team can check for sign-ins or account changes since the text arrived. That history is useful even after takedown, since the page may be gone by the time someone tries the stolen credentials.
Getting the Report Into the Payment Review
Even if the customer never entered a password, the impersonator may still be in touch. That’s why a generic phishing flag gives the payment reviewer so little to work with. The reviewer needs to know what the customer received, how they responded and when the contact took place. They can then weigh the report alongside the payment amount, the destination and recent activity on the account. If the reviewer calls the customer at a number the bank has on file, the customer may explain that someone from “bank support” told them to move their savings for safekeeping. That gives the reviewer a chance to warn the customer and, if the bank’s fraud policy calls for it, hold the payment for further review.
The response depends on what’s still in doubt. When the bank suspects someone else has signed in, an additional verification step can help establish whether it’s the customer at the other end. When the customer is already in the app and the evidence points to someone coaching them, the bank may get more from a conversation about the recipient than from another approval prompt. A successful check in that situation shouldn’t, by itself, clear the payment alert.
Payment reviews can also turn up evidence the security team hasn’t seen. If reviewers hear the same story from several customers whose transfers are headed to the same recipient, the bank can look for other payments to that account, including from customers who haven’t reported anything. The fraud team can pass the profile names or links mentioned on those calls to the investigators tracking the impersonation campaign. That can widen the search for affected customers while there’s still time to reach some of them before they pay.
360 Fraud Protection by AppGate brings those parts of the investigation into the bank’s decisions about access and payments. 360 Brand Guardian detects impersonating profiles and phishing sites and supports takedown. Where a threat can be tied to a customer, the bank can use that information to review activity on the account. 360 Risk Control can assess external threat data alongside behavioral, device and transaction signals in real time. That assessment can inform whether the bank sends a payment for review or uses 360 Adaptive Authentication to ask for additional verification when its policy calls for it.