Test users list
Short-term test users
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.- North America
- International
| Phone Number | First Name | Last Name |
|---|---|---|
| 2001004018 | Barbaraanne | Canet |
| Phone Number | First Name | Last Name |
|---|---|---|
| +2001004029 | Janos | Martina |
Unified Auth test users
Follow the Testing Steps for expected behavior per step.- North America
- International
| Phone Number | First Name | Last Name |
|---|---|---|
| 2001004014 | Lorant | Nerger |
| Phone Number | First Name | Last Name |
|---|---|---|
| +2001004025 | Bertie | Fremont |
Mobile Auth test users
Follow the Testing Steps for expected behavior per step.- North America
- International
| Phone Number | First Name | Last Name |
|---|---|---|
| 2001004016 | Inge | Galier |
| 2001004017 | Jesse | Mashro |
| Phone Number | First Name | Last Name |
|---|---|---|
| +2001004027 | Allissa | Zoren |
| +2001004028 | Wendy | Strover |
Testing steps
Now that you’ve done client-side, server-side, and CX implementation, test using the test users.- Lorant
- Inge
- Jesse
- Bertie
- Allissa
- Wendy
- Fail
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
Follow the steps below to test the Prove Unified Authentication flow with Lorant Nerger on desktop. This user will pass the entire Unified Authentication flow using Prove’s possession and return
success=true in the /unify-status response.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Lorant Nerger.
2
Initiate Start Request
Your front end will send the phone number, possession type, and final target URL to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the 
authToken to the front end. The front end will run Instant Link handling.4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
proveIdthat is tied to this user.success=truephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Lorant Nerger on mobile. This user will pass Prove’s possession and return
success=true in the /unify-status response. The user can then be sent through the Prove Unified Authentication flow again using the same phone number with a Prove Key.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Lorant Nerger.
2
Initiate Start Request
Your front end will send the phone number and possession type to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the 
authToken to the front end. The front end will run OTP handling. You will see the following page. Enter 1234 to simulate a successful OTP.4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
deviceIdthat’s an external identifier of the Prove ID.proveIdthat is tied to this user.success=truephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Lorant Nerger using customer-supplied possession. This user will pass the entire Unified Authentication flow using the customer’s possession and return
success=true in the /unify-bind response. The user can then be sent through the Prove Unified Authentication flow again using the same phone number with a Prove Key.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Lorant Nerger.
2
Initiate Start Request
Your front end will send the phone number and possession type to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Verify Mobile Number
The back end then calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
success=possession_requiredsince Prove is not performing the possession check.
4
Perform Your Own Possession Check
Perform your own possession check outside of Prove’s system. If the consumer fails, end the flow. If the consumer passes, then proceed to Bind Prove Key.
5
Bind Prove Key
The back end will then call the /unify-bind endpoint with the correlation ID.
The response provides:
proveIdthat is tied to this user.success=truephoneNumberthat was initially passed.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
Follow the steps below to test the Prove Unified Authentication flow with Inge Galier on desktop. This user will pass the entire Unified Authentication flow using Prove’s possession and return
success=true in the /unify-status response.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Inge Galier.
2
Initiate Start Request
Your front end will send the phone number, possession type, and final target URL to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the 
authToken to the front end. The front end will run Instant Link handling.4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
correlationIdthat is tied to this flow.success=truephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Inge Galier on mobile. This user will pass Mobile Auth and return
success=true in the /unify-status response. The user can then be sent through the Prove Unified Authentication flow again using the same phone number with a Prove Key.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Inge Galier.
2
Initiate Start Request
Your front end will send the possession type to the back end. Your back end will then call the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the
authToken to the front end. The front end will run Mobile Auth.4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
deviceIdthat’s tied to the mobile device.proveIdthat’s tied to this customer.phoneNumberthat was discovered by Mobile Auth.success=truephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Inge Galier using customer-supplied possession. This user will pass the entire Unified Authentication flow using the customer’s possession and return
success=true in the /unify-bind response. The user can then be sent through the Prove Unified Authentication flow again using the same phone number with a Prove Key.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Inge Galier.
2
Initiate Start Request
Your front end will send the phone number and possession type to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Verify Mobile Number
The back end then calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
correlationIdthat’s tied to this flow.success=possession_requiredsince Prove is not performing the possession check.phoneNumberthat was initially passed.
4
Perform Your Own Possession Check
Perform your own possession check outside of Prove’s system. If the consumer fails, end the flow. If the consumer passes, then proceed to Bind Prove Key.
5
Bind Prove Key
The back end will then call the /unify-bind endpoint with the correlation ID and phone number.
The response provides:
correlationIdthat’s tied to this flow.success=truephoneNumberthat was initially passed.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
Follow the steps below to test the Prove Unified Authentication flow with Jesse Mashiro on desktop. This user will fail the Unified Authentication flow using Prove’s possession and return
success=false in the /unify-status response.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Jesse Mashru.
2
Initiate Start Request
Your front end will send the phone number, possession type, and final target URL to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the
authToken to the front end. The front end will run Instant Link handling. This user fails Instant Link.4
Fail Possession Check
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
success=falsephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Jesse Mashro on mobile. This user will fail the Unified Authentication flow using Mobile Auth and return
success=false in the /unify-status response.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Jesse Mashro.
2
Initiate Start Request
Your front end will send the phone number and possession type to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the
authToken to the front end. The front end will fail Mobile Auth and OTP without prompting.4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
success=falsephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Jesse Mashro using customer-supplied possession. This user will encounter a server error in the /unify-bind response, simulating an error when creating the Prove key.
1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Jesse Mashro.
2
Initiate Start Request
Your front end will send the phone number and possession type to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Verify Mobile Number
The back end then calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
correlationIdthat’s tied to this flow.success=possession_requiredsince Prove is not performing the possession check.phoneNumberthat was initially passed.
4
Perform Your Own Possession Check
Perform your own possession check outside of Prove’s system. If the consumer fails, end the flow. If the consumer passes, then proceed to Bind Prove Key.
5
Bind Prove Key
The back end will then call the /unify-bind endpoint with the correlation ID and phone number.
You will receive a server error in the response.The user has failed to generate a Prove key. Send the user through your exception process.
Response
Report incorrect code
Copy
Ask AI
{
"code": 8000,
"message": "error at prove, try again later"
}
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
Follow the steps below to test the Prove Unified Authentication flow with Bertie Fermont on desktop. This user will pass the entire Unified Authentication flow using Prove’s possession and return
success=true in the /unify-status response.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bertie Fremont.
2
Initiate Start Request
Your front end will send the phone number, possession type, and final target URL to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the
authToken to the front end. The front end will run Instant Link handling. You will see the following page.4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
proveIdthat is tied to this user.success=truephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Bertie Fremont on mobile. This user will pass Prove’s possession and return
success=true in the /unify-status response. The user can then be sent through the Prove Unified Authentication flow again using the same phone number with a Prove Key.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bertie Fremont.
2
Initiate Start Request
Your front end will send the phone number and possession type to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the
authToken to the front end. The front end will run OTP handling. You will see the following page. Enter 1234 to simulate a successful OTP.4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
deviceIdthat’s an external identifier of the Prove ID.proveIdthat is tied to this user.success=truephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Bertie Fremont using customer-supplied possession. This user will pass the entire Unified Authentication flow using the customer’s possession and return
success=true in the /unify-bind response. The user can then be sent through the Prove Unified Authentication flow again using the same phone number with a Prove Key.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bertie Fremont.
2
Initiate Start Request
Your front end will send the phone number and possession type to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Verify Mobile Number
The back end then calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
correlationIdthat’s tied to this flow.success=possession_requiredsince Prove is not performing the possession check.phoneNumberthat was initially passed.
4
Perform Your Own Possession Check
Perform your own possession check outside of Prove’s system. If the consumer fails, end the flow. If the consumer passes, then proceed to Bind Prove Key.
5
Bind Prove Key
The back end will then call the /unify-bind endpoint with the correlation ID and phone number.
The response provides:
correlationIdthat’s tied to this flow.success=truephoneNumberthat was initially passed.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
Follow the steps below to test the Prove Unified Authentication flow with Allissa Zoren on desktop. This user will pass the entire Unified Authentication flow using Prove’s possession and return
success=true in the /unify-status response.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Allissa Zoren.
2
Initiate Start Request
Your front end will send the phone number, possession type, and final target URL to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the
authToken to the front end. The front end will run Instant Link handling.4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
correlationIdthat is tied to this flow.success=truephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Allissa Zoren on mobile. This user will pass Mobile Auth and return
success=true in the /unify-status response. The user can then be sent through the Prove Unified Authentication flow again using the same phone number with a Prove Key.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number,
+15551111111, for Allissa Zoren.2
Initiate Start Request
Your front end will send the possession type to the back end. Your back end will then call the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the
authToken to the front end. The front end will run Mobile Auth.4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
deviceIdthat’s tied to the mobile device.proveIdthat’s tied to this customer.phoneNumberthat was discovered by Mobile Auth.success=truephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Allissa Zoren using customer-supplied possession. This user will pass the entire Unified Authentication flow using the customer’s possession and return
success=true in the /unify-bind response. The user can then be sent through the Prove Unified Authentication flow again using the same phone number with a Prove Key.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Allissa Zoren.
2
Initiate Start Request
Your front end will send the phone number and possession type to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Verify Mobile Number
The back end then calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
correlationIdthat’s tied to this flow.success=possession_requiredsince Prove is not performing the possession check.phoneNumberthat was initially passed.
4
Perform Your Own Possession Check
Perform your own possession check outside of Prove’s system. If the consumer fails, end the flow. If the consumer passes, then proceed to Bind Prove Key.
5
Bind Prove Key
The back end will then call the /unify-bind endpoint with the correlation ID and phone number.
The response provides:
correlationIdthat’s tied to this flow.success=truephoneNumberthat was initially passed.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
Follow the steps below to test the Prove Unified Authentication flow with Wendy Stover on desktop. This user will fail the Unified Authentication flow using Mobile Auth and return
success=false in the /unify-status response.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Wendy Strover.
2
Initiate Start Request
Your front end will send the phone number, possession type, and final target URL to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the
authToken to the front end. The front end will run Instant Link handling. You will see the following page.4
Fail Possession Check
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
correlationIdthat is tied to this flow.success=falsephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Wendy Strover on mobile. This user will fail Mobile Auth and return
success=false in the /unify-status response.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Wendie Strover.
2
Initiate Start Request
Your front end will send the phone number and possession type to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end will send the
authToken to the front end. The front end will fail Mobile Auth.4
Verify Mobile Number
Once the front end finishes the possession check, the back end calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
correlationIdthat is tied to this flow.success=falsephoneNumberthat was initially passed.
Follow the steps below to test the Prove Unified Authentication flow with Wendie Strover using customer-supplied possession. This user will encounter a server error in the /unify-bind response, simulating an error when creating the Prove key.
1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Wendie Strover.
2
Initiate Start Request
Your front end will send the phone number and possession type to the back end. Your back end will then send the phone number to the /unify endpoint. The response will provide an auth token, correlation ID, and
success=pending because possession still needs to be performed.3
Verify Mobile Number
The back end then calls the /unify-status endpoint with the correlation ID to validate the phone number.
The response provides:
correlationIdthat is tied to this flow.success=possession_requiredsince Prove is not performing the possession check.phoneNumberthat was initially passed.
4
Perform Your Own Possession Check
Perform your own possession check outside of Prove’s system. If the consumer fails, end the flow. If the consumer passes, then proceed to Bind Prove Key.
5
Bind Prove Key
The back end will then call the /unify-bind endpoint with the correlation ID and phone number.
You will receive a server error in the response.The user has failed to generate a Prove key. Send the user through your exception process.
Response
Report incorrect code
Copy
Ask AI
{
"code": 8000,
"message": "error at prove, try again later"
}
Follow the steps below to test the Prove Unified Authentication flow with Laurent, Jesse, Bertie, or Wendie. This will introduce failures into the flow and return
success=false at various points.- Fail Validate (Mobile Flow)
1
Send Auth Token to the Front End
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 /unify-status endpoint with the correlation ID to validate the phone number.The user then fails /unify-status.The Prove flow is terminated and the front end proceeds to another authentication method.
Response
Report incorrect code
Copy
Ask AI
{
"phoneNumber": "2001004017",
"success": "false"
}