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 below to simulate different behaviors. You will simulate the possession checks utilizing the client-side SDK. No text messages will be sent and real user information will not validate - you must use the test users.
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
Please temporarily use the below test user when performing initial testing with Postman or cURL. This test user intentionally skips the client-side SDK authentication to help you understand the sequence of API calls.
The client-side authentication is a required integration element (it initiates the Prove possession check).
| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | SSN | |
|---|---|---|---|---|---|---|---|---|---|
| 2001004011 | Sheilakathryn | Butrimovich | 0 Mccormick Trail | Pittsburgh | PA | 15205 | 12/9/1974 | 148882298 | sbutrimovichb@who.int |
After initial short-term testing, please implement the Prove client-side SDK and utilize the remaining test users below to fully test your implementation. Please see our Quick Start Guide to better understand required integration components.
Test Users for Prove Verified Users
Below is the comprehensive list of test users. Follow the steps above in the Sandbox environment to test out your implementation to ensure it’s working properly. Please see the Outcomes Table to review scenarios to test and intepret success and failure states.
Key points about possession:
-
Mobile Flow Testing: When prompted for your OTP during
mobileflow testing, you must use1234to simulate a successful OTP. Any other combination of numbers will simulate a failure. -
Desktop Flow Testing: You will simulate Instant Link during Desktop flow testing. You know your logic is set up correctly if your test user passes the Validate step.
| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | SSN | |
|---|---|---|---|---|---|---|---|---|---|
| 2001004010 | Addy | Epinay | 52456 Arizona Street | El Paso | TX | 88553 | 3/3/1995 | 183613702 | aepinaya@jiathis.com |
| 2001004012 | Kurt | Mathen | 95079 Dawn Avenue | Frederick | MD | 21705 | 10/23/1963 | 529375642 | kmathenc@slideshare.net |
Prove Verified Users Outcomes and Test Scenarios
The below tables provides outcome possibilities including which sandbox users to test with, testing notes, and interpretation of each success and failed state in Production. The 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.
API Response Troubleshooting Tips
Please see the below table for assistance troubleshooting when Success=False in an API response. To understand what this indicates in Production, please see the Prove Verified Users Outcomes and Test Scenarios table above.
| Server Side Call | Possible Behaviors Resulting in Success=False | Troubleshooting Tips |
|---|---|---|
| /verify or /verify-status | Sandbox Users intended to fail this step: Kurt Mathen | Please see Test Scenario Table for which test users fail each scenario. |
| /verify or /verify-status | Client-side SDK Authenticate() function wasn’t called or was configured incorrectly. This function is required for all sandbox users except Sheilakathryn Butrimovich (used for initial temporary testing). | See the Client Side SDK implementation guide |
| /verify or /verify-status | Wrong OTP entered. | See our Client Side SDK implementation guide |
| /verify or /verify-status | First Name or Last Name isn’t associated with the phone number entered (you entered Addy Epinay’s Phone number). | Please see Test Scenario Table for which test users fail each scenario |
If you are encountering 400 or 500 response errors when running these test scenarios, please refer to the Error and Status Codes page.
If you’re still having issues, send your correlation ID from a failing request using either the Support button in the Portal or contacting your account representative.
Production Access
To access this functionality in Production, please contact your sales representative.