• Friendly fraud in agentic commerce: why every buyer gets a new excuse | Ben Herut, Chargeflow
    Nov 14 2026

    Every conversation about agentic commerce ends up at the same question. When an AI agent buys the wrong thing, who pays? I looked into this a while back, and I still don’t have a clean answer. When I landed at Money 20/20 Vegas, I grabbed someone who sees the answer play out in disputes every day.

    Ben Herut is VP of Payments at Chargeflow. We kept this one short. We talk about who is liable, what issuers and merchants need to know when an agent is shopping, why 3D Secure struggles without a human in the loop, and how friendly fraud in agentic commerce could give shoppers a brand new excuse.

    What you’ll hear in this episode:
    • Who is liable for AI agent purchases, and why Visa, Mastercard, and AmEx have not settled it yet
    • Why the AI provider is a new actor in the payment chain, and how BNPL offers a useful liability comparison Why issuers need agentic transaction flagging, and what the payment mandate, card mandate, and intention mandate could provide Why AI agent registration for issuers and merchants matters, and what merchant storefront readiness looks like
    • Why 3D Secure assumes a human in the loop, and what happens when an assistant buys without alerting its owner
    • How first party fraud grows when a shopper can say the AI agent made the mistake
    • Why AI provider security incentives matter, and who is most likely to pay while they stay unclear

    You should listen to this episode if you:
    • Run chargebacks or disputes at a merchant, acquirer, or issuer and want to prepare for agentic commerce
    • Own authentication or 3D Secure flows and are wondering how they hold up when an agent shops
    • Want to understand where liability may land when an AI agent makes a purchase
    • Are planning how to prove what a shopper approved when an agent acted for them

    Mehr anzeigen Weniger anzeigen
    10 Min.
  • Foundation models explained: the tech behind ChatGPT, applied to fraud | Pedro Sanzovo, Plaid
    Nov 7 2026

    Foundation models in fraud are on every conference agenda this year, and I keep hearing the same question. Is this the real thing or the next buzzword? When I landed at Money20/20 Vegas, I wanted to ask someone who builds with them every day.

    Pedro Sanzovo works on identity and fraud products, and has been in fraud his whole career. He started at Palantir, built a fraud company for merchants in Brazil, and sold it to Signifyd, where he led product work on machine learning models. Six months ago he joined Plaid.

    We kept this one short and practical. What is a foundation model, and how is it different from the models most of us run today? Where does it beat XGBoost, and where does it hit the same walls? And what do you do with an embedding when your team writes rules? Pedro had some good answers, and a few things I think you’ll want to hear.

    What you’ll hear in this episode:
    • What a foundation model is, and how transformer models differ from the chained rules and XGBoost models fraud teams have used for years
    • Why legacy models depend on handcrafted features and clean supervised labels, and why that is hard for smaller companies
    • How financial data foundation models treat transactions as a sequence of events and predict what comes next
    • What Pedro means by the precision uplift of up to 34% he is seeing, and why data quality still decides the outcome
    • Why latency constraints, such as 300 milliseconds for card transactions, shape which model belongs where
    • How foundation model explainability compares with XGBoost, and why credit and fraud face different expectations
    • Why embeddings are hard to turn into rules, and how AI agents might help

    You should listen to this episode if you:
    • Lead or work with a fraud data science team and are deciding whether to explore foundation models
    • Run a smaller fraud team and struggle with labeling and feature engineering
    • Want a plain explanation of how foundation models differ from XGBoost
    • Need to weigh precision gains against latency and explainability
    • Are curious how embeddings and AI agents could work together to produce fraud rules

    Mehr anzeigen Weniger anzeigen
    13 Min.
  • AI made building cheap. What are fraud vendors still for? | Netanel Kabala, co-founder @Duly
    Oct 31 2026

    There has always been an arms race in the vendor space, and this year it has been about AI. At the same time, the practitioners I talk with are building far more than they used to. A few weeks ago I spoke with a risk leader who described what her team built in house, and it was impressive. That made me wonder whether the ground is shifting beneath vendors, and whether we will still need them in a year or two.

    I invited Netanel Kabala to help me think it through. Netanel and I met at PayPal 17 years ago, when he started as a fraud analyst after the acquisition of PayPal’s Tel Aviv fraud sciences team. He later co-founded Simplex, the first crypto on-ramp provider, led AI and analytics at Nuvei after the acquisition, and recently co-founded Duly, which helps payment providers and fintechs own their decisioning stack. We look at building vs buying fraud vendors from several angles, including vendor fatigue, what teams build first, and what foundation models and decision models change. We don’t land on a yes or no answer, and I think that’s the honest result. Instead, we sketch where to build, where to buy, and where joint development makes sense.

    What you’ll hear in this episode:
    • Why vendor fatigue is pushing teams to build, and what that means for the vendor relationship
    • Why the most successful in-house builds so far are small tools that save one expert time and don’t replace a whole platform
    • How vendors are shifting from end-to-end solutions toward data providers, with network data and device intelligence valued most by larger teams
    • Why manual review viewers are easy to build with AI coding, and why a rule engine is a very different kind of project
    • How AI slop shows up in risk teams, from dozens of models built overnight to latency and drift monitoring problems nobody planned for
    • What foundation models and decision models change about features, anomaly detection, and who can deploy a real-time fraud model
    • Why segmentation is the best place to start, and why building generic capabilities like KYC or sanction screening is a trap
    • How to judge whether your organization is ready to build, including engineering support, access to risk talent, and leadership buy-in
    • Why the maintenance trap catches analysts who become product manager, DevOps engineer, and backend engineer at once

    You should listen to this episode if you:
    • Lead a fraud or risk team and are deciding what to build and what to keep buying
    • Feel vendor fatigue and want a clearer way to think about which relationships still earn their place
    • Have built something in house with AI and want to know whether it can scale
    • Need to explain to leadership what a build roadmap requires beyond a quick proof of concept
    • Want to know how foundation models and decision models may change the feature layer and vendor data

    Mehr anzeigen Weniger anzeigen
    54 Min.
  • Why Bolt lets some fraud in when it enters a new market | Jaanus Uudmäe, Head of Fraud at Bolt
    Oct 24 2026

    For a couple of years now, Jaanus Uudmäe’s LinkedIn posts have kept showing up in my feed, and they always carry a practical take on what fraud looks like at Bolt. Bolt is an on-demand marketplace headquartered in Estonia that operates in more than 50 countries, with ride hailing, food delivery, scooters, e-bikes, and car rentals. That means his team sees almost every kind of customer and almost every kind of abuse. Jaanus started as a software developer at Skype in 2007 and landed on the fraud team by accident. He joined Bolt in 2017 as a hands-on analyst when the fraud team had two people, and today he has 14 reporting to him.

    In this conversation, we spend most of our time in what I’d call the gray zone. Gray zone fraud is behavior where you can’t tell whether you’re looking at a fraudster, a frustrated customer, or an ordinary person who tried a trick a friend told them about. We talk about refund abuse and bonus abuse, why first time customers are the hardest to judge, and how to build labels when no one hands them to you. We also get into how to explain losses to the business when the numbers aren’t clean, and how Jaanus’s team uses AI in a way that surprised me.

    What you’ll hear in this episode:
    • How Jaanus went from a software developer at Skype to leading a 14 person fraud team at Bolt
    • Why marketplace fraud prevention gets harder in a three sided marketplace with riders, drivers, restaurants, and couriers
    • What gray zone first party fraud looks like in practice, from refund abuse to bonus abuse
    • Why first time customer fraud is the hardest call, and how Bolt decides when to act and when to fall back on standard policy
    • The difference between opportunistic vs professional fraud, and why opportunistic customers make A/B testing unreliable
    • How fraud label manufacturing works when nobody hands you the answers, and how to avoid recursive fraud labeling
    • Why label maturity matters, and which proxy metrics keep a team honest
    • How Bolt thinks about fraud risk appetite and fraud expansion cost when entering a new market
    • How AI works as a context layer for analysts, and why the fraud analyst mindset still matters

    You should listen to this episode if you:
    • Deal with refund abuse or bonus abuse and can’t prove intent
    • Work at a marketplace or on-demand platform with more than two sides
    • Are launching in a new market and need a way to talk about fraud losses with the business
    • Create your own fraud labels and worry about fooling yourself
    • Want to see how a technical fraud team uses AI for analysis without removing human judgment

    Mehr anzeigen Weniger anzeigen
    1 Std. und 5 Min.
  • Fraud rule management: strategy, behavioral and trend rules need different owners and cadences
    Oct 17 2026

    We talk about fraud rules all the time, but I rarely hear anyone ask what we actually mean by the word. What are rules for, who should write them, and how often should they be reviewed? Over the course of my career, I've found that fraud rule types fall into three distinct categories, and most teams manage all of them the same way. That habit quietly costs a lot. Teams end up over-monitoring some rules, under-monitoring others, handing ownership to the wrong people, and expecting rules to perform in ways they were never designed for.

    In this episode, I walk through strategy rules, behavioral rules, and trend rules, and explain how each one is written, measured, and owned. If you manage a rule engine, or you're responsible for how a fraud team spends its time, this is a practical way to organize that work.

    What you'll hear in this episode:
    • Why the three fraud rule types need different monitoring cadences, different owners, and different success criteria
    • How ML score fraud rules and threshold fraud rules segment your population into approve, decline, and step-up groups
    • Why changing one threshold in a strategy ruleset often means adjusting the others, and why those rules should be measured as a set
    • How behavioral rules fraud teams write, including velocity rules fraud examples, can catch several rings with the same MO without overfitting to one attack
    • What compound fraud rules look like in practice, including a device fingerprint fraud rules example that combines email risk, a new device, and a country mismatch
    • Why trend rules are your fastest and most accurate tool at first, and why they degrade so quickly
    • How the fraud rule lifecycle should work, with narrow rules acting as a stopgap while stronger defenses take over
    • What goes wrong with fraud rule prioritization when every rule gets the same attention

    You should listen to this episode if you:
    • Manage a rule engine and want a clear framework for how to write fraud rules that fit their purpose
    • Are building or restructuring a fraud team and need to decide which team should own which rules
    • Want to improve fraud rule deployment by tying strategy rules to your model release process
    • Keep adding narrow rules to stop attacks and are worried about the false positives piling up
    • Rely on a vendor model and need to know what to ask them for when setting thresholds

    Mehr anzeigen Weniger anzeigen
    7 Min.
  • Scaling Agentic AI: Lessons From the Field
    Oct 10 2026

    A few weeks ago I walked through the framework for the AI transformation journey. This conversation with Lalitha Rao, Chief Risk Officer at Imprint, is the natural next step. It is a real, in-the-field look at what it actually takes when a team commits to scaling agentic AI past the theory stage.

    In the nine months since her risk team started building out their agentic AI infrastructure in earnest, they’ve grown their loan book by 150%, increased revenue by 2.5x, and actually lowered loss rates on newer cohorts. All without cutting a single headcount. Lalitha’s team didn’t treat this as a cost-cutting exercise, they treated it as a way to create more value for Imprint's members and partners. And the results speak for themselves.

    If you’re further along in your own AI transformation journey and want a real example of what scaling agentic AI actually looks like once the framework meets the field, this is the conversation.

    What you'll hear in this episode:
    • Why Imprint's centralized AI platform, built by their CTO's team, turned out to matter more than any individual agent they've built
    • How ARIA, an autonomous credit policy agent, scours bureau and internal data to find early signs of portfolio deterioration and pushes the efficient frontier outward instead of just optimizing it
    • Why agentic AI unlocked something a SQL query or a standalone model couldn't, digesting multiple data sources in different formats into one coherent, repeatable workflow
    • How a residual mining agent continuously finds model errors, builds new features, and retrains models using out-of-time testing to guard against overfitting
    • Why Imprint never measured success by headcount reduction, and what they built instead with the team's freed-up time
    • Inside Project Shield, a suite of ten fraud agents that runs for six hours, costs about $300 in tokens, and saves hundreds of thousands of dollars in fraud losses
    • How a shared skills repository and clear data ownership let a non-engineering risk team build and maintain production-grade agents
    • Lalitha's honest build versus buy framework, and the specific vendors, including Sardine, LexisNexis, and Proof, Imprint still relies on
    • The real hiccups Imprint hit along the way, bloated proposals, false certainty in AI-generated reviews, and how they built guardrails to fix both

    You should listen to this episode if you:
    • Are further along in the AI transformation journey and want a concrete look at what scaling actually requires beyond the initial framework
    • Lead a risk, fraud, or credit team and are trying to decide which agentic AI use cases to prioritize first
    • Are weighing build versus buy decisions for AI agents and want a clear mental model for where proprietary data changes the calculus
    • Worry that scaling AI means shrinking your team, and want to hear a real counterexample
    • Want practical detail on how to actually enable non-engineers to build and maintain production-grade AI agents

    Mehr anzeigen Weniger anzeigen
    54 Min.
  • Is It 1st Party Fraud or 3rd Party Fraud?
    Oct 3 2026

    When you get hit by a fraud attack, the second question should be what kind of fraud am I actually dealing with. First party fraud vs third party fraud isn’t just a technical distinction. It fundamentally changes how you respond and what tools you deploy. I’m constantly amazed by how many teams either can’t tell the difference or don’t think it matters.

    This episode is about fixing that.

    What you’ll hear in this episode:
    • The core definitions of first party fraud and third party fraud
    • The specific signals that separate the two in practice
    • Two real, costly examples of teams deploying the wrong tools
    • Why third party fraud may be easier to detect than most people assume and why first party fraud may be harder
    • The specific tool stack each fraud type requires
    • Why most fraud prevention tooling was built around third party fraud by default

    You should listen to this episode if you:
    • Are trying to diagnose a rising fraud rate and aren't sure whether you're facing first party or third party fraud
    • Have invested in KYC identity verification or device fingerprinting fraud tools without seeing the results you expected
    • Are responsible for account takeover detection and want a clearer sense of which signals actually matter
    • Need to make the case internally for fraud prevention ROI by matching the right tool to the right fraud type
    • Are dealing with money mule detection or collusion fraud cases that don't cleanly fit either category

    Mehr anzeigen Weniger anzeigen
    7 Min.
  • Who is the Saturday Fraud Strategist, with Hailey Windham
    Sep 26 2026

    I handed my microphone over to Hailey Windham, host of Fraud Forward. For once, I'm the one answering the questions instead of asking them.

    Hailey opens by asking how I'd describe my mission today, since "builder" doesn't quite cover what I do anymore between advising, educating, and writing. That question sets up the real spine of this conversation. What fraud strategy actually means, why I think predictive fraud analytics is mostly a fabrication, and how a fraud strategist's real job is making sure a team can react well when things break, not pretending anyone can stay ahead of fraudsters.

    Hailey and I talk about where healthy skepticism turns into a blind spot, why foundation models are proving more valuable for enriching data than for scoring transactions, and I close out with real advice for anyone quietly wondering whether they could go independent themselves.

    Mehr anzeigen Weniger anzeigen
    48 Min.