​
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 along with its territories
  • Canada
  • The United Kingdom
  • Germany
  • France
  • Italy
  • Spain
  • Brazil
  • Australia
  • Indonesia
  • Singapore
  • Thailand
  • Malaysia
Prove continues to expand its global reach. Check back for updates on country availability.

​
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, you’ll need the following components:
  • Prove Platform server-side SDK: You can use one of Prove’s server-side SDKs on the back end of your web application. These are available in Go, Java, TypeScript, and JavaScript. The SDK handles OAuth 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 application. The client-side SDK handles all server calls for one-time password (OTP) and Instant Link possession checks and handles fallback functionality.
  • Web or Native Application: Your application Prove integrates into.

​
Unify Using Prove’s Possession Flow

Prove Unify authentication flow diagram
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.