Overview

When you interact with the Sandbox environment, you'll be able use any of the test users below to simulate different behaviors. No text messages will be sent in this environment and real user information will not validate properly either - you must use the test users.

A few things to note:

• When prompted for your OTP during mobile flow testing, you must use 1234 to simulate a successful OTP. Any other combination of numbers will simulate a failure.
• Use Milo or Martina when testing with Postman or curl because it doesn't require use of the client SDK. Otherwise, the success field of the Validate call will always return false.

Unless specified below, you can introduce failures in the tests that would otherwise be successful:

• If you call a step not specified in the next field (or out of order), you will receive:
  • Status Code: HTTP 403
  • Response: {"code":1003,"message":"step not allowed"}
• If you don't pass in a required field, you will receive:
  • Status Code: HTTP 400
  • Response: {"code":1001,"message":"field 'flowType' is missing"

Steps

These are the steps you'll follow for each of the tests.

• For Start:
  • Send into request:
    • flowType: use either mobile or desktop
    • phoneNumber: (use number from table above)
    • finalTargetUrl: https://www.prove.com
    • either dob or last4SSN (otherwise, pass it in to Challenge request)
  • Response will return:
    • authToken
    • correlationId
    • next = v3-validate
• For Validate:
  • Send into request:
    • correlationId (from Start response)
  • Response will return:
    • success = true
    • challengeMissing = false
    • next = v3-challenge or v3-complete
• For Challenge (only if the previous Validate call returned: next = v3-challenge):
  • Send into request:
    • correlationId (from Start response)
    • either dob or last4SSN (if you didn't pass it into Start request)
  • Response will return:
    • success = true
    • individual information (from table above)
    • next = v3-complete
• For Complete:
  • Send into request:
    • correlationId (from Start response)
    • individual information (from table above)
  • Response will return:
    • success = true
    • changeDetected (true if the data doesn't exactly match what was returned from Challenge response)
    • next = done

Prove Identity with KYC Test Users

Below is the comprehensive list of Prove Identity with KYC/CIP Test Users. Follow the steps above in the UAT environment to test out your implementation to ensure it's working properly.

📘

Test users are only in the Sandbox environment.

Prove Identity with KYC Outcomes and Test Scenarios

The below table provides Prove Identity outcome possibilities including which sandbox users to test with, testing notes and interpretation of each success and failed state in Production. The Prove Identity with KYC Test Users table above contains the comprehensive list of test users including mock data. If you are trying to troubleshoot Success=False in the API response, please see the next section.

Sandbox Troubleshooting Tips

Please see below table for assistance troubleshooting when Success=False in an API response. To understand what this indicates in Production, please see the Prove Identity with KYC Outcomes and Test Scenarios table above.

❗️

If you are encountering errors when running these test scenarios, please refer to the Error and Status Codes page.

If you're still having issues, send us your correlation ID from a failing request. We may be able to provide additional insight after reviewing our logs using either the Support button in the Portal or contacting your account representative.

📘

Self-Serve

For the option, please contact your sales representative.