Similarity
Similarity is an automated check that compares the face from the ID image with the face captured in the selfie. Some workflows may use alternate credential combinations, and each workflow defines the specific data required. The Similarity check is only executed when the necessary face images are available.
Dependency
Dependency includes Usability, but only for cases related to face detectability. The capability will not run only when the face on the ID cannot be detected. Missing mandatory ID fields do not affect Similarity execution.
Supported Credentials
Decision Details Labels
| Decision Type | Label | Description |
|---|---|---|
| NOT_EXECUTED | PRECONDITION_NOT_FULFILLED | Capability could not run because the required face could not be detected on the ID image. |
| NOT_EXECUTED | TECHNICAL_ERROR | An error prevented execution. |
| PASSED | MATCH | The faces in the images being compared belong to the same person. |
| REJECTED | NO_MATCH | The faces in the selfie and ID do not match. |
| WARNING | NOT_POSSIBLE | Similarity cannot be determined. |
For an overview of how Jumio handles PASSED, WARNING, and REJECTED across all capabilities, see How Jumio Handles Results.
Data
| Key | Type | Description |
|---|---|---|
similarity | string | Possible values: MATCH, NO_MATCH, NOT_POSSIBLE |
If an eIDAS digital ID is used instead of a physical ID, the system does not have access to the ID face, meaning Similarity checks cannot be performed. The actual ID image is also not returned, so these checks are not possible. Additionally, the data points returned may differ when using an eIDAS digital ID. For risk scoring, this limitation may need to be addressed in your rules configuration.