Différences

Ci-dessous, les différences entre deux révisions de la page.

--- en:guide_de_parametrage [2025/09/24 11:56] – [Additional Configurations and Available Controls] admin
+++ en:guide_de_parametrage [2026/01/12 16:39] (Version actuelle) – modification externe 127.0.0.1
@@ Ligne 35: / Ligne 35: @@
 \\
-{{:en:generalinformation.png?1000|}}
+{{:en:InformationsGeneralesEN.png}}
 \\
@@ Ligne 64: / Ligne 64: @@
 ⚠️ A cron job runs once a day to switch files to DELETED. This means the status update may happen up to 24 hours after the expiration.
+---
+=== 📱 Device number limit ===
+The maximum number of devices that can be used during the enrollment process can be configured here.
+  * **0** means no device limit is applied.
+  * **1** means the user cannot switch devices during the enrollment journey.
+  * **2** means the user can switch devices during the enrollment journey **one time**.
+If the configured device limit is exceeded, the user is **not blocked** and **no alert is displayed**.
+However, the **enrollment result will be set to KO**.
 ---
@@ Ligne 181: / Ligne 194: @@
 ===== Focus on the customizable online journey =====
-{{parcourspersonnalisable2.png}}
+{{customizable_process.png}}
-**Font verification**: A font check of the MRZ band is available. However, this control does not systematically guarantee a conclusive result and may slightly increase processing times.
+**Check font type**: A font check of the MRZ band is available. However, if the photo of the identity document provided by the user is of insufficient quality, this check may result in a higher number of failures (KO) and cause a slight increase in processing time.
 ---
-**Monochrome detection**: If the uploaded identity document is monochrome, it will be rejected.
+**Detection of monochrome**: If the uploaded identity document is monochrome, it will be rejected.
 ---
-**Detection of alterations and modifications to the ID photo**: This check detects anomalies (wave patterns, RF, pasted photos).
+**Detection of alteration and modification of the photo of the title**: This check detects anomalies (wave patterns, RF, pasted photos).
 ---
-**Extraction and verification of information**: The MRZ is automatically corrected, and the checksum verification is performed.
+**Extraction and control of information**: The MRZ is automatically corrected, and the checksum verification is performed.
 ---
-**Presentation attack detection**: If the uploaded or captured photo comes from a screen, it will be rejected.
+**Detection of attack by presentation**: If the uploaded or captured photo comes from a screen, it will be rejected.
 ---
@@ Ligne 212: / Ligne 225: @@
 ---
-**Check for the existence of both sides of the document**: If two sides are required and only one is provided, the file will be marked as KO.
+**Verify the existence of both sides of the document**: If two sides are required and only one is provided, the file will be marked as KO.
 ===== Additional Configurations and Available Controls =====
@@ Ligne 286: / Ligne 299: @@
 The entered last name is compared with both the birth name and the usual name.
-🔧 If you still want to perform such checks while redirecting the user to the ID360 identification URL—without letting them modify the expected data—an API method is available to push this data into the system (see: Developer Guide).
+🔧 If you still want to perform such checks while redirecting the user to the ID360 identification URL—without letting them modify the expected data, an API method is available to push this data into the system (see: Developer Guide).
+===== String Comparison in ID360 =====
 🔧 The algorithm used is a fuzzy matching.
+ID360 uses a **three-step approach** to compare strings.
+The goal is to enable reliable comparisons even when strings contain accents, special characters, or linguistic variations.
+==== 1. Unidecode Step ====
+The first step is to **remove accents and diacritical marks** to standardize the comparison.
+This allows words to be compared as if they were written using only standard ASCII characters.
+**Example:**
+  * élodie → elodie
+Thus, *élodie* and *elodie* will be considered **identical** at this stage.
+==== 2. Generic Transliteration Step ====
+Once accents are removed, ID360 applies a **generic transliteration**.
+This process converts non-ASCII characters (such as letters specific to certain languages) into their most common Latin alphabet equivalents.
+The original language of the word is **not** taken into account here — only a standard transliteration is applied.
+**Examples:**
+  * weiß → weiss
+  * düker → duker
+This step makes it possible to harmonize strings originating from different languages without knowing the linguistic context.
+==== 3. Precise Transliteration Step ====
+The final step performs a **contextual transliteration**, taking into account the **original language of the text**.
+For identity documents (passports, national ID cards, etc.), the language used corresponds to the **issuing country of the document**.
+As a result, some letters are transformed differently depending on the language.
+**Examples:**
+  *For Germany (DE)* :
+  * Jörg → Joerg
+  * Düker → Dueker
+  *For France (FR)* :
+  * Jörg → Jorg
+  * Düker → Duker
+This language-aware transliteration provides a **comparison more faithful to the document’s context**.
+==== Notes ====
+  * Specific transliteration rules depend on the **country of origin**.
+  * European countries are generally less affected by these differences, but **Germany** is a notable exception, as its rules are frequently used in official documents.
+  * Other countries may apply their own conventions depending on their civil registry standards or national requirements.
+==== Summary ====
+ID360 compares strings through a progressive process:
+  - **Character normalization** (removal of accents)
+  - **Universal transliteration** (generic conversion of non-ASCII characters)
+  - **Contextual transliteration** (conversion adapted to the document’s language)
+This method ensures a **robust, consistent, and linguistically accurate comparison**.