Welcome to the Prove Link documentation! This documentation applies only if you use our Prove Link frontend SDK and our Prove Link APIs.

For access to our classic documentation, please contact support@prove.com or your Prove representative.

​
Prove Pre-Fill Solution Overview

Our Prove Pre-Fill solution streamlines online form completion by auto-filling verified user information like name and address, while also providing strong identity authentication to prevent fraud. It leads to faster onboarding and reduced friction for users while maintaining a high level of security.

​
Integration Components

In order to implement the Prove Pre-Fill 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 Pre-Fill® 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 the below steps to understand each function’s 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 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

Available for Check Out via Self-Serve!

Please reference our Quick Start Guide to get started.

Was this page helpful?

Implementation Guide