Sandbox Testing
Learn more about simulating the Prove Identity flow using our Sandbox environment.
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 use1234
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, thesuccess
field of the Validate call will always returnfalse
.
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
ordesktop
- phoneNumber: (use number from table above)
- finalTargetUrl: https://www.prove.com
- either dob or last4SSN (otherwise, pass it in to Challenge request)
- flowType: use either
- Response will return:
- authToken
- correlationId
- next = v3-validate
- Send into request:
- For Validate:
- Send into request:
- correlationId (from Start response)
- Response will return:
- success = true
- challengeMissing = false
- next = v3-challenge or v3-complete
- Send into request:
- 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
- Send into request:
- 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
- Send into request:
Prove Identity Test Users
For each of the test users, follow the steps above in the UAT environment to test out your implementation to ensure it's working properly.
Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | SSN | |
---|---|---|---|---|---|---|---|---|---|
2001001682 | Shandee | Alexsandrowicz | 92739 Brown Road | Austin | TX | 78754 | 7/26/1988 | 245766546 | [email protected] |
2001004000 | Martina | Goodram | 28965 Homewood Plaza | Little Rock | AR | 72204 | 7/26/1995 | 490959347 | [[email protected]](mailto:[email protected] |
2001001683 | Cathy | Blazevic | 01 Beilfuss Plaza | Katy | TX | 77493 | 8/6/1992 | 369645267 | [email protected] |
2001001699 | Carney | Reinisch | 582 Coleman Point | San Antonio | TX | 78230 | 3/3/2000 | 166521601 | [email protected] |
2001001698 | Enid | Wildt | 861 Karstens Circle | Washington | DC | 20409 | 6/18/1996 | 212285822 | [[email protected]](mailto:[email protected] |
Test users are only in the Sandbox environment.
Prove Identity 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 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 Outcomes and Test Scenarios table above.
Server Side Call | Behavior Resulting in Success=False | Troubleshooting Tips |
---|---|---|
/start | Not Applicable | Please see Error and Status Codes page for common 400 response errors |
/validate | Prove Identity Sandbox user is intended to fail this step: Carney Reinisch | Please see Test Scenario Table for which test users fail each scenario |
/validate | Client Side SDK Authenticate() function wasn't called or was configured incorrectly* *Required for all sandbox users except Martina Goodram | See our Client Side SDK implementation guide |
/validate | Wrong one-time passcode (OTP) entered | See our Client Side SDK implementation guide |
/complete | First Name or Last Name or SSN isn't associated with the phone number entered (eg you entered Cathy Blazevic's Phone number with different last4) | Please see Test Scenario Table for which test users fail each scenario |
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.
Updated 23 days ago