Skip to main content
When you interact with the Sandbox environment, use test users to simulate different behaviors. Simulate the possession checks using the client-side SDK.
The testing environment doesn’t send text messages or validate real customer information.
If the system returns an unexpected code, reference the Error and Status Codes page.
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

Follow these steps for each of the tests for possessionType:desktop or possessionType:mobile.
  • For Verify:
    • Send into request:
      • possessionType: use either mobile or desktop
      • firstName
      • lastName
      • phoneNumber
      • finalTargetUrl: https://www.example.com
    • Response returns:
      • correlationId
      • success = pending
      • possessionResult = pending
      • verifyResult = pending
  • For Verify Status:
    • Send into request:
      • correlationId
    • Response returns:
      • correlationId
      • success = true
      • possessionResult = success
      • verifyResult = success
Follow these steps for each of the tests where possessionType=none.
  • For Verify:
    • Send into request:
    • Response returns:
      • correlationId
      • success = true
      • possessionResult = not_applicable
      • verifyResult = success

​
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.
Phone NumberFirst NameLast Name
2001004011SheilakathrynButrimovich
Phone NumberFirst NameLast Name
447968900002RozellaKimpton
After initial short-term testing, implement the Prove client-side SDK and use the remaining test users to test your implementation.

​
Test users for Prove Verified Users

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 use 1234 to simulate a successful OTP. Any other combination of numbers simulates a failure.
  • Desktop Flow Testing: Simulate Instant Link during Desktop flow testing.
Phone NumberFirst NameLast Name
2001004010AddyEpinay
2001004012KurtMathen
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 use 1234 to simulate a successful OTP. Any other combination of numbers simulates a failure.
  • Desktop Flow Testing: Simulate Instant Link during Desktop flow testing.
Phone NumberFirst NameLast Name
447302508005WenonaRansfield
447568540223JanekAmbrogio

​
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.

​
API response troubleshooting tips

Refer to the following table for help troubleshooting when success=false in an API response. To interpret in Production, refer to the Prove Verified Users Outcomes and Test Scenarios table.
Server Side CallPossible Behaviors Resulting in success=falseTroubleshooting Tips
/verify or /verify-statusSandbox Users intended to fail this step:
Kurt Mathen and Janek Ambrogio		Test Scenario Table for which test users fail each scenario.
/verify-statusClient-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-statusWrong OTP entered.Client-Side SDK implementation guide
/verify or /verify-statusFirst 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
If you receive 400 or 500 response errors when running these test scenarios, refer to the Error and Status Codes page. If you still have issues, send your 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.
⌘I