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 Users solution
The Prove Verified Users solution helps you compare what your systems know about a consumer—phone, name, and optional attributes—to Prove’s view of that identity on the network, so decisions rest on structured verification outcomes instead of CRM data alone. You can use Verified Users 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. The underlying idea is to match what you know (for example name, phone, optional attributes such as wallet ID) to Prove-backed identity signals so you can approve, step up, or decline with structured outcomes—not guesswork from stale CRM fields alone. Verified Users is not a replacement for your customer master, authorization, or every compliance control. It adds verification results andproveId linkage when checks succeed, which you map into your own policies and workflows.
Verified Users is available only in the United States.
How Verified Users fits together
At a high level, Verified Users rests on Verify, Connect, and optionally Manage. They describe how the product is structured, not a rigid checklist: you may use real-time checks only, batch only, or both, depending on how you onboard and refresh records.Verify (real time)
Verify is your back end callingPOST /v3/verify with verificationType: "verifiedUser" and the customer attributes your flow requires (for example phone, name, and optional identityAttributes). You interpret identity (including assurance level and reasons) and evaluation under the Global Fraud Policy. End-to-end setup, Sandbox testing, and response handling are in Verified Users Verify.
Connect (batch)
Connect is for batch identity verification over SFTP when you need to process lists of consumers outside a live/v3/verify call—for example large backfills or scheduled jobs. Configuration and file patterns are documented under Verified Users Connect.