Skip to main content

# Applicant

Applicant represents an individual’s account used for biometric verification.

All biometric checks conducted under any applicant are stored in attempts.

There are two main states of an applicant:

- Registered.
- Not registered.

A registered applicant assigns biometric data of a particular person. Once a person's biometric data has been assigned to a particular applicant, it cannot be re-registered under a different applicant.

## Applicant operations​

This section lists the operations that can be performed on an applicant.

### Registration​

Applicant registration is the process of linking a user's biometric data to an account based on successfully performed biometric checks. This operation is irreversible: once the biometric data are linked, they cannot be unlinked from the account. It is only possible to replace existing biometric data with new ones.

note

In this step, the biometric template from the submitted biometrics is checked against a database of registered applicants for a match.

danger

The addition of biometrics to the database is not instantaneous. The maximum time period for adding depends on the OMNI Platform index_update_period module setting. Until the photo is added, it is possible to register duplicates.

Authorization is available immediately after registration because this process compares the biometrics from the authorization attempt with the registration biometrics, not with the biometrics from the system database.

### Authorization​

Applicant authorization is the process of verifying the user's identity by comparing the provided biometric data with the data previously linked to the applicant.

During authorization the system analyzes and compares the current biometric parameters with the reference ones, which allows to confirm the authenticity of the user's identity. Successful authorization occurs with the data match.

note

In this step the biometric template from the surrendered biometrics is verified to match exclusively with the biometrics linked to the applicant.

### Registration confirmation​

note

This step is only possible after enabling the appropriate setting in the system.

In registration confirmation mode, the system processes biometrics as follows:

- Even if the initial registration attempts are successful, they do not associate the biometrics with the applicant.
- The final registration confirmation is a separate action that directly binds the biometrics to the applicant.

This mode is particularly effective when BAF is integrated into existing biometric validation systems.

danger

Applicants with unconfirmed registration do not have their biometrics stored in the database, which means multiple applicants with the same biometrics could be in an unconfirmed registration state.

The system confirms registration without comparing the biometric template against a central database, so confirming applicants with identical biometrics may result in duplicates.

To avoid potential issues, we recommend completing both the registration confirmation and registration in a single external session.

### Blocking​

If you block a non-registered applicant, no further authorization attempts can be made.

If you block a registered applicant, not only will further authorization attempts be blocked, but any attempt to register a new applicant will fail as the biometrics are already associated with the blocked individual.

### Unblocking​

Unblocking an applicant allows biometrics submission attempts to resume for that individual.

If you unblock an unregistered applicant, the enrollment attempts counter will be reset for that applicant.

### Reference biometric template updating​

note

This feature is only available via API.

Biometric template update allows you to modify the reference biometrics of an applicant. The updated biometrics will then be used for future authorization attempts.

danger

The update is not instantaneous. The maximum time for the update depends on the index_update_period setting in the OMNI Platform module. Until the photo is updated, authorization will continue to use the old biometrics.

### Deleting an applicant​

Deleting an applicant involves permanently removing their biometric and other data from the system. Once the process is complete, the biometric data can be re-enrolled if needed.

## Applicant statuses​

The applicant status indicates the current state of the applicant and determines the operations that can be performed for that applicant.

### Applicant status display locations​

In API responses, the applicant status is stored in two fields: statusName (text representation) and status (numeric representation).

Here’s an example of an API response containing applicant data:

    {
      "applicantId": "78c57b83-9420-404e-bc7e-9edd1c131e55",
      ...
      "status": 1,
      "statusName": "Success",
    }

In the dashboard, you can view the applicant's status in the table displaying all applicants:

### Description of applicant's statuses​

Below is a table outlining the applicant's statuses. For each status there is a list of actions that can be performed on the applicant in that status.

Status name | Status number | Status description | Possible action on the applicant
Pending | 0 | An applicant has just been created. No registration attempts have been made | Registration Block
Success | 1 | The applicant has been successfully registered. Biometrics saved in the database | Authorization Block Reference biometric template update
Failed | 2 | Applicant is blocked due to excess registration attempts | Unblock
Canceled | 3 | Applicant is closed manually | Unblock
FailedAttempt | 5 | The applicant has tried to register without success. Repeated attempts are possible | Registration Block
Unconfirmed | 6 | BAF has deemed the registration attempt successful, but validation of the external system is required to save the biometrics | Registration confirmation Block

note

Back to the global states of the applicant: registered and not registered.

An applicant is considered registered if it has the status "Success" or "Canceled" (in case of blocking a previously registered applicant). The other statuses correspond to the status not registered.

#### Applicant status transition diagram​