The testing environment doesn’t send text messages or validate real customer information.
sandbox test users can only be used with project credentials. Attempting to use these test users with different project credentials will result in an unauthorized access error.
Steps
With Possession
With Possession
Follow these steps for each of the tests for
possessionType:desktop
or possessionType:mobile
.-
For Verify:
-
Send into request:
-
possessionType
: use eithermobile
ordesktop
-
firstName
-
lastName
-
phoneNumber
-
finalTargetUrl
: https://www.example.com
-
-
Response returns:
-
correlationId
-
success = pending
-
possessionResult = pending
-
verifyResult = pending
-
-
Send into request:
-
For Verify Status:
-
Send into request:
correlationId
-
Response returns:
-
correlationId
-
success = true
-
possessionResult = success
-
verifyResult = success
-
-
Send into request:
Without Possession
Without Possession
Follow these steps for each of the tests where
possessionType=none
.-
For Verify:
-
Send into request:
-
possessionType
: usenone
-
firstName
-
lastName
-
phoneNumber
-
finalTargetUrl
: https://www.example.com
-
-
Response returns:
-
correlationId
-
success = true
-
possessionResult = not_applicable
-
verifyResult = success
-
-
Send into request:
Short-term test user
Use this test user when performing initial testing with Postman or cURL. This test user skips the client-side SDK authentication to walk you through the sequence of API calls.North America
North America
Phone Number | First Name | Last Name |
---|---|---|
2001004011 | Sheilakathryn | Butrimovich |
International
International
Phone Number | First Name | Last Name |
---|---|---|
447968900002 | Rozella | Kimpton |
Test users for Prove Verified Users
North America
North America
Follow the steps in the Sandbox environment to test out your implementation to ensure it’s working. Reference the Outcomes Table to review scenarios to test and interpret success and failure states.Key points about possession:
-
Mobile Flow Testing: When prompted for your one-time password (OTP) during
mobile
flow testing, you must use1234
to simulate a successful OTP. Any other combination of numbers simulates a failure. - Desktop Flow Testing: Simulate Instant Link during Desktop flow testing.
Phone Number | First Name | Last Name |
---|---|---|
2001004010 | Addy | Epinay |
2001004012 | Kurt | Mathen |
International
International
Follow the steps in the Sandbox environment to test out your implementation to ensure it’s working. Reference the Outcomes Table to review scenarios to test and interpret success and failure states.Key points about possession:
-
Mobile Flow Testing: When prompted for your OTP during
mobile
flow testing, you must use1234
to simulate a successful OTP. Any other combination of numbers simulates a failure. - Desktop Flow Testing: Simulate Instant Link during Desktop flow testing.
Phone Number | First Name | Last Name |
---|---|---|
447302508005 | Wenona | Ransfield |
447568540223 | Janek | Ambrogio |
Prove Verified Users outcomes and test scenarios
The following tables provides outcome possibilities including which sandbox users to test with and interpretations of each success and failed state in Production. The Test Users table has the comprehensive list of test users including mock data.Verified Users With Possession
Verified Users With Possession

Verified Users Without Possession
Verified Users Without Possession

API response troubleshooting tips
Refer to the following table for help troubleshooting whensuccess=false
in an API response. To interpret in Production, refer to the Prove Verified Users Outcomes and Test Scenarios table.
Server Side Call | Possible Behaviors Resulting in success=false | Troubleshooting Tips |
---|---|---|
/verify or /verify-status | Sandbox Users intended to fail this step: Kurt Mathen and Janek Ambrogio | Test Scenario Table for which test users fail each scenario. |
/verify-status | Client-side SDK Authenticate() function wasn’t called. Call this function for all sandbox users except Sheilakathryn Butrimovich, the initial temporary test user. | Client-Side SDK implementation guide |
/verify-status | Wrong OTP entered. | Client-Side SDK implementation guide |
/verify or /verify-status | First Name or Last Name isn’t associated with the phone number entered. You entered the phone number for Addy Epinay or Wenona Ransfield. | Test Scenario Table for which test users fail each scenario |
correlationId
from a failing request. Use either the Support button in the Portal or contact your account representative.
Production AccessFor Production access, contact your sales representative.