TL;DR: 56% month over month in non-live fraud shows AI-driven retail attacks shifting the mix, from Pindrop telemetry. Retail verification now has to weigh behavioural patterns and repeat workflows, not just a single credential check.
Editorial analysis by NHI Mgmt Group, based on content published by Pindrop: “Retail saw a 330% increase in AI fraud in 60 days”.
By the numbers:
- Among Pindrop customers in retail, there was a 56% month-over-month increase in non-live fraud in November.
- Live fraud dropped by 69% in the same period among Pindrop retail customers.
Key questions
Q: Why do passwords, KBAs and OTPs struggle against synthetic customer behaviour?
A: Those controls answer a narrow question about proof at a single moment.
Q: How can teams tell whether AI-assisted fraud is becoming a practical problem?
A: Look for faster campaign iteration, more personalised impersonation, and higher retry volume across email, chat, and support channels.
Q: What breaks when retail fraud becomes automated and AI-assisted?
A: Manual review, threshold-based approval and one-time verification all become easier to game when attackers can vary requests and repeat them at machine speed.
Practitioner guidance
- Tighten return-workflow controls Add velocity limits, anomaly scoring and step-up review on refund and return flows that can be scripted at scale.
- Instrument behavioural fraud signals Correlate device reputation, request timing, session reuse and customer journey deviations to spot AI-generated abuse earlier.
- Revisit low-friction verification points Review where passwords, KBAs and OTPs are being treated as sufficient proof in high-risk retail journeys.
Bottom line: AI-driven retail fraud now scales through normal-looking workflows, which makes behavioural verification as important as credential checks.
Glossary terms: AI-Enabled Fraud, Non-live Fraud, Return Fraud, Deepfake-based impersonation
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
AI fraud is now a workflow problem, not just a verification problem. The article shows attackers using bots and AI to imitate ordinary customer behaviour, which means the control failure sits inside retail processes rather than only at login. That shifts the governance question from “did the customer authenticate” to “did the transaction behave like a genuine customer journey.” Identity teams should treat behavioural consistency as part of assurance, not a separate fraud layer.
A few things that frame the scale:
- Nearly 60% of companies reported that fraud losses were still increasing in 2025.
A question worth separating out:
Q: Should organisations treat deepfake fraud as a fraud team issue or an identity governance issue?
A: Both, but the governance owner needs to be identity because the control failure happens at verification time. Fraud teams can tune detection, yet identity leaders must define the assurance threshold, the escalation path, and the evidence required before trust is granted.
👉 Read our full editorial: AI-enabled retail fraud is scaling past legacy checks