Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Bank Stopped Fraud With A Simple Wait
Transcript
- Lucas: Most people think fraud prevention is an arms race of better algorithms and faster servers. But last week I read about a mid-sized regional bank that cut its fraudulent transaction losses by forty percent without buying any new software. Luna: Forty percent is massive. Did they finally upgrade their legacy systems? Lucas: No. They did the exact opposite. They introduced a mandatory thirty-second pause before approving any high-risk digital transfer above five thousand dollars. That’s it. Just a hard stop. Luna: Thirty seconds feels like an eternity in fintech. How did customers react? Lucas: Surprisingly well, because the pause wasn’t dead air. It displayed a single line of text reminding the user to verify the recipient’s identity via a separate channel. It turned an impulsive click into a deliberate verification step. Luna: So they’re betting on cognitive friction over computational speed. Lucas: Exactly. For years, we’ve been told that every second of latency loses revenue. But here, that latency stopped bad money from leaving the building entirely. It’s a classic case where slowness is actually the feature. Luna: It reminds me of those hospital studies we covered earlier where adding a camera to track OR turnover time forced staff to be more mindful of each step. Lucas: Right. Visibility creates accountability. In this bank’s case, the thirty-second window created a moment of doubt. And doubt is good when you’re dealing with social engineering attacks where the victim is being pressured to act fast. Luna: Do you think this scales to larger institutions? Or does the volume make a manual pause impossible? Lucas: That’s the key question. The bank only applied this to transactions over five thousand dollars. The vast majority of daily transactions are small and automated. So they’re not slowing down the whole pipeline, just the risky tail end. Luna: Targeted friction. I like that. Lucas: If these conversations have moved your work forward in some small way, consider supporting the show directly. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these episodes. No ads, just us figuring out how businesses actually run. Luna: It really helps keep the research sharp and the interviews consistent. Thanks for keeping the lights on. Lucas: Back to the data. The bank tracked call volume during those thirty seconds. Surprisingly, less than two percent of users abandoned the transaction. The rest waited, verified, and completed the transfer. Luna: Two percent abandonment for a forty percent reduction in fraud loss? That’s a winning trade-off. Lucas: It is. But let’s look at the psychology. Why does a simple timer work so well? It’s because most fraud relies on urgency. The scammer wants you to feel panicked. The pause breaks that emotional loop. Luna: So it’s not a technical fix, it’s an emotional interrupt. Lucas: Precisely. It forces the brain back into analytical mode. Daniel Kahneman would love this. It shifts the user from System One thinking—fast, intuitive—to System Two, which is slower and more deliberate. Luna: Does the bank tell customers why the delay exists, or do they just frame it as a security measure? Lucas: They were transparent. The screen said something like 'Please verify this is you.' It wasn’t hidden behind jargon. It respected the customer enough to explain the protection. Luna: Transparency builds trust. If they had hidden it, people might assume the system was broken. Lucas: Absolutely. If users thought the app was lagging, support calls would spike. By naming the delay as a safety feature, they preempted frustration. It’s a great example of UX writing solving an operational problem. Luna: I wonder if other industries can copy this. Retailers have chargeback fraud too. Lucas: Definitely. E-commerce sites could implement a similar hold for high-value orders. Even a ten-second confirmation modal could reduce accidental clicks and impulse buys that get returned later. Luna: Reducing returns is almost as valuable as preventing fraud. Margins on returns are brutal. Lucas: True. But let’s stick to banking. The next phase for this bank is analyzing the pauses happen. Are there certain times of day where fraud spikes? Luna: Probably late nights or weekends when support teams are thinner. Lucas: Right. So they might adjust the length of the pause based on risk scoring. High risk gets sixty seconds. Medium risk gets thirty. Low risk stays instant. It’s dynamic friction. Luna: Dynamic friction. That’s a term I’m going to steal. Lucas: Use it wisely. The lesson here is that sometimes the best way to improve speed is to deliberately slow down the dangerous parts. It’s counterintuitive, but mathematically sound. Luna: It challenges the whole agile mantra of move fast and break things. Maybe we should move slow and secure things. Lucas: For critical infrastructure, absolutely. You don’t want to break security. You want to break the attacker’s momentum. Luna: Did the bank see any secondary benefits from this change? Lucas: Yes. Customer satisfaction scores actually went up slightly. People felt safer using the app. There’s a comfort premium attached to perceived security. Luna: So they saved money on fraud, improved retention, and boosted NPS. All from thirty seconds of silence. Lucas: It’s remarkable. We spend millions on AI models to predict fraud, but a simple timer changed the behavior of the human on the other side. Luna: Sometimes the simplest tool is the sharpest one. Lucas: Or the most effective one. I’m curious if you’ve noticed this kind of deliberate pause in other apps lately. Do you use any banking apps that feel intentionally slow? Luna: Not recently. Most try to be invisible. But maybe they should be a little more visible. Lucas: Maybe. Invisible is fine for utility. Visible is better for trust. As we build more complex financial lives, visibility might become the new luxury. Luna: I’ll have to watch my own transactions next time I log in. Lucas: Do. And notice how you feel when the screen loads versus when it asks you to confirm. Luna: It’s funny how much power lies in those tiny moments of hesitation. Lucas: It really is. Next time you’re designing a process, ask yourself: where is the rush hurting us? And maybe, just add a timer.