Implementation Guide

This guide provides instructions to integrate Prove Unify. Server-side and client-side implementation guides are available. Prove provides server-side SDKs in the following languages: Go, Java, TypeScript, and JavaScript. If you implement using a different back end language, you can interact with the API endpoints.

To integrate the Prove Unify solution, you must use the client-side SDK.

Prove Sandbox Credentials

Before you begin implementing, ensure you have Prove Sandbox credentials from the Developer Portal. To access Sandbox credentials, follow the steps outlined on the Authentication page.

Implementation With the Server-Side SDK

Step	Client-Side	Server-Side
Unify
1	If you need to collect the consumer’s phone number, create a screen to prompt for this information.
2	On submit, the form calls an endpoint on your back end server to pass in the consumer-submitted data. It also passes in the `possessionType` of either `mobile` or `desktop`.
3		Setup the SDK with the OAuth client ID and client secret from Portal to handle authentication for all server-side calls. If you integrate without the server-side SDK, make a call to the `/token` endpoint to generate the OAuth token.
4		Call the server-side SDK `Unify()` function to pass in the data to start the session. The call returns a one-time use `authToken` and a `correlationId`.
5		Save the `correlationId` in your session and then return the `authToken` to your client-side.
6	Setup the authenticator and the associated functions for Instant Link, one-time password (OTP), and Auth Finish Step. The Auth Finish step calls to your back end server which then calls the server-side SDK `Unify-Status()` function.
7	Pass the `authToken` to the client-side SDK `Authenticate()` function. Once the client-side possession completes, the Auth Finish step executes.
Unify-Status
8		Call the server-side SDK `Unify-Status()` function to return the results of the authentication. The Unify-Status response returns `true` or `false` indicating whether the possession check was successful. If the API returns `success=false`, then run your exception process.

Step	Client-Side	Server-Side
Unify
1	If you need to collect the consumer’s phone number, create a screen to prompt for this information.
2	On submit, the form calls an endpoint on your back end server to pass in the consumer-submitted data. It passes in the `possessionType` as `none`.
3		Setup the SDK with the OAuth client ID and client secret from Portal to handle authentication for all server-side calls. If you integrate without the server-side SDK, make a call to the `/token` endpoint to generate the OAuth token.
4		Call the server-side SDK `Unify()` function to pass in the data to start the session. The call returns a one-time use `authToken` and a `correlationId`.
5		Save the `correlationId` in your session and then return the `authToken` to your client-side.
6	Initialize the client-side SDK to place a Prove Key on the device.
Unify-Status
7		Call the server-side SDK `Unify-Status()` function. If this is the first time seeing this phone number, it returns `success=possession_required`.
8	Perform your own possession check using OTP.
Unify-Bind
9		If your possession check succeeds, call the server-side SDK `Unify-Bind()` function with the phone number to initiate the bind and register the Prove Key.
Future Authentication
10	Initialize the client-side SDK to check for an existing Prove Key.
11		Call the server-side SDK `Unify()` function with `possessionType=none` followed by `Unify-Status()`. If the Prove Key is bound to the phone number, `success=true` returns.

Get Started

Prove Pre-Fill®

Prove Identity®

Prove Verified Users

Prove Unify

Stay Informed

Implementation Guide

Prove Sandbox Credentials

Implementation With the Server-Side SDK

Get Started

Prove Pre-Fill®

Prove Identity®

Prove Verified Users

Prove Unify

Stay Informed

​Prove Sandbox Credentials

​Implementation With the Server-Side SDK

Prove Sandbox Credentials

Implementation With the Server-Side SDK