Topic starter
24/10/2026 8:47 pm
TL;DR: Fraud programs can stay aligned to an older product mix even as wallets, payouts and cross-border rails launch, according to SEON. Fraud coverage has to follow the customer journey before new abuse paths outgrow it.
Editorial analysis by NHI Mgmt Group, based on content published by SEON: “Your Fraud Stack Was Built for the Company You Used to Be”.
Key questions
Q: Why does BNPL create more fraud risk than traditional card payments?
A: BNPL creates more fraud risk because approvals are often fast, credit checks are lighter, and customer data collection is limited.
Q: What are the signs that fraud coverage is failing after product expansion?
A: The main signs are familiar controls still reporting healthy numbers while losses begin to show up in new channels, especially payout or stored-value flows.
Q: What breaks when fraud controls are built for an older product and the business expands?
A: Coverage becomes misaligned with the actual abuse path.
Practitioner guidance
- Map fraud coverage to the full customer lifecycle Rebuild coverage maps so onboarding, login, transaction and payout signals are analysed as one sequence, not separate silos.
- Reassess controls before each product launch Require a fraud impact review whenever a new wallet, payout rail, card or balance feature is added, with specific coverage assigned before go-live.
- Retain onboarding evidence for downstream decisions Keep identity, device and behavioural signals available beyond signup so later risk checks can reuse the original trust context.
Bottom line: Fraud controls can look effective while still being misaligned with the actual business if they were built for a previous product set.
Glossary terms: Lifecycle-Aware Fraud Detection, Coverage Drift, Synthetic Identity Fraud, Cash-Out Path
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
25/10/2026 11:11 am
Fraud coverage drift is the real governance failure here. The problem is not that teams lack controls, but that the controls were designed for a product that no longer exists. Once wallets, payouts and card-like balances enter the model, the fraud programme must be re-scoped around the relationship lifecycle rather than the original launch-state. Practitioners should treat control drift as a standing governance risk, not a tuning issue.
A few things that frame the scale:
- U.S. fraud losses are projected to reach $40 billion by 2027.
A question worth separating out:
Q: How should fraud and identity teams coordinate when new payment features go live?
A: They should align pre-launch rather than after the first loss. Fraud, identity and product teams need a shared view of which signals will persist across onboarding, authentication, transaction and payout stages, and which new abuse cases the feature introduces. If the control owner changes but the coverage map does not, the gap will emerge quickly.
👉 Read our full editorial: Fraud coverage gaps emerge when product roadmaps outgrow controls
This post was modified 6 days ago by NHI Mgmt Group