Documentation Hub
Start Here
Why Keyless?Start HereMobile SDKWeb SDKWorkforceIDV BridgeUser GuideAdmin portalOn-Premise
Start Here
Why Keyless?Start HereMobile SDKWeb SDKWorkforceIDV BridgeUser GuideAdmin portalOn-Premise
  • Keyless: Privacy-Preserving Biometric Authentication
  • Enrollment
  • Authentication
  • Account Recovery
Powered by GitBook
On this page
  • Live Enrollment
  • IDV Bridge

Was this helpful?

Enrollment

This pages explains the two options our customers have to enroll their users on to the Keyless system in order to authenticate their identity on an ongoing basis.

Last updated 25 days ago

Was this helpful?

Live Enrollment

Who's it for?

Businesses that want to use Keyless selfie-capture process either

  1. During the onboarding of new users

  2. As a way to enhance the authentication experience for existing authenicated users (by enhancing security and usability)

What it does

Keyless provides a User Interface (UI) to create a digital identity, which will then be used as a base template when a user attempts to authenticate in the future.

This involves capturing their facial biometrics and device details. Our passive liveness technology will also ensure the user is a real person.

How it works

Mobile SDK

The Keyless mobile SDK allows you to embed the capture of the selfie and enrollment seamlessly into your own Android or iOS app.

This is the recommended and most secure approach, as the selfie is processed exclusively on the customer's device and no biometric data is stored after enrollment, making the process completely privacy-preserving.

Find out more → Mobile SDK

Web SDK

The Keyless Web SDK allows you to integrate the enrollment experience into your own web-based services. The captured image is securely encrypted and sent to the Keyless server where it is transformed into a private key. No biometric data is stored.

Find out more → Web SDK

IDV Bridge

Who it’s for?

Businesses that have already created a biometric template as part of an existing Know Your Customer (KYC) or Identity Verification (IDV) flow.

What it does

The IDV Bridge leverages a user’s existing portrait for future authentication attempts. This removes the need for live enrollment while linking Keyless authentication to an potrait/selfie that was originally captured during an onboarding flow while establishing the true identity of the user.

Typically clients use this solution in one of two ways:

  1. Bulk upload of selfies - having collected a significant number of "selfies" or identity documents, typically during an onboarding or KYC process and clients can then use IDV Bridge to passively enroll these selfies/users into the Keyless system to allow for Authentication and genuine ongoing assurance that they are still dealing with that same identity.

  2. Single selfie upload - clients who already have selfie capture step in their onboarding flow can send this image to IDV Bridge to enroll their users into Keyless without having to add an additional step to the process, yet still allowing them to again authenticate and achieve the same genuine ongoing assurance as above.

Note also that this reduces risk for customers by transforming facial biometric data into a secure cryptographic key, enabling image deletion, and improves the user experience by removing the need for active live enrollment with Keyless.

How it works

Keyless have two deployment options to allow them to upload previously captured face portraits:

  1. IDV Bridge SaaS - A backend-to-backend where businesses pass encrypted images to our authentication service API for enrollment.

  2. IDV Bridge On-Premise - Keyless can support deployment of this service in your infrastructure as per the diagram below.

    Find out more -> IDV Bridge On-Premise (Keyless Agent) *Docs coming soon* (March '25)

Find out more ->

IDV Bridge Saas