Prove Unify Overview
Learn about the components that make up the Prove Unify solution
Prove Unify solution
Prove Unify simplifies and strengthens your authentication security by automatically choosing the right authenticator based on trusted device recognition and authenticator availability—reducing friction while protecting against fraud.Global availability
Prove Unify is available in the following regions:- The United States with its territories
- Canada
- The United Kingdom
- Germany
- France
- Italy
- Spain
- Brazil
- Australia
- Indonesia
- Singapore
- Thailand
- Malaysia
Prove Unify terminology
- Prove Key: Non extractable cryptographic key used for verification by Prove.
- Bind: Establishes possession of the phone number to register the Prove Key.
- Customer-Initiated Bind: Registry of a Prove Key based on customer-supplied possession of the phone number.
Integration components
To implement, gather the following components:- Prove Platform server-side SDK: You can use one of the server-side SDKs on the back end of your web app. These are available in Go, Java, TypeScript, and JavaScript. The SDK handles OAuth 2.0 token management and simplifies the request and response handling. Using a different back end language? You can integrate using the API endpoints.
- Prove Platform client-side SDK: You must use the web, iOS, or Android client-side SDK on the front end of your web app. The client-side SDK handles all server calls for one-time password (OTP) and Instant Link possession checks and handles fallback features.
- Web or Native Application: Your app Prove integrates into.
Unify Using Prove’s Possession Flow
1
Unify Call
The Unify call generates the OAuth token, initiates the session, and accepts the phone number input.
2
Client-Side SDK
The client-side SDK initiates the authentication.
- Mobile Channels: Checks for a bound Prove Key first. If one isn’t present, it falls back to SMS OTP and places the Prove Key.
- Desktop Channels: Uses Instant Link for the possession check.
3
Unify Status Call
The Unify Status call results indicate whether authentication passed or failed.
success=true indicates either the customer passed the possession check and completed the bind or authenticated using the Prove Key.4
Subsequent Authentication
If authentication passed, this customer can authenticate using the Prove Key on future authentications while the system maintains the Prove Key binding.
Unify Using Customer-Supplied Possession
Unify Using Customer-Supplied Possession
Only mobile channels are currently supported for customer-supplied possession.
1
Unify Call
The Unify call with
possessionType=none initiates the session and accepts the phone number input.2
Client-Side SDK
The client-side SDK initiates the authentication. It checks for a bound Prove Key first, then places the Prove Key if not already present.
3
Unify Status Call (First)
The Unify Status call either indicates the customer authenticated using the Prove Key or that you must perform possession verification.
4
Customer Possession Check
If you need to perform possession verification, your application needs to perform a customer-supplied possession check such as SMS OTP. If possession passes, proceed to the Unify bind step.
5
Unify Bind Call
The Unify Bind call completes the customer-initiated bind registering the Prove Key.
6
Subsequent Authentication
This consumer can use the Prove Key for future authentications while the system maintains the Prove Key binding.