Prove Identity Flow
Review this page to achieve a better understanding of of the Server Side, Client Side and UX components required to integrate in addition to a written walk-through of each functions responsibilities.
Prove Identity Solution Overview
Prove Identity® is a modern identity verification solution that combines active phone possession with other consumer-provided information like name and address to authenticate users seamlessly.
Integration Components
In order to implement the Prove Identity solution, you'll need the following components:
- Prove Server-Side SDK: You will use our Server-Side SDK on the backend of your web application.
- Purpose: Our Server-Side SDK interacts directly with Prove APIs on your backend. It handles OAuth token management and simplifies the request and response handling for our Prove APIs.
- Supported Languages: We provide server SDKs in Java, TypeScript/JavaScript, and Go.
If your backend language is not currently supported, you can still integrate our products by easily interacting with our REST APIs
- Prove Link Client-Side SDK: You must use one of our Client-Side SDKs on the frontend of your web, iOS or Android application.
- Purpose: Our client-side SDK handles all server calls for Mobile Auth, OTP, and Instant Link possession checks and handles fallback functionality.
- Web or Native Application: Your application Prove will integrate into
Prove Identity® Flow Diagram
This flow diagram contains a visual representation of the Server Side, Client Side and UX components required to integrate. Please review the written walk-through below this diagram to review each functions responsibilities.
Step-By-Step Responsibilities
Reference these steps to understand each functions responsibilities in the above diagram. If you are looking for a step-by-step comprehensive walk through, please reference our Implementation Guide.
- The Start call generates the OAuth token, initiates the session, and indicates the channel.
- The Client Side SDK initiates the Prove possession check
- For Mobile Channels it includes Mobile Auth℠ for real-time, MNO-coordinated verification with fallback to SMS OTP (One-Time Passcode) to verify a consumer
- For Desktop Channel it includes Instant Link℠ where users click a fortified link within an SMS message
- The Validate call indicates where Prove can successfully authenticate the possession and reputation checks
- The Complete call validates indicates whether Prove can authenticate the ownership
Launch Steps
If you haven't read our Quick Start Guide please start there to review how to start integrating Prove solutions. Otherwise, continue to the Implementation Guide for a detailed walk through.
To go-live with this product, please contact your sales representative.
Updated 7 days ago