Welcome to the Prove® Platform documentation! This documentation applies only if you use the client-side SDK and Prove® Platform APIs.

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

​
Prove Pre-Fill Solution Overview

The 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, you’ll need the following components:

  • Prove® Platform server-side SDK: You will use the server-side SDK on the backend of your web application.

    • Purpose: The server-side SDK interacts directly with Prove APIs on your backend. It handles OAuth token management and simplifies the request and response handling for the Prove APIs.

    • Supported Languages: Prove provides server SDKs in Java, TypeScript/JavaScript, and Go.

If you are using a different backend language, you can still integrate by easily interacting with the REST APIs.

  • Prove® Platform client-side SDK: You must use one of the client-side SDKs on the frontend of your web, iOS, or Android application.

    • Purpose: The client-side SDK handles all server calls for Mobile Auth, one-time password (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 user experience (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 the 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:

  • If implementing Mobile Auth℠, Prove will complete real-time, MNO-coordinated verification with fallback to SMS OTP to verify a consumer.

  • Otherwise, if implementing without the Mobile Auth add-on, SMS OTP will verify the consumer.

  • For Desktop Channels, it completes 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.

Sign up on the Developer Portal and try Pre-Fill today! Continue to the Implementation Guide for a detailed walk through of next steps.

Implementation Guide