Sandbox Testing
Learn more about simulating the Prove Pre-Fill 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 Pre-Fill with KYC Test Users
Below is the comprehensive list of Prove Pre-Fill with KYC/CIP 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 | |
---|---|---|---|---|---|---|---|---|---|
2001004001 | Sebastian | Limmer | 2302 Ronald Regan Park | Dayton | OH | 45470 | 12/23/1977 | 347465324 | [email protected] |
2001004002 | Leena | Tomashov | 4984 Sage Hill | Saint Louis | MO | 63104 | 5/13/1965 | 115925498 | [email protected] |
2001004004 | Johnnie | Lammiman | 0571 Gale Court | White Plains | NY | 10633 | 12/08/1977 | 111258802 | [email protected] |
2001001687 | Agretha | Chene | 4861 Jay Junction | Boston | MS | 02208 | 12/29/1994 | 369956933 | [email protected] |
2001001688 | Nevin | Chattey | 9398 Scott Plaza | Austin | TX | 78744 | 3/20/1980 | 542742985 | [email protected] |
Test users are only available in the Sandbox environment.
Prove Pre-Fill with KYC Outcomes and Test Scenarios
The below table provides Pre-Fill with KYC outcome possibilities including which sandbox users to test with, testing notes and interpretation of each success and failed state in Production. The Prove Pre-Fill 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.
API Response 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 Pre-Fill with KYC Outcomes and Test Scenarios table above.
Server Side Call | Possible Behaviors Resulting in Success=False | Troubleshooting Tips |
---|---|---|
/start | Not Applicable | Please see Error and Status Codes page for common 400 response errors |
/validate | Client Side SDK Authenticate() function wasn't called or was configured incorrectly* *Required for all sandbox users | See our Client Side SDK implementation guide |
/validate | Wrong one-time passcode (OTP) entered | See our Client Side SDK implementation guide |
/challenge | The phone number entered isn't associated with the SSN/partial or DOB entered (eg you entered Johnnie Lammiman's Phone number with different last4 than test user data) | See Pre-Fill Test User Table for sandbox test user data |
/complete | First Name or Last Name or SSN isn't associated with the phone number entered (eg you entered Johnnie Lammiman's Phone number with different last4) | 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 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 14 days ago