Prove Identity Sandbox Testing
Learn more about simulating the Prove Identity flow using the Sandbox environment
When you interact with the Sandbox environment, use test users to simulate different behaviors. Simulate the possession checks using the client-side SDK.
If the system returns an unexpected code, reference the Error and Status Codes page.
After initial short-term testing, implement the client-side SDK and use the remaining test users to test your implementation.
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
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.
Test users list
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.| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | Social Security Number | |
|---|---|---|---|---|---|---|---|---|---|
| 2001004000 | Martina | Goodram | 28965 Homewood Plaza | Little Rock | AR | 72204 | 7/26/1995 | 490959347 | mgoodram0@nasa.gov |
Prove Identity test users
Use the following list of test users to test Prove Identity. For expected behavior per step, review Testing Steps.| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | Social Security Number | |
|---|---|---|---|---|---|---|---|---|---|
| 2001004009 | Benji | Harper | 27 Financial Place | Bakersfield | CA | 93301-2425 | 09/02/1994 | 565252770 | bharperd@superstars.com |
| 2001001698 | Enid | Wildt | 861 Karstens Circle | Washington | DC | 20409 | 6/18/1996 | 212285822 | ewildtp@eepurl.com |
| 2001001699 | Carney | Reinisch | 582 Coleman Point | San Antonio | TX | 78230 | 3/3/2000 | 166521601 | creinischq@php.net |
Mobile Auth test users
Use the following list of test users to test Identity with the Mobile Auth add-on. For expected behavior per step, review Testing Steps.| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | SSN | |
|---|---|---|---|---|---|---|---|---|---|
| 5551111111 | Lena | Lansberry | 663 Stephen Drive | Grand Rapids | MI | 49518 | 3/4/1999 | 657766672 | llansberryk@nbcnews.com |
| 5552222222 | Axe | Summersett | 1823 School Park | Phoenix | AZ | 85025 | 9/24/1963 | 670752404 | asummersettl@boston.com |
Know Your Customer test users
Use the following test users to test the Know Your Customer (KYC) and Customer Identification Program (CIP) feature. This applies if you purchased the KYC add-on. For expected behavior per step, review the Testing Steps. When implementing the KYC add-on, pass in first name, last name, date of birth (DOB), and social security number (SSN) or address. This ensures you receive back the KYC and CIP fields in the /complete response.| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | Social Security Number | |
|---|---|---|---|---|---|---|---|---|---|
| 2001004008 | Maegan | Bertl | 003 Reinke Avenue | Omaha | NE | 68124 | 1/11/1998 | 217174600 | mbertl8@google.com.br |
| 2001004005 | Carrie | Wilding | 8 Helena Street | Milwaukee | WI | 53234 | 8/15/1990 | 657220663 | cwilding5@prweb.com |
| 2001004007 | Nora | Riddich | 160 Daystar Avenue | Philadelphia | PA | 19093 | 08/24/2000 | 760591291 | nriddich7@sina.com.cn |
Testing steps
Now that you’ve done client-side, server-side, and CX implementation, follow the step-by-step instructions to test each test user and ensure your implementation follows expected behavior.Follow the steps below to test the Prove Identity flow with Benji Harper. This user will pass the Identity flow.
1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Benji Harper.
2
Initiate Start Request
Your front end will send this data to the back end. Your back end will then send the phone number and flow type to the /start endpoint. The response will provide an auth token, correlation ID, and the next endpoint to call.
The final target URL must be sent if performing a desktop flow.
3
Send Auth Token to the Front End
Your back end will send the authToken to the front end SDK to do the possession handling.
The front end will run OTP handling. Use 1234 to simulate a successful OTP.
4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /validate endpoint with the correlation ID to authenticate the trustworthiness of the phone number.
The response provides:
success=truephoneNumberthat was initially passed./v3/completeas the next endpoint to call.
5
Prompt Consumer to Input PII
Enter the PII for Benji Harper in the form.
6
Review PII
Confirm the PII in the form. The back end will then call the /complete endpoint with the correlation ID and you will have a successful flow.
correlationId from a failing request. Use either the Support button in the Portal or contact your account representative.
Production AccessFor Production access, contact your sales representative.