Fraud coverage gaps: what happens when the product changes?

TL;DR: BNPL and fintech fraud programs often stay calibrated to an earlier product mix, so when wallets, payouts or cross-border rails launch, synthetic identities and account takeover risks move faster than the coverage map, according to SEON. Lifecycle-aware detection is now a governance problem, not just a model-tuning exercise.

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: What breaks when fraud controls are built for an older product and the business expands?

A: Coverage becomes misaligned with the actual abuse path.

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.

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.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →