Solution

Prove Auth®

Businesses are looking to improve their onboarding experiences, reduce costs and improve outcomes for their customers. Prove Auth® delivers modern techniques that increase security and reduce friction, delivering a unified solution for omnichannel auth, passwordless login, and/or a seamless second factor.

Prove uses strong binding methods to initially register a Prove Key on the mobile device, after which that key can be used either in-app or from other channels (ie. Desktop, Call Center, or Retail). Prove Auth® includes the use of the Prove Key whether on the mobile device or through a push notification to the device from another channel.

Coverage:

Bill Fish

Slack : bill.fish

Key Benefits / Outcomes:

  • No OTPs to steal since there’s only a link that’s deterministic to the phone
  • Replaces OTPs with new methods that reduce reliance on Mobile Network Operators
  • Authentication can be initiated in any channel with combination of capabilities
  • Unlimited-use pricing creates cost savings with every user authentication over OTP

A1 - Passwordless w/ SDK Use Case

Prove Auth® A1 creates a seamless authentication experience within a mobile app using the Prove Auth® SDK. It handles the initial possession check for the "bind", registers the Prove key, which can then be used for subsequent authentication. A1 will also cover the ability to send push notifications to the mobile app which can then reference the Prove key for authentication.

Mobile App

1

As the user logs in, Prove authenticates the device is the same as was registered at first app login.

2

The user can be logged in with minimal friction.

Download The Full CX Flow

Prev
Next

Desktop

1

User is logging in to their account on a secondary device (eg. desktop, tablet, etc.) with a username only.

2

If enabled, offer a Push Auth® option to the user.

3

The customer approves the login attempt and accepts the push notification and Prove authenticates the device was previously registered.

4

The user is logged in to the website

Download The Full CX Flow

Prev
Next

Mobile App Step-up - Passive

Status: Beta
Push Auth Fact SheetSolution & Use Case FAQ
1

As the customer attempts to login, Prove verifies possession of the device.

2

Use the on-device biometric to add a second factor of authentication.

3

Use the on-device biometric to add a second factor of authentication.

4

The user has been authenticated with two factors.

Download The Full CX Flow

Prev
Next

Desktop Step-up - Passive

Status: Beta
Push Auth Fact SheetSolution & Use Case FAQ
1

User is logging in to their account on a desktop or other secondary device with existing credentials.

2

If enabled, offer a Push Auth option to the user.

3

The customer approves the login through the push notification, while Prove verifies possession of the registered device

4

Use the on-device biometric to authenticate with a second factor.

5

Use the on-device biometric to authenticate with a second factor.

6

The transaction is allowed to proceed
if the proper person is authenticated

Download The Full CX Flow

Prev
Next

A2 - Passwordless for Web Use Case

Prove Auth® A2 enables Prove keys to be created and leveraged in mobile web scenarios. This will include step-up with on-device biometrics as well.

Mobile Web Step-up

Status: Early Adopter
Solution FAQStandard ConfigurationVideo Explainer
1

As the customer attempts to login, Prove authenticates possession of the device.

2

Use the on-device biometric to add a second factor of authentication.

3

The user has been authenticated with two factors.

Download The Full CX Flow

Prev
Next

Desktop Step-up

1

User is logging in to their account on a desktop or other secondary device with existing credentials.

2

If enabled, offer a Push Auth option to the user.

3

The customer approves the login through the push notification, while Prove authenticates possession of the registered device

4

Use the on-device biometric to authenticate with a second factor.

5

Use the on-device biometric to authenticate with a second factor.

7

The user is logged in to the website

Download The Full CX Flow

Prev
Next

Secondary Device

1

User is logging in to their account on a secondary device (eg. desktop, tablet, etc.) with a username only.

2

Present a QR code among the options that a user could scan, which would kick off the on-device login flow

3

The customer approves the login attempt on the landing page while Prove authenticates the device was previously registered.

4

Use the on-device biometric to authenticate with a second factor.

5

The user is logged in to the website

Download The Full CX Flow

