Skip to main content
Every transaction has a type. It decides what the user is asked to do, which checks run, and — crucially — what the result actually proves.

Document and biometric

Document capture and a liveness check. Proves the person is real, the document is genuine, and they match.

Document only

Document capture, no selfie. Proves the document is genuine and readable.

Biometric only

Liveness check, no document. Proves a real person is present — and, if enrolled, that it is the same person as before.

​
What runs for each type

1 Only when the customer already has an enrolled face. And which parts of the configuration apply:

​
Which type should I use?

1

Onboarding a new user

Document and biometric. This is the only type that ties a real, present person to a genuine document in one transaction, and it is what enrols the reference face that every later check depends on. Start every customer here.
2

Re-verifying a known user before something sensitive

Biometric only, for a customer who has already completed a document-and-biometric verification. A selfie is a few seconds; the comparison against the enrolled face proves it is the same person who onboarded. Good for high-value transfers, password resets, device changes.
3

Refreshing an expired or expiring document

Document only. The person is already enrolled; you need a new document on file. The document face is still compared against the enrolled face, so it cannot be someone else’s document.

​
When there is no enrolled face

On a customer with no enrolled face, a biometric-only verification proves only that a live human was in front of the camera. It does not prove who. The liveness check runs, the comparison is skipped with an informational finding, and the transaction can come back approved.If your product treats biometric-only as an identity check, make sure the customer has completed a document-and-biometric verification first. Your backend can enforce this by refusing to open a biometric-only transaction for a customer with no approved onboarding on record.

​
Time to complete

Match the time limit to how the flow is delivered. A step-up the user starts immediately from a button needs minutes, not hours; a document refresh you send by email is the case that justifies a long window. The exact setting is in the transaction configuration.

​
What the user experiences

The welcome and result screens can be turned off in the SDK configuration.