Account takeover fraud: The strategy that helps executives understand its real impact
Guest: John Matas
Today I’m digging into account takeover fraud from a perspective that I think a lot of fraud fighters are going to recognize immediately. Not just how damaging account takeover attacks are, but how hard it can be to get executives and cross-functional teams to really understand what that damage means in business terms.
Because honestly, this is where a lot of fraud teams get stuck.
They know the risk is real. They see the account compromise patterns. They see the customer harm. They see the operational drag, the support cost, the false positives, and the downstream mess that follows login fraud. But when it comes time to explain all of that internally, the message can get flattened into numbers that do not fully capture the impact or jargon that does not land outside the fraud team.
So in this episode, I sat down with John Matas, former fraud leader at Etsy and Macy’s, to talk about the strategy he uses to help executives and stakeholders understand fraud more clearly. And what I really like about this conversation is that it is not about watering fraud down. It is about translating it better.
That matters.
Because account takeover fraud is not just a fraud problem. It is a customer trust problem. It is a retention problem. It is a support problem. It is a brand problem. And if fraud teams want the right investment, the right urgency, and the right cross-functional support, they have to get much better at explaining that.
Here is what that means in practice:
- Account takeover fraud needs to be explained in business terms, not just fraud terms
- Account takeover prevention gets stronger when executives understand customer, revenue, and operational impact
- Fraud detection teams often need better internal storytelling to gain support for controls and resources
- Login fraud and account compromise affect much more than loss rates alone
What you’ll hear in this episode:
- Why John Matas does not always lead with fraud language when speaking to executives
- How to frame account takeover fraud in terms other teams and leadership can act on
- Why account takeover prevention requires support across product, support, operations, and leadership
- How false positives, suspicious login detection, and customer friction fit into the bigger business picture
- What fraud teams can do to improve internal influence without losing technical credibility
You should listen to this episode if you:
- Work in fraud, trust and safety, security, product, or risk and need better ways to explain account takeover fraud internally
- Want stronger executive buy-in for account takeover prevention, fraud detection, or login fraud controls
- Are trying to balance suspicious login detection with customer experience and false-positive pressure
- Need a clearer way to explain the value of behavioral biometrics, device intelligence, or multi-factor authentication
- Feel like your fraud team is doing important work that still is not fully understood across the business
If you liked this episode, be sure to subscribe and review the podcast on iTunes, Spotify, YouTube, or wherever you listen to podcasts. It really helps with getting the word out.
Episode notes & key takeaways
Why account takeover fraud is still misunderstood internally
Let’s break this down.
One of the biggest problems with account takeover fraud is that the people closest to it often understand it best, while the people who need to support the solution may only see a small piece of the impact. Leadership might see losses. Support might see angry customers. Product might see friction. Security might see login fraud attempts. But unless someone connects those dots, the full picture never really lands.
That is a problem.
Because account takeover attacks do not stay neatly inside one metric. They spill into customer churn, increased support costs, reputational damage, operational cleanup, and a whole lot of internal confusion about who owns what. And if executives only hear about it as “fraud losses,” they may miss the much bigger business story.
That is one of the most useful parts of this conversation with John. He gets into how fraud teams can translate the issue so it is understood as a business problem with customer and revenue implications, not just a fraud queue problem.
- Account takeover fraud is often underestimated when teams report only direct losses
- Account compromise affects customer trust, retention, and operational workload
- Fraud detection becomes easier to support when the broader business impact is made visible
- Account takeover prevention needs shared understanding across teams, not isolated ownership
Why translating fraud into business language works better
Here’s what’s actually happening.
A lot of fraud fighters walk into meetings hoping the facts will speak for themselves. Sometimes they do. A lot of the time, they do not. Not because the fraud is not serious, but because other teams are listening through their own priorities. Product is thinking about conversion. Support is thinking about volume. Leadership is thinking about growth and margin. And if fraud is framed only in fraud language, it may not connect.
Right.
That is why John’s approach is so smart.
He is not saying fraud teams should stop being fraud experts. He is saying they should learn how to explain account takeover fraud in terms the rest of the business already understands. Customer lifetime value. Cost to serve. Brand trust. Retention. Operational drag. Those are not watered-down concepts. They are often the most effective way to get real traction.
And honestly, that usually works a lot better than leading with acronyms and assuming everyone else will catch up.
- Account takeover prevention gets more executive support when tied to customer and business outcomes
- Login fraud should be explained in terms of trust, cost, and long-term value, not just attack volume
- Fraud teams increase influence when they translate rather than oversimplify
- Better communication can lead to faster alignment on controls, staffing, and priorities
Why false positives are part of the account takeover conversation too
This is where things get especially important.
A lot of companies know they need stronger protection against account takeover attacks. The problem is that they also know bad friction can cost them real customers. So fraud teams end up in a familiar position. Stop more fraud, but do not annoy good users. Tighten controls, but do not hurt conversion. Add protection, but do not overwhelm support.
That usually does not end well unless everyone understands the tradeoffs clearly.
This is exactly why false positives belong in the same conversation as account takeover fraud. If a company only focuses on stopping bad actors without understanding the customer experience cost of overly broad controls, it may create a different problem. And if it only focuses on smooth login flows without understanding the risk of weak controls, it leaves the door open to more account compromise.
That balance is where mature teams operate.
A few things worth paying attention to:
- Suspicious login detection should be measured against both fraud reduction and customer friction
- False positives can undermine trust just as much as weak controls if they are not managed carefully
- Account takeover prevention works best when teams understand the tradeoff between access and risk
- Executives need to see both the cost of fraud and the cost of bad friction to make better decisions
How behavioral biometrics and device intelligence fit the story
This is one of those areas where fraud teams can lose the room pretty quickly if they are not careful.
Behavioral biometrics, device intelligence, multi-factor authentication, and related controls can be incredibly useful in account takeover prevention. But if you explain them only as technical solutions without connecting them to the specific business problem they solve, they can sound abstract or optional to people outside fraud and security.
And that matters.
Because the real question is not whether a control sounds sophisticated. The real question is what it helps the business do better. Does it reduce account compromise? Does it improve suspicious login detection? Does it let the company apply smarter friction instead of more friction? Does it protect good customers without making every login feel like a hurdle?
That is the framing that holds up.
John’s broader point here really lands for me. Fraud teams have to explain not just what a tool is, but why it matters in practical terms. Otherwise the conversation gets stuck at the surface.
- Behavioral biometrics can help distinguish suspicious behavior from normal customer behavior
- Device intelligence adds useful context when login fraud patterns are hard to detect from credentials alone
- Multi-factor authentication is important, but it works best when used thoughtfully inside a broader strategy
- Account takeover prevention is stronger when controls are explained through outcomes, not just features
Why fraud teams need influence, not just expertise
Honestly, this is the biggest takeaway for me.
A lot of fraud professionals are already right about the risks they are seeing. The challenge is not always insight. Sometimes the challenge is influence. Can they explain the issue in a way that gets action? Can they connect the fraud story to the business story? Can they help executives, product teams, and other stakeholders understand why urgency is warranted without sounding alarmist or overly technical?
That is the part that really holds up in this conversation.
Because account takeover fraud is not going away. Credential stuffing will keep evolving. Login fraud will keep adapting. Customer expectations will keep rising. And fraud teams will keep needing support from people who do not live in this work every day.
So the better they get at translation, the better they usually get at results.
The big takeaway from this episode is pretty straightforward. Account takeover fraud is much easier to address when fraud teams stop assuming the rest of the business sees what they see and start explaining the risk in terms leadership can actually use. That does not mean dumbing anything down. It means connecting customer harm, false positives, trust, revenue, and operational cost to the underlying fraud problem. And once that clicks, better decisions usually follow.
That is the part I would pay attention to.
