Today we are talking about payments fraud strategy and why fraud teams get a whole lot stronger when they really understand how payments work underneath the surface. Not just chargebacks. Not just card testing. Not just the obvious fraud losses. The actual mechanics. The data. The flows. The approvals. The declines. All of it.
I sat down with Scott Engel, who has spent more than twenty years working across fraud and payments, to talk about how those two worlds connect, where fraud teams often miss valuable signals hiding inside payment data, and why learning the payments side of the business can completely change how you think about fraud prevention.
And that matters.
Because at first glance, fraud and payments can seem like neighboring functions that only overlap in a few places. But when you dig in, the fraud and payments relationship is much tighter than that. Payment orchestration and fraud decisions affect each other constantly. Authorization data for fraud detection matters. Payment declines and fraud outcomes matter. The payment lifecycle itself creates risk, opportunity, and visibility if you know where to look.
Here is what that means in practice:
- Payments fraud strategy gets stronger when fraud teams understand the payment lifecycle, not just the final outcome
- Payment data for fraud detection can reveal risk signals that are easy to miss if teams only focus on post-transaction loss
- Payment operations for fraud teams matter because fraud prevention and payments performance are constantly influencing each other
- Merchant payment fraud strategy works better when teams optimize payments and fraud together
- Continuous learning in payments gives fraud leaders a much clearer view of ecommerce payment risk
What you’ll hear in this episode
- How Scott’s career moved across fraud prevention in travel payments, subscription payments fraud, and broader payments leadership
- Why the fraud and payments relationship is much closer than many teams realize
- How payment data for fraud detection can improve fraud signals in payment flows
- What Scott’s pyramid of payment needs reveals about payments risk management
- Why payment team collaboration and network knowledge for fraud leaders matter so much
You should listen to this episode if you
- Work in fraud and want a stronger payments fraud strategy grounded in how payment systems actually work
- Support merchant payment fraud strategy and need better alignment between fraud and payments teams
- Want to understand authorization data for fraud detection and payment lifecycle fraud controls
- Care about ecommerce payment risk, payment declines and fraud, and optimizing approval performance without increasing abuse
- Value continuous learning in payments and want a more practical view of fraud prevention through payment expertise
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 payments fraud strategy starts with understanding payments
Let’s break this down.
A lot of fraud teams spend most of their time focused on the visible outcomes. Chargebacks. ATO. Card testing. Refund abuse. Friendly fraud. All important. Of course.
But if you stop there, you miss a lot.
Because payments fraud strategy gets much stronger when fraud teams understand what is happening inside the payment flow before the loss shows up. What data is available at authorization. What decline reason really means. How routing works. What the processor is doing. What the issuer is seeing. What the merchant can influence and what they cannot.
That is where things get interesting.
The more you understand the payment system, the better you get at spotting fraud signals in payment flows that might otherwise just look like noise.
And that matters.
Why the fraud and payments relationship is so important
At first glance, fraud and payments can look like separate priorities. Fraud wants to reduce abuse. Payments wants to improve approvals, lower cost, and keep transactions moving. Sometimes those goals line up neatly. Sometimes they do not.
But the reality is they are deeply connected.
Fraud decisions affect authorization rates.
Payment decisions affect fraud exposure.
Decline behavior changes customer experience.
Routing choices change what data you see.
And payment friction can either help or hurt depending on when and why it gets applied.
That is why the fraud and payments relationship matters so much.
If those teams are not working together, you usually end up with one of two bad outcomes. Either the fraud team blocks too much without understanding the payment cost, or the payments team chases conversion without understanding the abuse cost. Neither of those usually ends well.
Good payment team collaboration is not just nice to have. It is operationally necessary.
How payment data sharpens fraud detection
This is one of the most useful parts of the conversation with Scott.
Payment data for fraud detection is often underused by teams that are focused mostly on surface-level fraud signals. But payment systems generate a lot of useful information if you know what to look for.
Things like:
- Authorization data for fraud detection
- Response codes and issuer behavior
- Patterns in retries and declines
- Velocity across payment methods
- Signals tied to account updater activity, recurring billing, or processor-level behavior
None of that replaces good fraud models. But it adds context.
And honestly, context is where a lot of good fraud decisions get made.
This is especially true in subscription payments fraud and fraud prevention in travel payments, where payment patterns can be more complex and customer behavior can be harder to interpret cleanly. The more your team understands the payment side, the better you get at separating genuine customer behavior from risky behavior.
What the pyramid of payment needs tells us
Scott talks about his pyramid of payment needs, and I really like frameworks like this when they actually help people think more clearly. This one does.
Because payments risk management is not just about one metric. It is not just about approval rate or fraud rate or cost or customer experience by itself. It is about how those layers build on each other and where teams need stability before they start chasing optimization.
That is the part people sometimes skip.
They want better performance before they have enough operational consistency.
They want higher approvals before they understand their true fraud exposure.
They want better fraud outcomes without understanding the payment stack underneath them.
Right. That gets messy fast.
A strong payments fraud strategy depends on building from the foundation up. Stable operations. Clear visibility. Good data. Smart controls. Then optimization.
That usually works better than trying to solve everything with one dashboard and a lot of hope.
Why payment declines are a fraud problem too
Payment declines and fraud are connected in more ways than people realize. A decline is not always just a lost sale. Sometimes it is a fraud signal. Sometimes it is a false positive. Sometimes it is an issuer decision that tells you something useful about the transaction. Sometimes it is a clue that your routing, risk rules, or payment setup are creating unnecessary friction.
That is why declines matter.
If fraud teams ignore declines because they are only focused on approved fraud, they miss part of the story. And if payments teams ignore the fraud meaning behind decline patterns, they miss a different part of the story.
This is where optimize payments and fraud together becomes more than a nice phrase. It is the actual job.
Because the payment lifecycle fraud controls do not stop at approval. They include how you interpret rejection, retry, fallback, and customer recovery behavior too.
Why network knowledge matters for fraud leaders
One of the other strong themes in this episode is learning. Not just formal learning. Real learning. Talking to people. Building context. Understanding how the ecosystem works.
Network knowledge for fraud leaders matters because fraud and payments are both fields where a lot of the useful knowledge lives in the practical details. People who have seen how issuers behave. People who understand processors. People who have worked in travel, subscription, marketplaces, or digital goods. That kind of context is incredibly valuable.
We have seen this playbook before.
The leaders who stay curious usually make better decisions.
Continuous learning in payments is especially important for fraud professionals because the systems keep changing. New payment methods. New orchestration layers. New issuer behavior. New regulatory pressure. New fraud patterns. If your understanding of payments froze five years ago, your fraud strategy is probably missing something important.
What fraud teams should take from this episode
So what should fraud fighters take from this conversation?
First, learn more about payments than your job technically requires. Seriously. That knowledge compounds.
Second, use payment operations for fraud teams as a strategic advantage. The more fraud teams understand processor behavior, issuer responses, and transaction flow, the sharper their decisions tend to be.
Third, build stronger relationships with the payments side of the house. Payment team collaboration is one of those things that pays off over and over again once the trust is there.
A few practical priorities:
- Review what payment data your fraud team is actually using today
- Look at decline patterns as possible fraud intelligence, not just conversion pain
- Map fraud controls to different stages of the payment lifecycle
- Pressure test whether your merchant payment fraud strategy is improving both risk outcomes and payment performance
Because the goal is not just fewer fraud losses. It is a healthier system overall.
Why this episode matters
This episode is really about depth.
Yes, it is a conversation with Scott Engel about payments. But it is also a reminder that good fraud prevention gets better when teams understand the systems around the fraud, not just the fraud itself.
Payments fraud strategy is stronger when it is grounded in payment expertise.
Fraud prevention through payment expertise is more practical than a lot of teams realize.
And the fraud and payments relationship is one of the most important connections in this work.
That is the bigger takeaway.
If you want to make better fraud decisions, understand the payment flow.
If you want to reduce unnecessary friction, understand the payment flow.
If you want to see risk more clearly, understand the payment flow.
Because a lot of the answers fraud teams are looking for are already sitting inside the payments layer. They just are not always looking there yet.
