Face search

What it does

Face search answers a question that a single face match cannot: has this person been verified before? It compares a face with the faces of earlier verified users. It also compares a face with the person lists and blocklists that you maintain.

Three uses

Repeat-user search. A new face is looked up among earlier verified users, so a returning person can be recognised.
Person lists. Faces that you add to a list can be checked in the same flow.
Blocklists. Faces that you do not want to admit can be kept on a blocklist and checked for every new session.

How it works in the flow

The user completes the selfie step in the widget.
The face is searched among earlier verified users, and checked against your person lists and blocklists.
The outcome is added to the session, and your system or a reviewer decides what a match means for your service.

What a match means

A match is a signal. Your scenario and your own rules decide what happens next: a manual decision in the dashboard, a block, or no action. The duplicate account detection and blocklist screening use cases show two ways to use it.

Set it up

Repeat-user search and the lists are scenario options in the scenario editor. For standalone use, see the face API.

Read how face verification matches the selfie to the document, or talk to us about your lists.

Questions, answered plainly

What does face search find?

A returning person among earlier verified faces. It can also check a face against the person lists and blocklists that you upload.

Is face search part of every verification?

No. It is a scenario option that you switch on for the flows that need it.

Can I search faces without running a full session?

Yes. The face API offers detect, compare and search on their own. See face API.

Can the setup grow with my user base?

Tell us the volume you expect and we will plan the setup with you.