Skip to main content

​
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 NumberFirst NameLast Name
2001004018BarbaraanneCanet
After initial short-term testing, implement the client-side SDK and use the remaining test users to test your implementation.

​
Unified Auth test users

Follow the Testing Steps for expected behavior per step.
  • North America
  • International
Phone NumberFirst NameLast Name
2001004014LorantNerger

​
Mobile Auth test users

Follow the Testing Steps for expected behavior per step.
  • North America
  • International
Phone NumberFirst NameLast Name
2001004016IngeGalier
2001004017JesseMashro

​
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.
Example of the Instant Link screen in the Prove Unified Authentication sandbox testing flow
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:
  • proveId that is tied to this user.
  • success=true
  • phoneNumber that was initially passed.
You have a successful flow but no Prove Key is placed as it only applies to mobile devices. Send the user on through your authenticated flow.