Documentation Index
Fetch the complete documentation index at: https://developer.prove.com/llms.txt
Use this file to discover all available pages before exploring further.
Scope
This page lists Sandbox test users for Prove Identity and documents expected requests, responses, and flow outcomes in that environment. Rules in the intro above (no live SMS, credential pairing, and so on) apply here as well.
Desktop flows: For flowType=desktop, POST /v3/start must include a final target URL (not repeated at every step below).
Test users list
Short-term test user
Use with cURL or Postman to exercise the HTTP sequence without the client-side SDK. Use the personas below for SDK-backed end-to-end tests.
| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | Social Security Number | Email |
|---|
2001004000 | Martina | Goodram | 28965 Homewood Plaza | Little Rock | AR | 72204 | 7/26/1995 | 490959347 | mgoodram0@nasa.gov |
Prove Identity test users
Standard Identity personas.
| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | Social Security Number | Email |
|---|
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
Personas for Identity with the Mobile Auth add-on.
| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | Social Security Number | Email |
|---|
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
For the KYC add-on (including CIP fields in responses).
KYC add-on: POST /v3/complete requests must include first name, last name, DOB, and SSN (or address) for KYC and CIP fields to be returned.
| Phone Number | First Name | Last Name | Address | City | State | Zip | Date of Birth | Social Security Number | Email |
|---|
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.
Benji
Enid
Carney
Lena
Axe
Maegan
Carrie
Nora
Fail
Follow these steps to test the Prove Identity flow with Benji Harper. This user passes the Identity flow.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Benji Harper.
Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number and flow type to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.
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 simulates 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:
success=truephoneNumber that was initially passed.evaluation: authentication and risk results; failure reason codes in Global fraud policy./v3/complete as the next endpoint to call.
Prompt Consumer to Input PII
Enter the PII for Benji Harper in the form.
Review PII
Confirm the PII in the form. The back end calls the /complete endpoint with the correlation ID to return a successful flow.
Follow these steps to test the Prove Identity flow with Enid Wildt. This user passes the Identity flow.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Enid.
Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number and flow type to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.
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 simulates 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:
success=truephoneNumber that was initially passed.evaluation: authentication and risk results; failure reason codes in Global fraud policy./v3/complete as the next endpoint to call.
Prompt Consumer to Input PII
Enter the PII for Enid Wildt in the form.
Review PII
Confirm the PII in the form. The back end calls the /complete endpoint with the correlation ID to return a successful flow.
Follow these steps to test the Prove Identity flow with Carney Reinisch. This user falls out of the Identity 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 phone number for Carney.
Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number and flow type to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.
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 simulates 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
}
Follow these steps to test the Prove Identity flow with Mobile Auth add-on for Lena Lansberry. This user passes the Identity flow using Mobile Auth.Prompt Customer
Start the onboarding flow on the initial screen and prompt to accept consent.
Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number and 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 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 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:
success=truephoneNumber that was initially passed.evaluation: authentication and risk results; failure reason codes in Global fraud policy./v3/complete as the next endpoint to call.
Prompt Consumer to Input PII
Enter the PII for Lena Lansberry in the form.
Review PII
Confirm the PII in the form. The back end calls the /complete endpoint with the correlation ID to return a successful flow.
Follow these steps to test the Prove Identity flow with Mobile Auth add-on for Axe Summersett. This user fails Mobile Auth, falls back to OTP, and passes the overall Prove Identity flow.Prompt Customer
Start the onboarding flow on the initial screen and prompt to accept consent.
Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number and flow type to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.Axe’s phone number needs to be passed into Start() due to Sandbox limitations. However, in Production this isn’t necessary. The client-side SDK prompts for phone number only if Mobile Auth fails. Refer to the Web, Android, or iOS SDK documentation to configure your implementation to handle phone number collection when prompted.
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.
If on desktop, the system fails Mobile Auth and the client-side SDK prompts for the phone number. 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:
success=truephoneNumber that was initially passed.evaluation: authentication and risk results; failure reason codes in Global fraud policy./v3/complete as the next endpoint to call.
Prompt Consumer to Input PII
Enter the PII for Axe Summersett in the form.
Review PII
Confirm the PII in the form. The back end calls the /complete endpoint with the correlation ID to return a successful flow.
Follow these steps to test the Prove Identity flow with KYC add-on for Maegan Bertl. This user passes the Identity flow with high multiCIP KYC/CIP data.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Maegan Bertl.
Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number and flow type to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.
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 simulates 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:
success=truephoneNumber that was initially passed./v3/complete as the next endpoint to call.
Prompt Consumer to Input PII
Enter the PII for Maegan Bertl in the form.
Review PII
Confirm the PII in the form. The back end calls the /complete endpoint with the correlation ID to return a successful flow. The response provides simulated KYC and CIP results in the response. This user passes both checks.
Follow these steps to test the Prove Identity flow with KYC add-on for Carrie Wilding. This user passes the Identity flow but also returns 4 simulated hits against KYC watchlists.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Carrie Wilding.
Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number and flow type to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.
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 simulates 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:
success=truephoneNumber that was initially passed./v3/complete as the next endpoint to call.
Prompt Consumer to Input PII
Enter the PII for Carrie Wilding in the form.
Review PII
Confirm the PII in the form. The back end calls the /complete endpoint with the correlation ID to return a successful flow. The response returns KYC and CIP data. This user fails the KYC check. Send the user through your exception process.
Follow these steps to test the Prove Identity flow with KYC add-on for Nora Riddich. This user fails the Identity flow at the Complete step and returns multiCIPConfidence=low.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Nora Riddich.
Initiate Start Request
Your front end sends this data to the back end. Your back end sends the phone number and flow type to the /start endpoint. The response provides an auth token, correlation ID, and the next endpoint to call.
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 simulates 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:
success=truephoneNumber that was initially passed./v3/complete as the next endpoint to call.
Prompt Consumer to Input PII
Enter the PII for Nora Riddich in the form.
Review PII
Confirm the PII in the form. The back end calls the /complete endpoint with the correlation ID to return a successful flow. The response returns KYC and CIP data. 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 Identity flow with Benji, Carney, Enid, Axe, Maegan, Carrie, or Nora. 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 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
}
Review PII
When viewing the PII page, 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
}
