Implementation Guide
Review the steps for implementing Pre-Fill
Prerequisites
- Sandbox credentials: Ensure you have Prove Sandbox credentials from the Developer Portal. To access Sandbox credentials, follow the steps outlined on the Authentication page. To access the Prove API, you’ll need to use your OAuth client ID and client secret. You can load these from environment variables or another method:
The OAuth token expires after 60 minutes, requiring you to get another token.
- Server-side SDK: Install the server-side SDK of your choice by running a command in your terminal, or by using a dependency management tool specific to your project.
- Client-side SDK: Install the client-side SDK of your choice by running a command in your terminal, or by using a dependency management tool specific to your project.
To integrate Prove Pre-Fill solutions, you must use the client-side SDKs.
Prove manages a maven repository with Android binaries to enable integration with Gradle.
Update the dependencies object in the build.gradle
file:
You’ll also need to point to the repository by updating your settings.gradle
file with the Maven repository:
The following needs added to the build.gradle
file to also download dependency libraries:
If you receive an error message on the application@fullBackupContent
value, you can resolve it by adding this line of code to your application AndroidManifest.xml
file inside the <application>...</application>
node. Add it as an attribute to the opening application
tag:
The Prove Auth SDK and its children SDKs merge the following permissions into the main application:
Prove manages a repository with the libraries to enable integration.
Execute the following to import CocoaPod from the Prove pod repository:
Implement Prove Pre-Fill
Prompt Customer
Create or update your first screen to prompt for phone number and challenge data.
Create or update your first screen to prompt for phone number and challenge data.
Create or update your first screen to prompt the customer to accept the terms and conditions to use Mobile Auth to verify a customer.
In order for Mobile Auth to succeed:
- Disable VPN.
- Disable Private Relay on iOS.
When testing, you can ignore any Chrome error messages that mention ERR_TUNNEL_CONNECTION_FAILED
- this is due to the VPN, but the SDK fallbacks to OTP.
Determine Type of Flow
You can determine if the customer is on a mobile or desktop browser using this example. If the isMobile
is true, set mobile
as the flowType
for the Start()
function on the server, otherwise you can set desktop
:
You can determine if the customer is on a mobile or desktop browser using this example. If the isMobile
is true, set mobile
as the flowType
for the Start()
function on the server, otherwise you can set desktop
:
When using the Android SDK, set mobile
as the flowType
for the Start()
function on the server.
When using the iOS SDK, set mobile
as the flowType
for the Start()
function on the server.
Initialize the Flow
You need to send a request to your back end server with the phone number, flow type, and an optional challenge to start the flow. This can either be the date of birth or last four digits of the social security number.
You need to send a request to your back end server with the phone number, flow type, and an optional challenge to start the flow. This can either be the date of birth or last four digits of the social security number.
You need to send a request to your back end server with the flow type.
Call the Start Endpoint
On the back end, you’ll start a Prove flow with a call to the Start()
function. This function takes these required parameters:
-
flowType
: eitherdesktop
ormobile
to describe which type of device the customer is starting their flow on. -
finalTargetURL
: required whenflowType=desktop
. It can be either a Prove provided URL or your own URL that instructs the customer to close their mobile browser.
These parameters are optional:
-
ssn
: full or last four digits of the customer’s social security number. You can pass it intoStart()
orChallenge()
. -
dob
: date of birth in one of these formats:YYYY-MM-DD
,YYYY-MM
,MM-DD
. You can pass it intoStart()
orChallenge()
.
The function returns the following fields:
-
authToken
: send this to your client-side code through theAuthenticate()
function - it’s a JSON Web Token (JWT) tied to the current flow and used for the possession checks. It expires after 15 minutes. -
correlationId
: save this in your current session, then pass it in to each of theValidate()
,Challenge()
, andComplete()
function calls of the same flow. The correlation ID ties together different system calls for the same Prove flow. It can aids in troubleshooting. The session expires in 15 minutes from when the correlation ID returns from theStart()
call. -
next
: map of the next API call you need to make.
Return the authToken
in a response to the front end.
Authenticate
Once you have the authToken
, build the authenticator for both the mobile and desktop flows.
Configure OTP
There are two functions to implement for the OTP handling - a start and a finish step. The OTP session has a two minute timeout from when it’s sent through SMS to when the customer can enter in the OTP.
To set the OTP handler, implement withOtpFallback(startStep: OtpStartStep | OtpStartStepFn, finishStep: OtpFinishStep | OtpFinishStepFn)
, OtpStartStep
and OtpFinishStep
. The JavaScript snippet has a simplified example while the TypeScript snippet explains various situations. Ensure you return an object with the field phoneNumber
to the resolve()
function.
Retry functionality is unavailable using OTP.
Call the resolve(input: OtpStartInput)
method to return the collected phone number to the SDK.
If you passed the phone number in the Start()
call, call resolve(null)
to communicate to the SDK you have the customer’s agreement to deliver the SMS OTP message. Ensure you return an object to resolve()
function.
Call the reject("some error message")
method to communicate to the SDK any issues while trying to obtain the phone number. Report an error if the customer cancels the SMS OTP transaction or presses the back button to leave the SMS OTP start step screen.
Call the resolve(result: OtpFinishResult)
method to return the collected OTP value in which result
variable has OnSuccess
value for OtpFinishResultType
and the OTP value wrapped in OtpFinishInput
.
Call the reject("some error message")
method to communicate to the SDK any issues while trying to obtain the OTP value. Report an error if the customer cancels the SMS OTP transaction or presses the back button to exit out of the SMS OTP finish step screen.
Also call the resolve(result: OtpFinishResult)
method to request a SMS OTP message in which the result
variable has OnResendOtp
as value for OtpFinishResultType
. The SDK initiates a OtpStartStep.execute()
call to allow the mobile app to restart the phone number collection logic. You can send up to three OTPs during the same authentication session.
Configure Instant Link
There is one function to configure for Instant Link. The Instant Link session has a three minute timeout from when it’s sent through SMS to when the customer can selects it.
To set the Instant Link handler, withInstantLinkFallback(startStep: InstantLinkStartStep | InstantLinkStartStepFn)
requires implementing the InstantLinkStartStep
interface. The JavaScript snippet has a simplified example while the TypeScript snippet explains various situations. Ensure you return an object with the field phoneNumber
to the resolve()
function.
Call the resolve(input: InstantStartInput)
method to return the collected phone number to the SDK.
If you passed the phone number in the Start()
call, call resolve(null)
to communicate to the SDK you have the customer’s agreement to deliver the SMS OTP message. Ensure you return an object to resolve()
function.
Call the reject("some error message")
method to communicate to the SDK any issues while trying to obtain the phone number. Report an error if the customer cancels the Instant Link transaction or presses the back button to leave the Instant Link start step dialog.
In the desktop flow, a WebSocket opens for three minutes on the desktop browser while waiting for the customer to select the link in the text message. Once clicked, the WebSocket closes and the AuthFinishStep
function finishes.
wss: device.uat.prove-auth.proveapis.com
and wss: device.prove-auth.proveapis.com
.Configure OTP
There are two functions to implement for the OTP handling - a start and a finish step. The OTP session has a two minute timeout from when it’s sent through SMS to when the customer can enter in the OTP.
To set the OTP handler, implement withOtpFallback(startStep: OtpStartStep | OtpStartStepFn, finishStep: OtpFinishStep | OtpFinishStepFn)
, OtpStartStep
and OtpFinishStep
. The JavaScript snippet has a simplified example while the TypeScript snippet explains various situations. Ensure you return an object with the field phoneNumber
to the resolve()
function.
Retry functionality is unavailable using OTP.
Call the resolve(input: OtpStartInput)
method to return the collected phone number to the SDK.
If you passed the phone number in the Start()
call, call resolve(null)
to communicate to the SDK you have the customer’s agreement to deliver the SMS OTP message. Ensure you return an object to resolve()
function.
Call the reject("some error message")
method to communicate to the SDK any issues while trying to obtain the phone number. Report an error if the customer cancels the SMS OTP transaction or presses the back button to leave the SMS OTP start step screen.
Call the resolve(result: OtpFinishResult)
method to return the collected OTP value in which result
variable has OnSuccess
value for OtpFinishResultType
and the OTP value wrapped in OtpFinishInput
.
Call the reject("some error message")
method to communicate to the SDK any issues while trying to obtain the OTP value. Report an error if the customer cancels the SMS OTP transaction or presses the back button to exit out of the SMS OTP finish step screen.
Also call the resolve(result: OtpFinishResult)
method to request a SMS OTP message in which the result
variable has OnResendOtp
as value for OtpFinishResultType
. The SDK initiates a OtpStartStep.execute()
call to allow the mobile app to restart the phone number collection logic. You can send up to three OTPs during the same authentication session.
Configure Instant Link
There is one function to configure for Instant Link. The Instant Link session has a three minute timeout from when it’s sent through SMS to when the customer can selects it.
To set the Instant Link handler, withInstantLinkFallback(startStep: InstantLinkStartStep | InstantLinkStartStepFn)
requires implementing the InstantLinkStartStep
interface. The JavaScript snippet has a simplified example while the TypeScript snippet explains various situations. Ensure you return an object with the field phoneNumber
to the resolve()
function.
Call the resolve(input: InstantStartInput)
method to return the collected phone number to the SDK.
If you passed the phone number in the Start()
call, call resolve(null)
to communicate to the SDK you have the customer’s agreement to deliver the SMS OTP message. Ensure you return an object to resolve()
function.
Call the reject("some error message")
method to communicate to the SDK any issues while trying to obtain the phone number. Report an error if the customer cancels the Instant Link transaction or presses the back button to leave the Instant Link start step dialog.
In the desktop flow, a WebSocket opens for three minutes on the desktop browser while waiting for the customer to select the link in the text message. Once clicked, the WebSocket closes and the AuthFinishStep
function finishes.
wss: device.uat.prove-auth.proveapis.com
and wss: device.prove-auth.proveapis.com
.The cellular data connection can sometimes be unavailable during testing. The Builder
class offers a withTestMode(boolean testMode)
method, which permits simulated successful session results while connected to a Wi-Fi network only (without a cellular data connection available). Testing using a Wi-Fi connection is useful in the Sandbox environment.
The ProveAuth
object is thread safe. You can use it as a singleton. Most Prove Auth methods are blocking and therefore can’t execute in the main application thread. The application employs an executor service with a minimum of two threads to manage threads due to the SDK’s ability to process concurrent blocking requests.
Configure OTP
You need to implement two functions for the one-time password (OTP) handling - a start and a finish step.
You can’t use retry functionality in OTP.
To set the OTP handlers, implement OtpStartStep
and OtpFinishStep
. The Java snippet has an example.
OtpStartStep
example:
OtpFinishStep
example:
In the event a cellular data connection is unavailable during testing, use the Builder class. It permits simulated successful session results while connected to a Wi-Fi network. Testing using a Wi-Fi connection is useful in the Sandbox environment.
The Prove Auth object is thread safe and used as a singleton. Most Prove Auth methods are blocking and therefore can’t execute in the main application thread. The application employs an executor service with a minimum of two threads to manage threads due to the SDK’s ability to process concurrent blocking requests.
Configure OTP
You can implement two functions for the OTP handling - a start and a finish step.
To set the OTP handlers, implement OtpStartStep
and OtpFinishStep
interfaces. The Swift snippet has an example.
Retry functionality is unavailable in OTP.
OtpStartStep
example:
OtpFinishStep
example:
Verify Mobile Number
In the AuthFinishStep
, you’ll specify a function to call once the possession checks complete on the mobile phone. This endpoint on your back end server calls the Validate()
function to validate the phone number. If it was successful, the server returns the results from the Challenge()
function including customer information. Refer to the following example fields that return and then prefill on a form for the customer to verify. The AuthFinishStep
then completes. In the event of cancellation, the server makes a call to the Validate()
function and returns success=false
.
Validate Mobile Phone
Once the possession checks finish on the mobile device, the finish handler on the client-side SDK executes. You then make a request to your server such as POST /verify
to make the next call in the flow to the Validate()
function.
This function requires the Correlation ID which is returned by the Start()
function.
The function returns the following fields:
-
success
: eithertrue
if the mobile number validation was successful, orfalse
if it failed. -
challengeMissing
:true
if you need to pass the challenge into theChallenge()
function. -
phoneNumber
: either the validated phone number or no field. -
next
: map of the next API you need to call you need to make.
The challenge missing field determines if you need to return to the front end and request either the last four of their social security number or date of birth. If the challenge was already passed into the Start()
call, the back end can then make a call to the Challenge()
function and return the results to the front end.
Call the Challenge Endpoint
If the Validate()
function returns v3-challenge
as one of the keys in the Next
field map, call the Challenge()
function to return the customer information matching the mobile number and challenge.
This function requires the Correlation ID which is returned by the Start()
function.
If the Validate()
function returned challengeMissing=true
, send one of these parameters in the request:
-
ssn
: full or last four digits of the customer’s social security number. -
dob
: date of birth in one of these formats:YYYY-MM-DD
,YYYY-MM
,MM-DD
.
The function returns the following fields:
-
success
:true
if customer info returned. -
individual
: customer information in a map. -
next
: map of the next API you need to call you need to make.
If success=true
, return the customer information in a response to the front end to prefill the form.
Verify the Customer Information
Once the customer has made any edits to their prefill information, submit that information to the back end server so the Complete()
call can then verify the customer information.
Call the Complete Endpoint
This function is the final call in the flow that verifies the customer information.
This function takes these required parameters:
-
Correlation ID: this is the ID returned by the
Start()
function. -
Individual: customer information in a map.
The function returns the following fields:
-
Success:
true
if customer information returned. -
Next: map of the next API call you need to make, in this case,
Done
.
You can then respond to the front end with the results of the customer verification.
Test Your Prove Implementation
Next, reference the Sandbox test scenarios to test users and simulate different behaviors encountered in production.
To launch in Production, please contact your Prove representative.