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.
Prerequisites
- Sandbox access — Prove Sandbox credentials and environment configuration from the Prove Portal.
- Access token — Obtain a bearer token using Prove OAuth (Authentication) for
POST /v3/unify,POST /v3/unify-status, andPOST /v3/unify-bind. - Implementation — Complete client and server integration using Unified Authentication implementation guide.
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. These users allow you to test “Prove Possession” and “Customer-Supplied Possession with Force Bind” flows.- North America
- International
| Phone Number | First Name | Last Name |
|---|---|---|
| 2001004014 | Lorant | Nerger |
| 2001004015 | Laney | Dyball |
| Phone Number | First Name | Last Name |
|---|---|---|
| +2001004025 | Bertie | Fremont |
| +2001004026 | Bonnie | Sidon |
Mobile Auth test users
Follow the Testing Steps for expected behavior per step. These users allow you to test “Prove Possession” and “Prove Passive Authentication with Customer-Supplied Possession Fallback” flows.- North America
- International
| Phone Number | First Name | Last Name |
|---|---|---|
| 2001004016 | Inge | Galier |
| 2001004017 | Jesse | Mashro |
| 2001004041 | Penny | Jowers |
| Phone Number | First Name | Last Name |
|---|---|---|
| +2001004027 | Allissa | Zoren |
| +2001004028 | Wendy | Strover |
| +2001004043 | Amii | Porritt |
Testing steps
Now that you’ve done client-side, server-side, and CX implementation, test using the test users.- Lorant
- Laney
- Inge
- Jesse
- Penny
- Bertie
- Bonnie
- Allissa
- Wendy
- Amii
- Fail
- Prove Possession - Mobile
- Customer-Supplied Possession with Force Bind
- Prove Possession - Desktop
Follow these steps to test the Prove Unified Authentication flow with Lorant Nerger on mobile. This user passes Prove’s possession and return
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Lorant Nerger.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the 
authToken to the front end. The front end runs OTP handling. Enter 1234 to simulate a successful OTP.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, deviceId, and phoneNumber in Sandbox. See POST /v3/unify-status for the full response.You have a successful flow and a Prove key for this phone number. Sending this user through again bypasses the possession check due to the Prove key. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Lorant Nerger using customer-supplied possession. This user passes the entire Unified Authentication flow using the customer’s possession and return
success=true in the /unify-bind response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Lorant Nerger.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Verify Mobile Number
The back end then calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=possession_required (Prove is not performing the possession check). See POST /v3/unify-status.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.
Bind Prove Key
The back end calls
POST /v3/unify-bind with the correlation ID.
Expect success=true, proveId, and phoneNumber in Sandbox. See POST /v3/unify-bind for the full response.You have a successful flow and a Prove key for this phone number. Sending this user through again bypasses the possession check due to the Prove key. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Lorant Nerger on desktop. This user passes the entire Unified Authentication flow using Prove’s possession and return
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Lorant Nerger.
Initiate Start Request
Your front end sends the phone number, possession type, and final target URL to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the 
authToken to the front end. The front end runs Instant Link handling.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, and phoneNumber in Sandbox (no Prove Key on desktop). See POST /v3/unify-status.The system completes the flow successfully but omits a Prove Key because it only applies to mobile devices. Send the user on through your authenticated flow.- Prove Possession - Mobile
- Customer-Supplied Possession with Force Bind
- Prove Possession - Desktop
Follow these steps to test the Prove Unified Authentication flow with Laney Dyball on mobile. This user fails Prove’s possession and return
success=false in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Laney Dyball.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs OTP handling. Enter 1111 to simulate an unsuccessful OTP.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=false and phoneNumber. See POST /v3/unify-status.The test user failed. Send the user through your exception process.Follow these steps to test the Prove Unified Authentication flow with Laney Dyball using customer-supplied possession. Treat this user as a fail case and assume they fail your possession check. This user receives
success=possession_required on /unify-status. You then proceed to run your possession. They fail out of the flow.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Laney Dyball.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Verify Mobile Number
The back end then calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=possession_required (Prove is not performing the possession check). See POST /v3/unify-status.Follow these steps to test the Prove Unified Authentication flow with Laney Dyball on desktop. This user fails the Unified Authentication flow using Prove’s possession and return
success=false in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Laney Dyball.
Initiate Start Request
Your front end sends the phone number, possession type, and final target URL to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Instant Link handling.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=false and phoneNumber. See POST /v3/unify-status.The test user failed. Send the user through your exception process.- Prove Possession - Mobile
- Prove Passive Authentication with Customer-Supplied Possession Fallback
- Prove Possession - Desktop
Use this procedure to test the Prove passive authentication with customer-supplied possession fallback flow with Inge Galier on mobile. This user passes Mobile Auth and returns
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Inge Galier.
Initiate Start Request
Your front end sends the possession type to the back end. Your back end calls the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Mobile Auth.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, deviceId, and phoneNumber from Mobile Auth in Sandbox. See POST /v3/unify-status for the full response.You have a successful flow and a Prove key tied to this phone number. Sending this user through again bypasses the possession check due to the Prove key. Send the user on through your authenticated flow.Use this procedure to test the Prove passive authentication with customer-supplied possession fallback flow with Inge Galier on mobile. This user passes Mobile Auth and returns
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Inge Galier.
Initiate Start Request
Your front end sends the possession type to the back end. Your back end calls the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Mobile Auth.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, deviceId, and phoneNumber from Mobile Auth in Sandbox. See POST /v3/unify-status for the full response.You have a successful flow and a Prove key tied to this phone number. Sending this user through again bypasses the possession check due to the Prove key. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Inge Galier on desktop. This user passes the entire Unified Authentication flow using Prove’s possession and returns
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Inge Galier.
Initiate Start Request
Your front end sends the phone number, possession type, and final target URL to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Instant Link handling.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, and phoneNumber in Sandbox (no Prove Key on desktop). See POST /v3/unify-status.The system successfully runs the flow but excludes the Prove key because it only applies to mobile devices. Send the user on through your authenticated flow.- Prove Possession - Mobile
- Prove Passive Authentication with Customer-Supplied Possession Fallback
Use this procedure to test the Prove passive authentication with customer-supplied OTP fallback flow with Jesse Mashro on mobile. This user fails the Unified Authentication flow using Mobile Auth and return
success=false in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Jesse Mashro.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end fails Mobile Auth and OTP without prompting.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=false and phoneNumber. See POST /v3/unify-status.The test user failed. Send the user through your exception process.Follow these steps to test the Prove Unified Authentication flow with Jesse Mashro on mobile. This user fails the Unified Authentication flow using Mobile Auth and return
success=false in the /unify-status response.Follow this flow when testing Prove passive authentication with customer-supplied possession fallback.
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Jesse Mashro.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end fails Mobile Auth and OTP without prompting.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=false and phoneNumber. See POST /v3/unify-status.The test user failed. Send the user through your exception process.If you are testing the reputation check flow by sending
checkReputation=true in the /unify request, Penny fails the reputation check and returns success=false in the final response.- Prove Possession - Mobile
- Prove Passive Authentication with Customer-Supplied Possession Fallback
- Prove Possession - Desktop
Follow these steps to test the Prove Unified Authentication flow with Penny Jowers on mobile. This user fails Mobile Auth but passes OTP and returns
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Penny Jowers.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end attempts Mobile Auth, which fails. The SDK then falls back to OTP handling. Enter 1234 to simulate a successful OTP.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, deviceId, and phoneNumber in Sandbox. See POST /v3/unify-status for the full response.You have a successful flow and a Prove key tied to this phone number. Sending this user through again bypasses the possession check due to the Prove key. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Penny Jowers on mobile with customer-supplied possession fallback. This user fails Mobile Auth but passes after a successful customer OTP and returns
success=true in the /unify-bind response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Penny Jowers.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end attempts Mobile Auth, which fails.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_required reminding you to perform your own possession check.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.
Bind Prove Key
The back end calls
POST /v3/unify-bind with the correlation ID.
Expect success=true, proveId, and phoneNumber in Sandbox. See POST /v3/unify-bind for the full response.You have a successful flow and a Prove key tied to this phone number. Sending this user through again bypasses the possession check due to the Prove key. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Penny Jowers on desktop. This user passes the entire Unified Authentication flow using Prove’s possession and return
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Penny Jowers.
Initiate Start Request
Your front end sends the phone number, possession type, and final target URL to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Instant Link handling.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, and phoneNumber in Sandbox (no Prove Key on desktop). See POST /v3/unify-status.The system successfully runs the flow but excludes the Prove key because it only applies to mobile devices. Send the user on through your authenticated flow.- Prove Possession - Mobile
- Customer-Supplied Possession with Force Bind
- Prove Possession - Desktop
Follow these steps to test the Prove Unified Authentication flow with Bertie Fremont on mobile. This user passes Prove’s possession and return
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bertie Fremont.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs OTP handling. Enter 1234 to simulate a successful OTP.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, deviceId, and phoneNumber in Sandbox. See POST /v3/unify-status for the full response.You have a successful flow and a Prove key tied to this phone number. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Bertie Fremont using customer-supplied possession. This user passes the entire Unified Authentication flow using the customer’s possession and return
success=true in the /unify-bind response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bertie Fremont.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.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_required, reminding you to perform your own possession check.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.
Bind Prove Key
The back end calls
POST /v3/unify-bind with the correlation ID and phone number.
Expect success=true, proveId, and phoneNumber in Sandbox. See POST /v3/unify-bind for the full response.You have a successful flow and a Prove key tied to this phone number. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Bertie Fremont on desktop. This user passes the entire Unified Authentication flow using Prove’s possession and returns
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bertie Fremont.
Initiate Start Request
Your front end sends the phone number, possession type, and final target URL to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Instant Link handling.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, and phoneNumber in Sandbox (no Prove Key on desktop). See POST /v3/unify-status.The system successfully runs the flow but excludes the Prove key because it only applies to mobile devices. Send the user on through your authenticated flow.- Prove Possession - Mobile
- Customer-Supplied Possession with Force Bind
- Prove Possession - Desktop
Follow these steps to test the Prove Unified Authentication flow with Bonnie Sidon on mobile. This user fails Prove’s possession and return
success=false in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bonnie Sidon.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs OTP handling. Enter 1111 to simulate an unsuccessful OTP.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=false and phoneNumber. See POST /v3/unify-status.The test user failed. Send the user through your exception process.Follow these steps to test the Prove Unified Authentication flow with Bonnie Sidon using customer-supplied possession. Treat this user as a fail case and assume they fail your possession check. This user receives
success=possession_required on /unify-status. You then proceed to run your possession. Fail the user out of the flow.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bonnie Sidon.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.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_required, reminding you to perform your own possession check.Follow these steps to test the Prove Unified Authentication flow with Bonnie Sidon on desktop. This user fails the Unified Authentication flow using Prove’s possession and return
success=false in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bonnie Sidon.
Initiate Start Request
Your front end sends the phone number, possession type, and final target URL to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Instant Link handling.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=false and phoneNumber. See POST /v3/unify-status.The test user failed. Send the user through your exception process.- Prove Possession - Mobile
- Prove Passive Authentication with Customer-Supplied Possession Fallback
- Prove Possession - Desktop
Follow these steps to test the Prove Unified Authentication flow with Allissa Zoren on mobile. This user passes Mobile Auth and returns
success=true in the /unify-status response.Follow this flow when testing Prove passive authentication with customer-supplied possession fallback.
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Allissa Zoren.
Initiate Start Request
Your front end sends the possession type to the back end. Your back end calls the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Mobile Auth.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, deviceId, and phoneNumber from Mobile Auth in Sandbox. See POST /v3/unify-status for the full response.You have a successful flow and a Prove key tied to this phone number. Sending this user through again bypasses the possession check due to the Prove key. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Allissa Zoren on mobile. This user passes Mobile Auth and returns
success=true in the /unify-status response.Follow this flow when testing Prove passive authentication with customer-supplied possession fallback.
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Allissa Zoren.
Initiate Start Request
Your front end sends the possession type to the back end. Your back end calls the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Mobile Auth.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, deviceId, and phoneNumber from Mobile Auth in Sandbox. See POST /v3/unify-status for the full response.You have a successful flow and a Prove key tied to this phone number. Sending this user through again bypasses the possession check due to the Prove key. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Allissa Zoren on desktop. This user passes the entire Unified Authentication flow using Prove’s possession and return
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Allissa Zoren.
Initiate Start Request
Your front end sends the phone number, possession type, and final target URL to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Instant Link handling.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, and phoneNumber in Sandbox (no Prove Key on desktop). See POST /v3/unify-status.The system successfully runs the flow but excludes the Prove key because it only applies to mobile devices. Send the user on through your authenticated flow.- Prove Possession - Mobile
- Prove Passive Authentication with Customer-Supplied Possession Fallback
Follow these steps to test the Prove Unified Authentication flow with Wendy Strover on mobile. This user fails Mobile Auth and return
success=false in the /unify-status response.Follow this flow when testing Prove passive authentication with customer-supplied possession fallback.
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Wendy Strover.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end fails Mobile Auth.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=false and phoneNumber. See POST /v3/unify-status.Follow these steps to test the Prove Unified Authentication flow with Wendy Strover on mobile. This user fails Mobile Auth and return
success=false in the /unify-status response.Follow this flow when testing Prove passive authentication with customer-supplied possession fallback.
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Wendy Strover.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end fails Mobile Auth.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=false and phoneNumber. See POST /v3/unify-status.If you are testing the reputation check flow by sending
checkReputation=true in the /unify request, Amii fails the reputation check and returns success=false in the final response.- Prove Possession - Mobile
- Prove Passive Authentication with Customer-Supplied Possession Fallback
- Prove Possession - Desktop
Follow these steps to test the Prove Unified Authentication flow with Amii Porritt on mobile. This user fails Mobile Auth but pass OTP and return
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Amii Porritt.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end attempts Mobile Auth, which fails. The SDK falls back to OTP handling. Enter 1234 to simulate a successful OTP.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, deviceId, and phoneNumber in Sandbox. See POST /v3/unify-status for the full response.You have a successful flow and a Prove key tied to this phone number. Sending this user through again bypasses the possession check due to the Prove key. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Amii Porritt on mobile with customer-supplied possession fallback. This user fails Mobile Auth but passes after a successful customer possession check and returns
success=true in the /unify-bind response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Amii Porritt.
Initiate Start Request
Your front end sends the phone number and possession type to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end attempts Mobile Auth, which fails.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_required reminding you to perform your own possession check.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.
Bind Prove Key
The back end calls
POST /v3/unify-bind with the correlation ID.
Expect success=true, proveId, and phoneNumber in Sandbox. See POST /v3/unify-bind for the full response.You have a successful flow and a Prove key tied to this phone number. Sending this user through again bypasses the possession check due to the Prove key. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Amii Porritt on desktop. This user passes the entire Unified Authentication flow using Prove’s possession and return
success=true in the /unify-status response.Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Amii Porritt.
Initiate Start Request
Your front end sends the phone number, possession type, and final target URL to the back end. Your back end sends the phone number to the /unify endpoint. The response provides an auth token, correlation ID, and
success=pending.Send Auth Token to the Front End
Your back end sends the 
authToken to the front end. The front end runs Instant Link handling.Verify Mobile Number
Once the front end finishes the possession check, the back end calls
POST /v3/unify-status with the correlation ID to validate the phone number.
Expect success=true, proveId, and phoneNumber in Sandbox (no Prove Key on desktop). See POST /v3/unify-status.The system successfully runs the flow but excludes the Prove key because it only applies to mobile devices. Send the user on through your authenticated flow.Follow these steps to test the Prove Unified Authentication flow with Lorant, Jesse, Bertie, or Wendy. This introduces failures into the flow and return
success=false at various points.- Fail Validate (Mobile Flow)
Send Auth Token to the Front End
During the mobile flow, use 1111 to simulate a failed OTP.
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 terminates and the front end proceeds to another authentication method.
Response
{
"phoneNumber": "2001004017",
"success": "false"
}