When you interact with the Sandbox environment, use 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.
Use project credentials with sandbox test users only. Attempting to use these test users with different project credentials results 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 | Email |
|---|
2001001695 | Milo | Pinson | 6377 Birchwood Hill | Littleton | CO | 80161-2001 | 1/17/1981 | 847350596 | mpinsonm@dyndns.org |
Prove Pre-Fill test users
Use the following list of test users to test Pre-Fill. Review the Testing Steps for expected behavior per step.
| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | Social Security Number | Email |
|---|
2001001693 | Marcia | Longo | 00 Mallard Park
71 Walton Trail | New Orleans
Memphis | LA
TN | 70165
38150 | 7/19/1982 | 470806227 | mlongok@amazonaws.com |
2001001688 | Nevin | Chattey | 9398 Scott Plaza | Austin | TX | 78744 | 3/20/1980 | 542742985 | nchatteyf@techcrunch.com |
2001001687 | Agretha | Chene | 4861 Jay Junction | Boston | MS | 02208 | 12/29/1994 | 369956933 | achenee@printfriendly.com |
Mobile Auth test users
Use the following list of test users to test Pre-Fill with the Mobile Auth add-on. Review the Testing Steps for expected behavior per step.
| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | Social Security Number | Email |
|---|
5550000000 | Cathee | Simmonett | 49 Moulton Plaza | Athens | GA | 30610 | 10/6/1962 | 771240999 | csimmonettj@toplist.cz |
5555555555 | Van | Moors | 9 Prairie Rose Court | Columbus | MS | 39705 | 1/7/1976 | 409890062 | vmoorsd@rakuten.co.jp |
Know Your Customer test users
You can test Know Your Customer (KYC) and Customer Identification Program (CIP) with the following test users. Review the Testing Steps for expected behavior per step.
| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | Social Security Number | Email |
|---|
2001004004 | Johnnie | Lammiman | 0571 Gale Court | White Plains | NY | 10633 | 12/08/1977 | 111258802 | jlammiman4@xinhuanet.co |
2001004001 | Sebastian | Limmer | 2302 Ronald Regan Park | Dayton | OH | 45470 | 12/23/1977 | 347465324 | slimmer1@canalblog.com |
2001004002 | Leena | Tomashov | 4984 Sage Hill | Saint Louis | MO | 63104 | 5/13/1965 | 115925498 | ltomashov2@joomla.org |
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.
Marcia
Agretha
Nevin
Cathee
Van
Johnnie
Sebastian
Leena
Fail
Follow these steps to test the Prove Pre-Fill flow with Marcia Longo. This user passes the entire Pre-Fill flow and return success=true in the /complete response.Prompt Customer
Start the onboarding flow on the initial screen and enter the PII for Marcia Longo. Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number, flow type, and challenge to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.Send the final target URL if performing a desktop flow.
Send Auth Token to the Front End
Your back end sends the authToken to the front end SDK to do the possession handling.The front end runs OTP handling. Use 1234 to simulate a successful OTP. The front end runs Instant Link handling. 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:
challengeMissing=false due to passing the challenge into the /start call.success=truephoneNumber that was initially passed./v3/challenge as the next endpoint to call.
The back end calls the /challenge endpoint with the correlation ID. The response provides PII for Marcia, "success": true, and the next endpoint to call. Review PII
The form prefills with the PII returned from the /challenge endpoint. Confirm the provided information without editing it. The back end calls the /complete endpoint with the correlation ID to return a successful flow. Send the user on through your onboarding flow. Follow these steps to test the Prove Pre-Fill flow with Agretha Chene. This user falls out of the Pre-Fill flow at the Validate step and returns success=false in the /validate response.Prompt Customer
Start the onboarding flow on the initial screen and enter the PII for Agretha Chene. Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number, flow type, and challenge to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.Send the final target URL if performing a desktop flow.
Send Auth Token to the Front End
Your back end sends the authToken to the front end SDK to do the possession handling.The front end runs OTP handling. Use 1234 to simulate a successful OTP. Agretha fails the authentication due to risk, and the results appear in the next step. The front end runs Instant Link handling. 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.This user fails /validate.{
"next": {
"done": "done"
},
"success": false,
"challengeMissing": false
}
Follow these steps to test the Prove Pre-Fill flow with Nevin Chattey. This user falls out of the Pre-Fill flow at the Validate step and returns success=false in the /validate response.Prompt Customer
Start the onboarding flow on the initial screen and enter the PII for Nevin Chattey. Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number, flow type, and challenge to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.Send the final target URL if performing a desktop flow.
Send Auth Token to the Front End
Your back end sends the authToken to the front end SDK to do the possession handling.The front end runs OTP handling. Enter any number in the front end. Nevin fails the authentication regardless of the number entered, and you see the results in the next step. The front end runs Instant Link handling. 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.This user fails /validate.{
"next": {
"done": "done"
},
"success": false,
"challengeMissing": false
}
Follow these steps to test the Prove Pre-Fill flow with Mobile Auth add-on for Cathee Simmonett. This user fails Mobile Auth on mobile but pass the OTP. This user passes the entire Pre-Fill flow and return success=true in the /complete response.Begin Application
Start the onboarding flow on the initial screen. Prompt the customer to accept the terms and conditions. Initiate Start Request
Pass Cathee’s phone number into Start() due to Sandbox limitations. However, in Production don’t send the phone number into Start() when using Mobile Auth. The client-side SDK prompts for phone number only if Mobile Auth fails.
Send the final target URL if performing a desktop flow.
Send Auth Token to the Front End
Your back end sends the authToken to the front end SDK to do the possession handling.The system fails Mobile Auth and the client-side SDK prompts for the phone number.The front end runs OTP handling. Use 1234 to simulate a successful OTP. The front end runs Instant Link handling. 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:
challengeMissing=true since you didn’t enter challenge data into the /start call.success=truephoneNumber that was initially passed./v3/challenge as the next endpoint to call.
Prompt for Challenge Data
The front end prompts the user with this screen. Enter the PII for Cathee Simmonett. This screen looks different depending on what challenge data you want to receive.The back end calls the /challenge endpoint with the correlation ID and challenge data. The response provides PII for Cathee, "success": true, and the next endpoint to call. Review PII
The form prefills with the PII returned from the /challenge endpoint. Confirm the provided information. The back end calls the /complete endpoint with the correlation ID to return a successful flow. Follow these steps to test the Prove Pre-Fill flow with Mobile Auth add-on for Van Moors. This user passes Mobile Auth on mobile. He passes the entire Pre-Fill flow and return success=true in the /complete response.Begin Application
Start the onboarding flow on the initial screen. Prompt the customer to accept the terms and conditions. Initiate Start Request
Your front end sends data to the back end. Your back end sends an empty phone number and the flow type to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.For this workflow, the SDK collects the phone number rather than passing in the phone number into the /start endpoint. Refer to the Web, Android, or iOS SDK documentation to configure your implementation to handle phone number collection when prompted. Send the final target URL if performing a desktop flow.
Send Auth Token to the Front End
Your back end sends the authToken to the front end SDK to do the possession handling.This user passes Mobile Auth.
If on desktop, the system fails Mobile Auth and the client-side SDK prompts for the phone number.The front end then runs Instant Link handling. 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:
challengeMissing=true since you didn’t enter challenge data into the /start call.success=truephoneNumber that was initially passed./v3/challenge as the next endpoint to call.
Prompt for Challenge Data
The front end prompts the user with this screen. Enter the PII for Van Moors. This screen looks different depending on what challenge data you want to receive.The back end calls the /challenge endpoint with the correlation ID and challenge data. The response provides PII for Van, "success": true, and the next endpoint to call. Review PII
The form prefills with the PII returned from the /challenge endpoint. Confirm the provided information. The back end calls the /complete endpoint with the correlation ID to return a successful flow. Follow the steps to test the Prove Pre-Fill flow with KYC add-on for Johnnie Lammiman. This user passes the entire Pre-Fill flow and returns success=true in the /complete response and returns high MultiCIP and no hits against mock-configured KYC watch lists.Prompt Customer
Start the onboarding flow on the initial screen and enter the PII for Johnnie Lammiman. Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number, flow type, and challenge to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.Send the final target URL if performing a desktop flow.
Send Auth Token to the Front End
Your back end sends the authToken to the front end SDK to do the possession handling.The front end runs OTP handling. Use 1234 to simulate a successful OTP. The front end runs Instant Link handling. 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:
challengeMissing=false due to passing the challenge into the /start call.success=truephoneNumber that was initially passed./v3/challenge as the next endpoint to call.
The back end calls the /challenge endpoint with the correlation ID. The response provides PII for Johnnie, "success": true, and the next endpoint to call. Review PII
The form prefills with the PII returned from the /challenge endpoint. Confirm the provided information. The back end calls the /complete endpoint with the correlation ID to return a successful flow. The response provides KYC and CIP data in the /complete response. This user passes both checks. Follow these steps to test the Prove Pre-Fill flow with KYC add-on for Sebastian Limmer. This user proceeds through the entire Pre-Fill flow. The /complete response returns success=true but also returns 4 simulated hits against KYC watchlists.Prompt Customer
Start the onboarding flow on the initial screen and enter the PII for Sebastian Limmer. Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number, flow type, and challenge to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.Send the final target URL if performing a desktop flow.
Send Auth Token to the Front End
Your back end sends the authToken to the front end SDK to do the possession handling.The front end runs OTP handling. Use 1234 to simulate a successful OTP. The front end runs Instant Link handling. 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:
challengeMissing=false due to passing the challenge into the /start call.success=truephoneNumber that was initially passed./v3/challenge as the next endpoint to call.
The back end calls the /challenge endpoint with the correlation ID. The response provides PII for Sebastian, "success": true, and the next endpoint to call. Review PII
The form prefills with the PII returned from the /challenge endpoint. Confirm the provided information. The back end calls the /complete endpoint with the correlation ID to return a successful flow. The response provides KYC and CIP data in the /complete response. This user fails the KYC check. Send the user through your exception process. Follow these steps to test the Prove Pre-Fill flow with KYC add-on for Leena Tomashov. This user fails the Pre-Fill flow at the Complete step and return multiCIPConfidence=low.Prompt Customer
Start the onboarding flow on the initial screen and enter the PII for Leena Tomashov. Initiate Start Request
Your front end sends this data to the back end. Your back end then sends the phone number, flow type, and challenge to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.Send the final target URL if performing a desktop flow.
Send Auth Token to the Front End
Your back end sends the authToken to the front end SDK to do the possession handling.The front end runs OTP handling. Use 1234 to simulate a successful OTP. The front end runs Instant Link handling. 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:
challengeMissing=false due to passing the challenge into the /start call.success=truephoneNumber that was initially passed./v3/challenge as the next endpoint to call.
The back end calls the /challenge endpoint with the correlation ID. The response provides PII for Leena, "success": true, and the next endpoint to call. Review PII
The form prefills with the PII returned from the /challenge endpoint. Confirm the provided information. The back end calls the /complete endpoint with the correlation ID. The response provides KYC and CIP data in the /complete response. This user fails the Complete step indicating Prove was unable to validate their identity. This user also fails the CIP check. Send the user through a step-up authentication method. Follow these steps to test the Prove Pre-Fill flow with Marcia, Cathee, Van, Johnnie, Sebastian or Leena. This introduces failures into the flow and return success=false at various points.Send Auth Token to the Front End
Your back end sends the authToken to the front end SDK to do the possession handling. During the mobile flow, use 1111 to simulate a failed OTP when presented with the following OTP page.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 test user then fails /validate.{
"next": {
"done": "done"
},
"success": false,
"challengeMissing": false
}
Prompt Customer
Start the onboarding flow on the initial screen and enter the wrong SSN or DOB for the user. 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:
challengeMissing=false due to passing the challenge into the /start call.success=truephoneNumber that was initially passed./v3/challenge as the next endpoint to call.
The back end calls the /challenge endpoint with the correlation ID. The user then fails /challenge. Send the user through the exception process.{
"next": {
"v3-complete": "/v3/complete"
},
"success": false
}
Review PII
When viewing the following page, prefilled with the user’s PII, change the last name.The back end calls the /complete endpoint with the correlation ID and the edited information. The user fails /complete. Send the user through the exception process.{
"next": {
"v3-complete": "/v3/complete"
},
"success": false
}
