Identity Document Check

General behaviour

Note: The ability to retry upon failure depends on the node configuration in the journey (maximum number of attempts allowed).

---

Success cases

These codes do not interrupt the journey. The user sees a validation screen and continues.

Message displayed to the user (all success cases):

• Title: Verification successful!
• Subtitle: Your document has been successfully validated. You may now continue the verification process.

---

✅ Code 1.0 — Full success

Back-office message (analyst):

The document has been fully verified by the AI — valid and compliant.

Validation points displayed to the user:

• Image quality: ✅ Validated
• Information readability: ✅ Confirmed
• Document: ✅ Verified

---

✅ Code 4.0 — Partial success

Back-office message (analyst):

The document was processed, but some checks could not be completed — please verify its authenticity manually.

Validation points displayed to the user:

• Image quality: ✅ Validated
• Information readability: ✅ Confirmed

The journey is not blocked because incomplete checks may result from a technical limitation rather than an actual issue with the document. The analyst must complete the verification manually in the back-office.

---

⚠️ Code 5.0 — Success with fraud alert

Back-office message (analyst):

⚠️

At least one element of the document is suspected to be fraudulent.

Validation points displayed to the user:

• Image quality: ✅ Validated
• Information readability: ✅ Confirmed

The fraud alert is intentionally not communicated to the user in order not to disclose the fraud detection methods. Furthermore, the journey is not blocked as this may be a false positive — the analyst must make the final decision in the back-office.

---

⚠️ Code 6.0 — Success with registry alert

Back-office message (analyst):

⚠️

The person appears on a public registry: criminal / sanctioned / politically exposed person (PEP).

Validation points displayed to the user:

• Image quality: ✅ Validated
• Information readability: ✅ Confirmed

The PEP or sanctioned status is intentionally not communicated to the user to avoid revealing that the person has been identified as such. Likewise, the journey is not blocked as this may be a false positive (name match, outdated data) — the final decision belongs to the analyst.

---

Failure cases — retry available

These codes temporarily block the journey. The user is invited to correct and resubmit their document, within the retry limit configured on the node.

Message displayed to the user (all failure cases):

• Title: Verification failed
• Subtitle: We were unable to validate your document. Please check the points below and try again.

---

🔁 Code 2.0 — Generic processing failure

Back-office message (analyst):

The document could not be processed.

Validation points displayed to the user:

• Image quality: ⚠️ Average
• Information readability: ❌ Insufficient
• Document: ❌ Could not be verified

---

🔁 Code 2.1 — Blurry image

Back-office message (analyst):

The document could not be processed: blurry image.

Validation points displayed to the user:

• Image quality: ❌ Blurry
• Information readability: ❌ Insufficient
• Document: ❌ Could not be verified

Guidance displayed to the user:

The photo is not sharp. Avoid any blur or glare.

---

🔁 Code 2.2 — Unreadable text

Back-office message (analyst):

The document could not be processed: unable to read the text information.

Validation points displayed to the user:

• Image quality: ⚠️ Average
• Information readability: ❌ Unreadable
• Document: ❌ Could not be verified

Guidance displayed to the user:

The photo is not sharp. Avoid any blur or glare.

---

🔁 Code 2.4 — MRZ not found

Back-office message (analyst):

The document could not be processed: the MRZ was not found.

Validation points displayed to the user:

• Image quality: ⚠️ Average
• Information readability: ❌ The MRZ strip (<<<) is truncated
• Document: ❌ Could not be verified

Guidance displayed to the user:

The photo is not sharp. Avoid any blur or glare.

---

🔁 Code 2.5 — Missing document side

Back-office message (analyst):

The document could not be processed: one side of the document is missing.

Validation points displayed to the user:

• Image quality: ✅ Validated
• Information readability: ✅ Confirmed
• Document: ❌ One side of the document is missing

---

🔁 Code 2.6 — Identity document not identified

Back-office message (analyst):

The document could not be processed: no identity document was identified.

Validation points displayed to the user:

• Image quality: ✅ Validated
• Information readability: ✅ Confirmed
• Document: ❌ The submitted document is not the expected one

Guidance displayed to the user:

We were unable to identify your identity document.

---

🔁 Code 3.0 — Expired document

Back-office message (analyst):

The document is expired.

Validation points displayed to the user:

• Image quality: ✅ Validated
• Information readability: ✅ Confirmed
• Document: ❌ The document is expired

---

🔁 Code 7.0 — Identity mismatch with user input

Back-office message (analyst):

The document holder does not match the user's input.

Validation points displayed to the user:

• Image quality: ✅ Validated
• Information readability: ✅ Confirmed
• Document: ❌ The information on the document does not match the information entered

---

🔁 Code 7.1 — Document photo ≠ selfie

Back-office message (analyst):

The photo on the document does not match the submitted selfie.

Validation points displayed to the user:

• Image quality: ✅ Validated
• Information readability: ✅ Confirmed
• Document: ❌ The photo on the document does not match the photo taken

🔁 Code 8.0 — Specimen detected

Back-office message (analyst):

⚠️

The document was found in the specimen database.

Message displayed to the user:

• Title: Verification failed
• Orange banner: The submitted document is a specimen
• Image quality: ✅ Validated
• Information readability: ✅ Confirmed

Specimen detection is a definitive case: no retry is offered and the journey is stopped. The analyst must handle this case manually in the back-office.

---

Summary