For the complete documentation index, see llms.txt. This page is also available as Markdown.

Face Liveness Lite

Face Liveness Lite is a lightweight face liveness verification solution. It confirms that a real, live person is in front of the camera and rejects spoofing attempts such as photos, screens or masks. The mobile SDKs have a minimal footprint, and the final result is retrieved by your backend, never decided on the device.

How it works

1

Your backend requests a session token

Your backend requests a session token and stores the tokenId returned with it. See Backend Setup — step 1.

2

Your app runs the capture

Your app passes the sessionToken to the SDK as mobileToken, together with the personId, and starts the capture.

3

The SDK returns a signedResponse

When the capture ends, on success or on failure, the SDK returns a signedResponse (a signed JWT). Your app forwards it to your backend.

4

Your backend validates it and retrieves the result

Your backend verifies the signedResponse signature, checks that its tokenId matches the stored one, and retrieves the result with the livenessAttemptId. See Backend Setup and Result Reference.

Platforms

Regions

Face Liveness Lite runs in two isolated regions, US and Brazil: see Regions for the hosts and rules. The SDK selects the region from the session token, starting at these versions:

Platform
Minimum version

iOS (CafSDKiOS)

7.8.0

Android

7.27.0

Glossary

Term
Description

sessionToken

Token your backend requests for each attempt. The app passes it to the SDK as mobileToken.

tokenId

Identifier of the session token. Your backend stores it and compares it with the one inside the signedResponse.

personId

Identifier of the user, passed to the SDK.

signedResponse

Signed JWT returned by the SDK at the end of the capture. It carries identifiers only, not the liveness result.

livenessAttemptId

Identifier of the attempt, read from the signedResponse. Used to retrieve the result.

Failure

The capture ran but did not pass. The SDK returns a reason to guide the user, and a signedResponse.

Error

The run could not start or finish. No capture was assessed and no signedResponse is returned.

Last updated