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.
Editorial analysis by NHI Mgmt Group, based on content published by Prove Identity: “Case Study: How a Growing Fintech Eliminated Bot Fraud & Made Onboarding Faster and Easier”.
By the numbers:
- The article says Prove Identity serves 2,500+ leading companies.
Key questions
Q: What breaks when bot fraud controls add friction but still miss fake sign-ups?
A: The onboarding funnel breaks because the business pays twice: it loses legitimate users to friction and still funds fraudulent accounts that slip through.
Q: Why do rewards programmes attract more bot fraud in fintech onboarding?
A: Rewards programmes create immediate economic value for attackers, so bots target sign-up paths where fake accounts can capture incentives quickly.
Q: How can teams tell whether onboarding fraud controls are actually working?
A: They should look for falling fake-account creation, lower incentive leakage, fewer bot attempts reaching full registration and less legitimate-user abandonment.
Practitioner guidance
- Define distinct controls for proofing and authentication Map sign-up, first login and repeat access to separate trust decisions so the same check is not forced to cover both account creation and session trust.
- Use behavioural and device reputation signals Incorporate phone tenure, SIM swap history, velocity and device churn into the onboarding risk decision before the account is created.
- Measure friction against bot loss rates Track abandonment, fake-account blocking and rewards leakage together so anti-fraud controls are judged on both protection and conversion.
Bottom line: Bot fraud in onboarding can drain incentives and distort growth metrics even when teams have basic identity checks in place.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
10/07/2026 9:34 pm
Bot fraud is an identity governance problem, not just a fraud problem. Once scripted sign-ups can enter the customer journey, the control question shifts from blocking obvious automation to deciding how much trust to assign at each step. That is why identity verification, authentication and behavioural risk signals need to work as one governance layer, not as disconnected point controls. Practitioners should treat onboarding trust as a lifecycle decision, not a single gate.
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: What is the difference between identity verification and authentication in a digital finance app?
A: Identity verification establishes who a person is by checking evidence such as documents, biometrics, or trusted credentials. Authentication confirms that the same person is present again when they return. In a digital finance app, verification usually happens at onboarding, while authentication protects later sessions, account access, and transaction approvals after identity has already been established.
👉 Read our full editorial: Bot fraud in fintech shows why identity verification still matters