Flow
Review the Flow Diagram for Prove Pre-Fill®.
Introduction
The Prove Pre-Fill® solution can be easily incorporated into your existing applications to support phone-based authentication for pre-filling an application or verifying user identity.
Overview
This guide is designed to help our customers get up to speed quickly on the Prove Pre-Fill® implementation. It covers a series of steps and tools to help implement the Prove flows easily and quickly.
In order to implement the Prove flows, you'll need the following components:
- Prove Server SDK: the SDK you'll use on the backend of your web application.
- Prove Client Web SDK: the SDK you'll use on the frontend of your web application.
- Web Application: the web application to support the Prove flows.
Prove Pre-Fill® Flow
Below is a diagram of the interactions between your web application server and client to complete a Prove flow:
- 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 Challenge call indicates whether Prove can authenticate the consumers identity information with enough trust and assurance. If so, Challenge passes back the consumer's verified identity information
- The Complete call indicates whether Prove can authenticate the ownership
Prove Pre-Fill® Flow Without Mobile Auth
Reference this flow if you do NOT plan to implement Mobile Auth℠ as part of your possession check:
Available for Check Out via Self-Serve!
Please reference our Quick Start Guide to get started.
Updated 3 days ago