Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.prove.com/llms.txt

Use this file to discover all available pages before exploring further.

Prove Human Assurance solution

Prove Human Assurance helps businesses tell real humans apart from malicious bots in real time, before fraud happens. It passively verifies whether a phone is truly tied to a human device, not a virtual machine, emulator, or IoT SIM. By analyzing phone reputation, activity patterns, and Prove’s proprietary device intelligence, Prove can flag suspicious automation instantly, without adding friction for legitimate customers. The product is aimed at moments that matter—sign-in, signup, or high-risk steps—where you need a timely human-vs-automation read before an attacker racks up abuse or burns trust downstream. Human Assurance is not a complete anti-abuse or bot-management program on its own. It gives you strong phone- and device-centric signals and structured /v3/verify outcomes—including assurance level and policy-related fields—so your application can allow, step up, or block according to your own rules, tooling, and any other signals you combine in real time.

How Human Assurance fits together

At a high level, Human Assurance rests on Authenticate, Verify, and optionally Manage. They describe how the real-time product is structured, not a rigid checklist: your integration may combine or revisit them depending on channel, risk, and whether the customer already has a bound Prove Key. Use Human Assurance Connect during initial implementation to exchange batch files over SFTP and load Human Assurance results for an existing customer base.

Authenticate (possession)

Authenticate means proving possession of the phone number. Your app integrates Prove’s Authenticate SDK (Web, iOS, or Android) so the customer can complete possession on the device. That establishes trust in the device and number before or alongside your server-side checks. End-to-end setup—including how your back end coordinates with Prove—is covered in the Human Assurance Authenticate guide.

Verify

Verify is your back end calling POST /v3/verify with verificationType: "humanAssurance" and the inputs your flow requires. You interpret identity (for example assuranceLevel and reasons against Assurance levels) and evaluation under the Global Fraud Policy alongside authentication outcomes. Step-by-step implementation, response handling, and Sandbox testing are in Human Assurance Verify.

Manage

Manage applies when a verified identity meets Prove’s Global Fraud Policy: it can be enrolled for continuous monitoring of phone and related identity changes. That matters for Human Assurance because automation and takeover risk change when the line or number does—monitoring helps you reassess assurance after the first real-time check. That path is documented under Human Assurance Manage. Webhook notifications for those phone and identity change events are available in the US.