Implementation Guide

This guide provides instructions to integrate Prove Verified Users. Implementation guides for server-side and client-side SDKs 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 Verified Users with possession, use one of the client-side SDKs.

For mobile network operator (MNO) consent information in the following countries, contact your Prove representative:

Canada
The United Kingdom
Germany
France

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 and Testing page.

If implementing in North America and International regions, you need to create two projects. One for Prove Verified Users and one for Prove Verified Users International when generating your Sandbox credentials.

Implementation With the Server-Side SDK

Step	Client-Side	Server-Side
Verify
1	If you need to collect the consumers phone number, first name, or last name, 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`. For `desktop`, pass in the IP address of the client application.
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 `Verify()` 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 `Verify-Status()` function.
7	Pass the `authToken` to the client-side SDK `Authenticate()` function. Once the client-side possession completes, the Auth Finish step executes.
Verify-Status
8		Call the server-side SDK `Verify-Status()` function to return the results of the verification. The Verify-Status response returns `true` or `false` indicating whether the name claimed by an individual is the one who owns the phone number. If the API returns `success=false`, then run your exception process.

Step	Server-Side
Verify
1	Pass in the customers first name, last name, phone number, and optional customer identifier.
2	The Verify response returns `true` or `false` indicating whether the name claimed by an individual is the one who owns the phone number. If the API returns `success=false`, then run your exception process.

Test Your Prove Implementation

Next, reference the Sandbox test scenarios to test users and simulate different behaviors encountered in production.

Launch Steps

Reference the Production Launch Steps to request your production credentials.

Get Started

Prove Pre-Fill®

Prove Identity®

Verified Users

Implementation Guide

Prove Sandbox Credentials

Implementation With the Server-Side SDK

Test Your Prove Implementation

Get Started

Prove Pre-Fill®

Prove Identity®

Verified Users

​Global Consent

​Prove Sandbox Credentials

​Implementation With the Server-Side SDK

​Test Your Prove Implementation

Global Consent

Prove Sandbox Credentials

Implementation With the Server-Side SDK

Test Your Prove Implementation