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 |
| 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.- 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 - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
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.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 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 because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end sends the 
authToken to the front end. The front end runs 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:
proveIdtied to this user.success=truephoneNumberthat was initially passed.
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.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 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 because possession still needs to be performed.3
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.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.proveIdtied to this user.success=truephoneNumberthat was initially passed.
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. Send the user 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 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.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 isn’t 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 calls the /unify-bind endpoint with the correlation ID.
The response provides:
proveIdtied to this user.success=truephoneNumberthat was initially passed.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
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.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Laney Dyball.
2
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 because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs 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:
success=falsephoneNumberthat was initially passed.
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.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Laney Dyball.
2
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.3
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.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 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=possesion_required on /unify-status. You then proceed to run your possession. They fail out of the flow.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Laney Dyball.
2
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.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 isn’t performing the possession check.
4
Perform Your Own Possession Check
Perform your own possession check outside of Prove’s system, simulating a failure and ending the flow.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
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.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 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 because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs 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:
proveIdtied to this user.success=truephoneNumberthat was initially passed.
Follow the steps in this section to test the Prove Unified Authentication flow with Inge Galier on mobile. This user passes Mobile Auth and returns
success=true in the /unify-status response. You can then send the user 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 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.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs 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 Mobile Auth discovered.success=true
Follow the steps in this section to test the Prove Unified Authentication flow with Inge Galier using customer-supplied possession. This user passes the entire Unified Authentication flow using the customer’s possession and returns
success=true in the /unify-bind response. You can then send the user 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 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.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_required, reminding you to complete a 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 calls the /unify-bind endpoint with the correlation ID and phone number.
The response provides:
proveIdtied to this customer.success=truephoneNumberthat was initially passed.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
Follow these steps to test the Prove Unified Authentication flow with Jesse Mashro on desktop. This user fails 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 Mashro.
2
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 because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs Instant Link handling. This user fails Instant Link.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 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.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 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 because possession still needs to be performed.3
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.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 these steps to test the Prove Unified Authentication flow with Jesse Mashro using customer-supplied possession. Treat this user as a fail case and assume they fail your possession check. This user receives
success=possesion_required on /unify-status. You then proceed to run your possession. Fail the user out of the flow.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 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.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 isn’t performing the possession check.
4
Perform Your Own Possession Check
Perform your own possession check outside of Prove’s system, simulating a failure and ending the flow.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
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.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Penny Jowers.
2
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 because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs 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:
proveIdtied to this user.success=truephoneNumberthat was initially passed.
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.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Penny Jowers.
2
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.3
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.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:
deviceIdtied to the mobile device.proveIdtied to this customer.phoneNumberthat Mobile Auth discovered.success=true
Follow these steps to test the Prove Unified Authentication flow with Bonnie Sidon 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.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bonnie Sidon.
2
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.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_required reminding you to perform your own 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 calls the /unify-bind endpoint with the correlation ID.
The response provides:
proveIdtied to this user.success=truephoneNumberthat was initially passed.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
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.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 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.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs 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:
proveIdtied to this user.success=truephoneNumberthat was initially passed.
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.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 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 because possession still needs to be performed.3
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.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.proveIdtied to this user.success=truephoneNumberthat was initially passed.
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.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 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.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_required, reminding you to perform your own 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 calls the /unify-bind endpoint with the correlation ID and phone number.
The response provides:
proveIdtied to this user.success=truephoneNumberthat was initially passed.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
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.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bonnie Sidon.
2
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 because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs 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:
success=falsephoneNumberthat was initially passed.
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.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bonnie Sidon.
2
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 because possession still needs to be performed.3
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.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 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=possesion_required on /unify-status. You then proceed to run your possession. Fail the user out of the flow.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Bonnie Sidon.
2
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.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_required, reminding you to perform your own possession check.4
Perform Your Own Possession Check
Perform your own possession check outside of Prove’s system, simulating a failure and ending the flow.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
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.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 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 because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs 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’s tied to this customer.success=truephoneNumberthat was initially passed.
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. You can then send the user 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 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.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs 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 Mobile Auth discovered.success=truephoneNumberthat was initially passed.
Follow the steps in this section to test the Prove Unified Authentication flow with Allissa Zoren using customer-supplied possession. This user passes the entire Unified Authentication flow using the customer’s possession and returns
success=true in the /unify-bind response. You can then send the user 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 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.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_required since 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 calls the /unify-bind endpoint with the correlation ID and phone number.
The response provides:
proveIdthat’s tied to this customer.success=truephoneNumberthat was initially passed.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
Follow these steps to test the Prove Unified Authentication flow with Wendy Strover on desktop. This user fails 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 Wendy Strover.
2
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.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end runs 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:
success=falsephoneNumberthat was initially passed.
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.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 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.3
Send Auth Token to the Front End
Your back end sends the
authToken to the front end. The front end fails 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:
success=falsephoneNumberthat was initially passed.
Follow these steps to test the Prove Unified Authentication flow with Wendy Strover 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.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 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.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_required, reminding you to perform your own possession check.4
Perform Your Own Possession Check
Perform your own possession check outside of Prove’s system, simulating a failure and ending the flow.
- Prove Possession - Desktop
- Prove Possession - Mobile
- Customer-Supplied Possession
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.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Amii Porritt.
2
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 because possession still needs to be performed.3
Send Auth Token to the Front End
Your back end sends the 
authToken to the front end. The front end runs 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:
proveIdtied to this user.success=truephoneNumberthat was initially passed.
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.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Amii Porritt.
2
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.3
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.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.proveIdtied to this user.success=truephoneNumberthat was initially passed.
Follow these steps to test the Prove Unified Authentication flow with Amii Porritt 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.1
Prompt Customer
Start the onboarding flow on the initial screen and enter the phone number for Amii Porritt.
2
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.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_required pending your 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 calls the /unify-bind endpoint with the correlation ID.
The response provides:
proveIdtied to this user.success=truephoneNumberthat was initially passed.
Follow these steps to test the Prove Unified Authentication flow with Laurent, Jesse, Bertie, or Wendy. This introduces 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 terminates and the front end proceeds to another authentication method.
Response
Report incorrect code
Copy
Ask AI
{
"phoneNumber": "2001004017",
"success": "false"
}