Notifications
Clear all
Topic starter
10/07/2026 9:12 pm
TL;DR: Spark Wallet said bot fraud was draining rewards spend and slowing onboarding, with fake accounts bypassing earlier identity checks until it used Prove identity verification and authentication tools to block bots and simplify sign-up. The case shows that fraud controls must reduce abuse without creating avoidable customer friction.
NHIMG editorial — based on content published by Prove Identity: How a Growing Fintech Eliminated Bot Fraud and Made Onboarding Faster and Easier
By the numbers:
- Trusted by 2500+ leading companies to reduce fraud and improve consumer experiences, Prove says its platform is used broadly across customer identity workflows.
Questions worth separating out
Q: How should security teams stop bot fraud without hurting onboarding conversion?
A: Use layered identity signals and risk-based challenge steps instead of forcing every user through the same verification path.
Q: Why do rewards and incentive programmes attract bot abuse?
A: Rewards create an immediate financial target, which makes onboarding fraud profitable at scale.
Q: What do teams get wrong about identity verification for bot defence?
A: They often treat identity verification as a one-time gate instead of a continuous trust decision.
Practitioner guidance
- Separate synthetic-account detection from generic onboarding checks Measure bot behaviour against the specific steps where fake accounts enter your funnel, then add controls before rewards, funded actions, or account activation.
- Correlate identity signals before you block or challenge Combine device tenure, phone reputation, velocity, and behavioural patterns into one risk decision rather than relying on a single signal.
- Treat abandonment as a control metric Track completion rate, support contacts, and retry frequency alongside fraud losses so you can see when verification is pushing real users away.
What's in the full article
Prove Identity's full case study covers the operational detail this post intentionally leaves for the source:
- How Spark Wallet configured Prove Pre-Fill, Prove Auth, and Trust Score in its mobile onboarding flow
- The fraud and revenue impact narrative from Spark Wallet's CEO, including how fake-account losses affected incentives
- The practical experience of reducing user friction while keeping bots out of the sign-up journey
- The webinar and consultation path mentioned by Prove for teams evaluating a similar onboarding model
👉 Read Prove Identity's case study on stopping bot fraud in fintech onboarding →
Bot fraud in fintech onboarding: what practitioners need to act on?
Explore further
10/07/2026 9:34 pm
Bot fraud is an identity assurance problem, not just a fraud operations problem. When fake accounts can clear onboarding, the issue is that the trust boundary is too shallow, not that the fraud team is underpowered. Identity verification has to operate as a live control plane across proofing, authentication, and behavioural review. For practitioners, the governance question is whether the programme can stop synthetic identities before they become funded or rewarded accounts.
A question worth separating out:
Q: Who should be accountable when onboarding fraud keeps getting through?
A: Accountability should sit across fraud operations, IAM, and product teams because the failure spans trust, access, and user experience. If only one team owns the control, the programme usually optimises for its own metric and misses the broader risk. Clear ownership prevents blind spots between verification design and abuse response.
👉 Read our full editorial: Bot fraud in fintech shows why identity verification still matters
