Liveness configuration

How to customize the liveness flow.

The liveness flow starts with the end user taking a selfie or video.

There are three liveness providers available as of currently:

Provider	Description	WEB	SDK	Device
AWS	verifies a still image of the end user that it contains a non obstructed face	✅	❌	❌
Sensetime	verifies a video taken by the end user that they perform a certain action	✅	❌	❌
Facetec	verifies a video taken by the end user that they make a 3d face scan	✅	✅	✅

You can find more information about these providers in the Liveness and Face Recognition providers guide

These are the liveness configuration options:

• livenessCount
  number - default 1
  The amount of times one has to pass liveness to get a verified liveness result. (applies only to SenseTime provider)
• threshold
  number - default 0.8
  Minimum score to pass the verifying process in decimal format. (0.8 = 80% match)
  If there are multiple scores calculated, all scores must be greater than the threshold.

Example

JSON

{
  "livenessConfig": {
    "required": true,
    "attempts": 2,
    "livenessCount": 2,
    "threshHold": 0.8,
    "endFlowOnFailure": false
  }
}

Device Livenesss

After the "Dip Chip Point" flow, it is possible to combine this flow with additional liveness verification. The difference with regular liveness is that device liveness is done on a registered kiosk device and the user has to do an additional OTP authentication through the case's contact number.

The configuration options for device liveness are identical as above, and will always use the Facetec provider.