Bot Detection Overview

Pain points

Distinguishing between genuine user interactions and those from bots or malicious actors: Digital platforms struggle with this, leading to fraud, compromised user experiences, and higher costs.
Lack of precision in identifying and blocking sophisticated bot attacks: Current solutions often fail to block advanced bot attacks, especially at the top of the funnel. SMS pumping, etc.
Segmenting users to determine what level of verification is required: Businesses need to segment users for various levels of verification and authentication to manage risk and user experience.

Human user segmentation: Accurately distinguishes between human and non-human traffic, enabling tailored user journeys.
Reduced fraud: Minimizes fraud rates by preventing bot-driven attacks and identifying high-risk activity.
Enhanced user experience: Improves the experience for genuine users by reducing friction and unnecessary verification steps.

Field	Field Type	Bot Prevention	Description
`phoneNumber`	`string`	`Required`	The number of the mobile phone. Acceptable characters are: alphanumeric with symbols ’+’.
`phoneNumber` (date last verified)	`string`	`Optional`	The last date that a possession check was completed for a phone number. The format is `YYYY-MM-DD`. Acceptable characters are: numeric with symbol ’-‘
`verificationType`	`string`	`"bot"`	Prove offers different verification methods based on your use case and authorization level required. Available verification methods are: `bot` `verifiedUsers` `prefill prefillForBusiness` `accountOpening` `identityResolution`
`firstName`	`string`	`Optional`	The verified first name of the user.
`lastName`	`string`	`Optional`	The verified last name of the user.
`emailAddress`	`string`	`Optional`	The email address associated with the phone number.