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 Verified User solution
The Prove Verified User solution helps you compare what your systems know about a consumer—phone, name, and optional attributes—to Prove’s view of that identity drawn from the Prove Identity Network (devices, credentials, and longitudinal phone context), so decisions rest on structured verification outcomes instead of CRM data alone. You can use Verified User to verify existing users in your CRM, validate users before they complete an action on your platform, or at other moments when you need a fresh Prove read on identity tied to a phone number. On the implementation side, you translate successful/v3/verify results and proveId into the trust signals your UX needs (badges, labels, eligibility to list, buy, message, or transact) consistent with your policies.
Typical programs include digital marketplaces, social and dating apps, ticketing and high-value peer-to-peer flows, gig and staffing platforms, live streaming or gaming communities with age or safety rules, and eCommerce flows where impersonation and chargeback risk matter—always with phone-anchored verification at the core.
The underlying idea is to match what you know to Prove-backed identity signals so you can approve, step up, or decline with structured outcomes—not guesswork from stale CRM fields alone. Depending on your program configuration and contract, you can combine Verified User with optional step-up paths (for example additional KYC or sanctions and watchlist screening) so higher-risk segments get more friction without forcing document-first journeys on everyone.
Where policy allows, phone-first verification can also reduce reliance on document-centric identity steps for every user—lowering UX cost compared to always-on document capture, while your own risk team decides when document or liveness paths are still required.
Verified User is not a replacement for your customer master, authorization, or every compliance control. It adds verification results and proveId linkage when checks succeed, which you map into your own policies and workflows.
Verified User is available only in the United States.
How fits together
At a high level, rests on 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.Verify
Verify is your back end callingPOST /v3/verify with the verification type and the inputs your flow requires to obtain a verification result and, when successful, identifiers such as proveId that you can persist for later calls, support, and linking to other Prove capabilities. End-to-end setup, Sandbox testing, and response handling are in the Verify guide.