Sandbox Testing
Learn more about simulating the Prove Unify 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.
Prove Unify sandbox test users can only be used with Prove Unify 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
Use this test user when performing initial testing with cURL or Postman. This test user skips the client-side SDK authentication to walk you through the sequence of API calls.
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 Unify
API Response Troubleshooting Tips
Refer to the following table for help troubleshooting when success=false in an API response.
| Server Side Call | Possible Behaviors Resulting in success=false | Troubleshooting Tips |
|---|---|---|
/unify-status | Client-side SDK Authenticate() function wasn’t called. Call this function for all sandbox users except user 2001004018/+2001004029, the initial temporary test user. | Client-Side SDK implementation guide |
/unify-status | Wrong OTP entered. | For successful OTP in Sandbox, use code 1234. Any other code simulates a failure. |
/unify-bind | Your possession check failed, or the phone number doesn’t match the test user. | Verify the phone number matches one of the test users in the provided table. |
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.