Implementation Guide
Review the steps for implementing Verified Users
Global Consent
The following countries require mobile network operator (MNO) consent to integrate Verified Users. Please contact your Prove representative to discuss requirements.
- Canada
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 Verified Users with Possession, you must use the client-side SDK.
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 Verified Users
Prompt Customer
Create or update your first screen to prompt the customer for phone number, first name, and last name.
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 possessionType
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 possessionType
for the Start()
function on the server, otherwise you can set desktop
:
When using the Android SDK, set mobile
as the possessionType
for the Verify()
function on the server.
When using the iOS SDK, set mobile
as the possessionType
for the Verify()
function on the server.
Call the Verify Endpoint
On the back end, you’ll start a Prove flow with a call to the Verify()
function. This function takes these required parameters:
-
possessionType
: eitherdesktop
ormobile
to describe which type of device the customer is starting their flow on. -
phoneNumber
: the phone number of the customer. -
firstName
: the first name of the customer. -
lastName
: the last name of the customer. -
finalTargetURL
: required whenpossessionType=desktop
. This should be a URL you maintain. Once the customer clicks the Instant Link, they will be redirected to this URL. It should instruct the customer to continue the workflow.
The optional parameters:
-
smsMessage
: a field to customize the message body sent in the Instant Link or OTP SMS message. Otherwise, you can use Prove defaults. -
clientCustomerId
: a client-generated unique ID for a specific customer. You can link calls related to the same customer, across different requests or sessions. The client defines the format of this ID. -
clientRequestId
: a client-generated unique ID for a specific request. You can identify specific requests using this field. You determine the format of this ID.
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 toVerifyStatus()
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 theVerify()
call. -
possessionResult
: will returnpending
since the possession check needs to complete first. -
verifyResult
:pending
since the verification check needs to complete first. -
success
: the result of the combination ofverifyResult
andpossessionResult
. A result ofpending
is returned until the Verify and Possession checks are completed.
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 VerifyStatus()
function to validate the phone number. The AuthFinishStep
then completes.
Validate Possession and Ownership of 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-status
to make the next call in the flow to the VerifyStatus()
function.
This function requires the Correlation ID which is returned by the Verify()
function.
The function returns the following fields:
-
success
: The result of the combination of Verify Result and Possession Result. Possible values aretrue
orfalse
. -
possessionResult
: eithersuccess
if the possession check was successful orfailed
if it failed. -
verifyResult
: eithersuccess
if the verification was successful orfailed
if it failed, ornot_applicable
if possession failed.
You can then respond to the front end with the results of the customer verification.
Prompt Customer
Create or update your first screen to prompt the customer for phone number, first name, and last name.
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 possessionType
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 possessionType
for the Start()
function on the server, otherwise you can set desktop
:
When using the Android SDK, set mobile
as the possessionType
for the Verify()
function on the server.
When using the iOS SDK, set mobile
as the possessionType
for the Verify()
function on the server.
Call the Verify Endpoint
On the back end, you’ll start a Prove flow with a call to the Verify()
function. This function takes these required parameters:
-
possessionType
: eitherdesktop
ormobile
to describe which type of device the customer is starting their flow on. -
phoneNumber
: the phone number of the customer. -
firstName
: the first name of the customer. -
lastName
: the last name of the customer. -
finalTargetURL
: required whenpossessionType=desktop
. This should be a URL you maintain. Once the customer clicks the Instant Link, they will be redirected to this URL. It should instruct the customer to continue the workflow.
The optional parameters:
-
smsMessage
: a field to customize the message body sent in the Instant Link or OTP SMS message. Otherwise, you can use Prove defaults. -
clientCustomerId
: a client-generated unique ID for a specific customer. You can link calls related to the same customer, across different requests or sessions. The client defines the format of this ID. -
clientRequestId
: a client-generated unique ID for a specific request. You can identify specific requests using this field. You determine the format of this ID.
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 toVerifyStatus()
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 theVerify()
call. -
possessionResult
: will returnpending
since the possession check needs to complete first. -
verifyResult
:pending
since the verification check needs to complete first. -
success
: the result of the combination ofverifyResult
andpossessionResult
. A result ofpending
is returned until the Verify and Possession checks are completed.
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 VerifyStatus()
function to validate the phone number. The AuthFinishStep
then completes.
Validate Possession and Ownership of 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-status
to make the next call in the flow to the VerifyStatus()
function.
This function requires the Correlation ID which is returned by the Verify()
function.
The function returns the following fields:
-
success
: The result of the combination of Verify Result and Possession Result. Possible values aretrue
orfalse
. -
possessionResult
: eithersuccess
if the possession check was successful orfailed
if it failed. -
verifyResult
: eithersuccess
if the verification was successful orfailed
if it failed, ornot_applicable
if possession failed.
You can then respond to the front end with the results of the customer verification.
Gather Customer Data
Gather your customer data for phone number, first name, and last name from your CRM.
Call the Verify Endpoint
On the back end, you’ll start a Prove flow with a call to the Verify()
function. This function takes these required parameters:
-
possessionType
:none
to indicate you are using your own possession. -
phoneNumber
: the phone number of the customer. -
firstName
: the first name of the customer. -
lastName
: the last name of the customer.
The optional parameters:
-
clientCustomerId
: a client-generated unique ID for a specific customer. You can link calls related to the same customer, across different requests or sessions. The client defines the format of this ID. -
clientRequestId
: a client-generated unique ID for a specific request. You can identify specific requests using this field. You determine the format of this ID.
The function returns the following fields:
-
correlationId
: the correlation ID ties together different system calls for the same Prove flow. It can aid in troubleshooting. -
success
:true
if the flow succeeded,false
if it failed. -
possessionResult
:not_applicable
to indicate you are using your own possession. -
verifyResult
: eithersuccess
if the verification was successful,failed
if it failed.
You can then respond to the front end with the results of the customer verification.
Webhook Notifications
Webhook notifications are only available for US-based phone numbers.
Configure webhooks to receive change events notifications for previously verified, enrolled customers.
Here’s how to get these webhook notifications up and running:
Access the Portal
Login to the Portal.
Find Your Project
Navigate to your Verified Users project.
Configure Webhook
Using the Configure tab, select the Configure button next to the Sandbox webhook. You will be presented with a screen that looks like this:
Enter the URL of your webhook endpoint and select Save and Test Webhook. This will save your configuration and send a test webhook to the URL you provided.
If you would like a sample URL to test, you can use Webhook.site to generate a unique URL for testing.
Authenticate Webhook
The webhook URL must be authenticated using Prove’s JWT secret. The JWT is a synchronous JWT using HS256 (synchronous algorithm).
This secret is used to sign the JWT token that Prove sends with the webhook notifications. Open the webhook configuration and add the appropriate code snippet to your server-side implementation, replacing whsec_your_secret
with the secret provided by the Portal.
The secret value is autogenerated when the appropriate URL is entered and you select Save and Test Webhook or Configure Webhook.
Parse the Webhook Payload
The following snippet shows an example of each type of change event you could receive from Prove. Each notification will come as an array of event objects.
Access Production
Once you have successfully tested the webhook and finished your implementation, configure and test your production webhook URL. This will allow you to receive notifications for live events.
-
Prove will not send retroactive notifications that occur before the webhook is configured.
-
By nature of each change event, an event triggering for an
identityId
will result in no further notifications for that identity.In the event your customer provides an updated phone number, we’d recommend initiating a new verification with the updated identity information. If verification is successful, Prove will monitor the updated phone number.
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.