Prev
Next

Mobile Auth

Status: Release
Solution & Use Case FAQ
1

As the customer attempts to login, Prove discovers the phone number from the Mobile Network Operator, to be used to authenticate the correct user.

2

The user has been authenticated

Download The Full CX Flow

Prev
Next

Instant Link - Desktop

Status: Release
Solution & Use Case FAQ
1

User is logging in to their account on a desktop or other secondary device.

2

If enabled, offer a Push Auth option to the user. If Push Auth is unavailable, fallback to Instant Link.

3

User clicks the URL in the text message, and Prove authenticates possession in the background.

4

The transaction is allowed to proceed if the proper person is authenticated

Download The Full CX Flow

Prev
Next

A3 - AirKey Auth

Prove Auth® A3: Use your credit card to authenticate for card activation, step-up, or payment authorization.

Mobile App / Browser

Status: Early Adopter
Solution FAQStandard ConfigurationSolution Overview
1

User is attempting to login

2

User is asked to step-up with a second factor

3

Instructions provided on how to use AirKey

4

User taps their card to the phone

5

Successful tap authenticates the user

Download The Full CX Flow

Prev
Next

Desktop Step-up

1

User is logging in to their account on a desktop or other secondary device with existing credentials.

2

If enabled, offer a Push Auth option to the user.

3

The customer approves the login through the push notification, while Prove authenticates possession of the registered device

4

Use the on-device biometric to authenticate with a second factor.

5

Use the on-device biometric to authenticate with a second factor.

7

The user is logged in to the website

Download The Full CX Flow

Prev
Next

Instant Link - Desktop

Status: Release
Solution & Use Case FAQ
1

User is logging in to their account on a desktop or other secondary device.

2

If enabled, offer a Push Auth option to the user. If Push Auth is unavailable, fallback to Instant Link.

3

User clicks the URL in the text message, and Prove authenticates possession in the background.

4

The transaction is allowed to proceed if the proper person is authenticated

Download The Full CX Flow

Prev
Next

A5 - Portable Identity and Web Wallet

Prove Auth® A5 allows for the creation, reutilization and management of a ProveID, which is issued through using Prove Pre-Fill® when signing up for an account with an issuing entity. That ProveID can be re-used when accessing a relying party, hence making it "Portable". The identity and which entities have access to which customer information can be actively managed by the end user.

Create Prove ID

1

User is attempting to open an account.

2

User is asked to enter date of birth.

(scroll down the screen)
3

User is displayed with prefilled information.

4

Use the on-device biometric for Prove ID.

5

User has successfully created an account and their Prove ID.

Download The Full CX Flow

Prev
Next

Reuse Prove ID

1

User is attempting to sign up to a new account using their Prove ID.

2

Use the on-device biometric for verification.

3

User is displayed with a prefilled information.

4

Account is successfully set up using Prove ID.

Download The Full CX Flow

Prev
Next

Manage Prove ID

1

User logs in to their Prove ID account.

2

Use the on-device biometric for verification.

3

User can view and manage information shared.

4

User can manage different features of their Prove ID.

5

User can review their personal information.

6

User can review their documents uploaded as proofs or claims.

7

User can review or edit their ID relationships.

8

User can review or edit their payment options.

9

User can review or edit identities linked with their Prove ID.

Download The Full CX Flow

Prev
Next

MotionAuth - Mobile

Status: Beta
Gait Auth Fact SheetSolution & Use Case FAQ
1

As the user approaches the door, a sensor detects the presence of the mobile device (via bluetooth or NFC). The motion data of the user is then evaluated against the model.

2

If the user’s motion matches the model then access is granted.

Download The Full CX Flow

Prev
Next

ROI Models

Prove Auth® A1 ROI Model

Download ROI Model

Prove Auth® A2 ROI Model

Download ROI Model

Prove Auth® TCO ROI Model

Download ROI Model

A1 ROI Model

Prove Auth® Rate Card

Prove Auth® Case Studies

Stay tuned! Case studies coming soon!