The testing environment doesn’t send text messages or validate real customer information.
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 | |
|---|---|---|---|---|---|---|---|---|---|
| 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 | |
|---|---|---|---|---|---|---|---|---|---|
| 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.KYC test users
You can test Know Your Customer (KYC) and Customer Identification Program (CIP) functionality 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 | |
|---|---|---|---|---|---|---|---|---|---|
| 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 the steps below to test the Prove Pre-Fill flow with Marcia Longo. This user will pass the entire Pre-Fill flow and return
success=true in the /complete response.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the PII for Marcia Longo.
2
Initiate Start Request
Your front end will send this data to the back end. Your back end will then send the phone number, flow type, and challenge to the /start endpoint. The response will provide an auth token, correlation ID, and the next endpoint to call.
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.
- Mobile Flow
- Desktop Flow
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:
The response provides:
challengeMissing=falsedue to passing the challenge into the /start call.success=truephoneNumberthat was initially passed./v3/challengeas the next endpoint to call.
"success": true, and the next endpoint to call.5
Review PII
The form will be prefilled with the PII returned from the /challenge endpoint. Confirm the provided information without editing it. The back end will then call the /complete endpoint with the correlation ID and you will have a successful flow. Send the user on through your onboarding flow.