When you interact with the Sandbox environment, you’ll be able to 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.
If an unexpected code is returned, reference the Error and Status Codes page.
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 NumberFirst NameLast NameAddressCityStateZipDate of BirthSocial Security NumberEmail
2001001695MiloPinson6377 Birchwood HillLittletonCO80161-20011/17/1981847350596mpinsonm@dyndns.org
After initial short-term testing, implement the client-side SDK and use the remaining test users to test your implementation.

​
Prove Pre-Fill Test Users

Use the following list of test users to test Pre-Fill. Review the Testing Steps below for expected behavior per step.
Phone NumberFirst NameLast NameAddressCityStateZipDate of BirthSocial Security NumberEmail
2001001693MarciaLongo00 Mallard Park

71 Walton Trail		New Orleans



Memphis		LA



TN		70165



38150		7/19/1982470806227mlongok@amazonaws.com
2001001688NevinChattey9398 Scott PlazaAustinTX787443/20/1980542742985nchatteyf@techcrunch.com
2001001687AgrethaChene4861 Jay JunctionBostonMS0220812/29/1994369956933achenee@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 below for expected behavior per step.
Phone NumberFirst NameLast NameAddressCityStateZipDate of BirthSocial Security NumberEmail
5550000000CatheeSimmonett49 Moulton PlazaAthensGA3061010/6/1962771240999csimmonettj@toplist.cz
5555555555VanMoors9 Prairie Rose CourtColumbusMS397051/7/1976409890062vmoorsd@rakuten.co.jp

​
KYC Test Users

You can test Know Your Customer (KYC) and CIP functionality with the following test users. This applies if you purchased the KYC add-on. Review the Testing Steps below for expected behavior per step
Phone NumberFirst NameLast NameAddressCityStateZipDate of BirthSocial Security NumberEmail
2001004004JohnnieLammiman0571 Gale CourtWhite PlainsNY1063312/08/1977111258802jlammiman4@xinhuanet.co
2001004001SebastianLimmer2302 Ronald Regan ParkDaytonOH4547012/23/1977347465324slimmer1@canalblog.com
2001004002LeenaTomashov4984 Sage HillSaint LouisMO631045/13/1965115925498ltomashov2@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.
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.
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:
  • challengeMissing=false due to passing the challenge into the /start call.
  • success=true
  • phoneNumber that was initially passed.
  • /v3/challenge as the next endpoint to call.
The back end will then call the /challenge endpoint with the correlation ID. The response will provide PII for Marcia, "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.
Phone NumberFirst NameLast NameAddressCityStateZipDate of BirthSocial Security NumberEmail
2001004000MartinaGoodram28965 Homewood PlazaLittle RockAR722047/26/1995490959347mgoodram0@nasa.gov
After initial short-term testing, implement the client-side SDK and use the remaining test users to test your implementation. Reference the Quick Start Guide to gather the required components.

​
Prove Identity Test Users

For each of the test users, simulate the flow in the staging environment to test out your implementation to ensure it’s working. Reference the Outcomes Table to review scenarios to test and interpretation of success and failed states.

​
Mobile Flow Testing

When prompted for your one-time password (OTP) during mobile phone flow testing, you must use 1234 to simulate a successful OTP.
Phone NumberFirst NameLast NameAddressCityStateZipDate of BirthSocial Security NumberEmail
2001004009BennyHarper27 Financial PlaceBakersfieldCA93301-242509/02/1994565252770bharperd@superstars.com
2001001699CarneyReinish582 Coleman PointSan AntonioTX782303/3/2000166521601creinischq@php.net
2001001698EnidWilde861 Karstens CircleWashingtonDC204096/18/1996212285822ewildtp@eepurl.com

​
Prove Identity Outcomes and Test Scenarios

The following table provides Prove Identity outcome possibilities including which sandbox users to test with and interpretations of each success and failed state in Production. The Prove Identity Test Users table has the comprehensive list of test users including mock data.

​
Sandbox Troubleshooting Tips

Reference the table for help troubleshooting when success=false in an API response. To troubleshoot an API response in Production, refer to the Prove Identity Outcomes and Test Scenarios.
Server Side CallBehavior Resulting in success=falseTroubleshooting Tips
/startNot ApplicableError and Status Codes page for common 400 response errors
/validateProve Identity Sandbox user intended to fail this step: Carney ReinishTest Scenario Table for which test users fail each scenario
/validateClient-Side SDK Authenticate() function wasn’t called.* * Required for all sandbox users except Martina Goodrum.Client-side SDK implementation guide
/validateWrong OTP enteredClient-side SDK implementation guide
/completeThe First Name, Last Name, or Social Security Number isn’t associated with the phone number entered. You entered Cathy Blažević’s phone number with different last4.Test Scenario Table for which test users fail each scenario
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.
Production AccessFor Production access, contact your sales representative.