Duplicate account detection

The job

One person, several accounts: for promotions, for limits, for evading a ban. A name or an email address is easy to change. The face is harder to change, so the face is what this flow checks.

The flow

1. The selfie. The new user takes a selfie in the widget, and liveness confirms that a live person is present.
2. The search. The face is searched among earlier verified faces. See face search.
3. The outcome. If a returning face is found, the session carries that signal next to the other results.
4. The decision. Your rules decide: link the new account to the old one, hold it for review, or allow it. A reviewer can make a manual decision in the dashboard.

The flow needs the selfie and the search. A document can be added with document verification when your service asks for it.

Scenario setup

Repeat-user search is a scenario option. Switch it on in the scenario editor for the flow where duplicates matter, such as sign-up.

What your system receives

The session status and the results of the steps, including the outcome of the search. See session statuses.

How it differs from a blocklist

Duplicate detection looks for people who were verified before. A blocklist looks for people you chose to list. The two can run together.

Next

Read about face search, or write to us about your sign-up flow.