Sandbox Testing
Learn more about simulating the Prove Verified Users flow using the Sandbox environment
Overview
When you interact with the Sandbox environment, you’ll be able use the 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.
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.
Unless specified below, you can introduce failures in the tests that would otherwise be successful:
-
If you call a step out of order, you will receive:
-
Status Code: HTTP 403
-
Response:
{"code":1003,"message":"step not allowed"}
-
-
If a required field is missing, you will receive:
-
Status Code: HTTP 400
-
Response:
{"code":1001,"message":"field 'flowType' is missing"}
-
Steps
Short-Term Test User
After initial short-term testing, implement the Prove client-side SDK and use the remaining test users to test your implementation. Refer to the Quick Start Guide to gather the required integration components.
Test Users for Prove Verified Users
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 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 |
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.
For Production access, contact your sales representative.