Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
| en:guide_de_parametrage [2026/01/07 10:27] – [General Information] admin | en:guide_de_parametrage [2026/04/10 15:44] (Version actuelle) – jsellame | ||
|---|---|---|---|
| Ligne 59: | Ligne 59: | ||
| === 🗄️ Active database retention duration in ID360 for enrollments (in minutes) === | === 🗄️ Active database retention duration in ID360 for enrollments (in minutes) === | ||
| - | Not editable | + | By default |
| Duration before the file is archived. This also defines how long you can access uploaded identity documents, selfies, and supporting documents from the admin platform. | Duration before the file is archived. This also defines how long you can access uploaded identity documents, selfies, and supporting documents from the admin platform. | ||
| Ligne 229: | Ligne 229: | ||
| ===== Additional Configurations and Available Controls ===== | ===== Additional Configurations and Available Controls ===== | ||
| - | **This person must act on behalf of a legal entity** | + | **This person must be acting |
| • If the identity is listed in the KBIS: | • If the identity is listed in the KBIS: | ||
| Ligne 245: | Ligne 245: | ||
| --- | --- | ||
| - | **Capture the identity document if a MIE is selected** | + | **Capture the identity document if the user chooses an EIM** |
| * Step 1: Identification via FranceConnect(+) or La Poste Digital Identity | * Step 1: Identification via FranceConnect(+) or La Poste Digital Identity | ||
| Ligne 256: | Ligne 256: | ||
| --- | --- | ||
| - | **Enable rear camera | + | **Enable |
| Allows a helper to assist the user during selfie capture by activating the rear camera. | Allows a helper to assist the user during selfie capture by activating the rear camera. | ||
| Ligne 262: | Ligne 262: | ||
| --- | --- | ||
| - | **Visual control of documents** | + | **Visual control of the document type** |
| Allows visual verification to check if the document matches a known template. | Allows visual verification to check if the document matches a known template. | ||
| - | 🔧 Currently being improved; it is not recommended to check this option. | + | 🔧 Bêta fonctionnality 🔧 |
| --- | --- | ||
| - | **Split | + | **Split address on identity documents** |
| The address will be split into street number, street name, postal code, and city. | The address will be split into street number, street name, postal code, and city. | ||
| Ligne 383: | Ligne 383: | ||
| --- | --- | ||
| - | If you would like more details on data extraction and both unitary and cross-check verifications, | + | If you would like more details on data extraction and both unitary and cross-check verifications, |
| - | **“ID360-Inf-Documentation on Extractions | + | |
| --- | --- | ||
| Ligne 427: | Ligne 426: | ||
| --- | --- | ||
| - | **Verify issuance | + | **Check birth date against |
| - | Compares the issuance | + | Compares the birth date shown on the document (VIZ) with the one read from the MRZ. |
| --- | --- | ||
| - | **Verify issuance | + | **Check emission |
| - | Compares the visually | + | Compares the emission date as it appears |
| --- | --- | ||
| - | **Verify birth date against MRZ**: | + | **Check first names against |
| - | Compares the birth date shown on the document (VIZ) with the one read from the MRZ. | + | Compares the first names as seen on the document |
| --- | --- | ||
| - | **Verify | + | **Check surname against the MRZ**: |
| - | Ensures that the checksums in the Machine Readable Zone are valid and that the MRZ follows international standards. | + | Compares |
| --- | --- | ||
| - | **Verify last name against | + | **Check that the document numbers in the VIZ and the MRZ are the same**: |
| - | Compares the last name as it appears on the identity | + | Compares the document |
| --- | --- | ||
| - | **Verify last name against 2D-DOC**: | + | **Checks document type against 2D-DOC |
| - | Compares the last name from the 2D-DOC | + | Compares the document type (passport, ID card, residence permit, driver’s license) |
| --- | --- | ||
| - | **Verify document number | + | **Checks emission date against |
| - | Compares the document number | + | Compares the visually read issuance date (from the VIZ) with the one inferred |
| - | + | ||
| - | --- | + | |
| - | + | ||
| - | **Verify document number against 2D-DOC**: | + | |
| - | Compares the document number from the 2D-DOC (if available) with the one extracted from the MRZ. | + | |
| --- | --- | ||
| - | **Verify | + | **Checks |
| Compares the first name from the 2D-DOC (if available) with the one extracted from the MRZ. | Compares the first name from the 2D-DOC (if available) with the one extracted from the MRZ. | ||
| --- | --- | ||
| - | **Verify | + | **Checks |
| Compares the gender from the 2D-DOC (if available) with the one extracted from the MRZ. | Compares the gender from the 2D-DOC (if available) with the one extracted from the MRZ. | ||
| --- | --- | ||
| - | **Verify document type against 2D-DOC**: | + | **Checks id number |
| - | Compares the document | + | Compares the document |
| --- | --- | ||
| - | **Verify first names against MRZ**: | + | **Checks if the Id document was not issued on Sunday**: |
| - | Compares the first names as seen on the document | + | Checks that the document |
| --- | --- | ||
| - | **Verify document number presence in both VIZ and MRZ**: | + | **Checks |
| - | Checks | + | Ensures |
| --- | --- | ||
| - | **Verify document was not issued in the future**: | + | **Checks name against 2D-DOC data**: |
| - | Checks that the issuance date is prior to today’s date. | + | Compares the last name from the 2D-DOC (if available) with the one extracted from the id card. |
| --- | --- | ||
| - | **Verify | + | **Checks that the document |
| - | Checks that the document was not issued on a Sunday. | + | Checks that the issuance date is prior to today’s date. |
| --- | --- | ||
| - | **Verify | + | **Checks that the document has not expired |
| - | Verifies that the document is still valid, considering a 15-year validity for adults | + | Verifies that the document is still valid, considering a 15-year validity for majors |
| The validity period is 15 years for national identity cards issued since 2004.Example: | The validity period is 15 years for national identity cards issued since 2004.Example: | ||
| For cards issued before 2004, ID360 also applies a 15-year validity period. | For cards issued before 2004, ID360 also applies a 15-year validity period. | ||
| Ligne 509: | Ligne 503: | ||
| --- | --- | ||
| - | **Verify | + | **Checks that the document number is not include in the blacklist**: |
| Checks whether the document number is listed in a configurable blacklist (to reject known fraudulent documents). | Checks whether the document number is listed in a configurable blacklist (to reject known fraudulent documents). | ||
| + | |||
| + | --- | ||
| + | |||
| + | **Checks that the document was recognized**: | ||
| + | Checks that the document is an identity document | ||
| ===== Digital Identity ===== | ===== Digital Identity ===== | ||
| Ligne 535: | Ligne 534: | ||
| **Passive liveness check**: | **Passive liveness check**: | ||
| - | The user must take a photo of their face. | + | The user will be required to take a photo of their face. The system will verify that the end user is live (liveness detection), that they are not wearing a mask or using filters, that the face does not come from a photo, and that no spoofed video stream (e.g. webcam injection) is being used. |
| **Biometric facial comparison with the ID document**: | **Biometric facial comparison with the ID document**: | ||
| Ligne 566: | Ligne 565: | ||
| If the sender’s name should differ from the company name in ID360 when sending an OTP by SMS, or when switching from a landline or tablet to a mobile phone, it should be entered here. | If the sender’s name should differ from the company name in ID360 when sending an OTP by SMS, or when switching from a landline or tablet to a mobile phone, it should be entered here. | ||
| - | ===== Interface Customization ===== | + | ====== Interface Customization ====== |
| + | |||
| + | You can customize the visual rendering of the journey at two levels: the process or the end user. | ||
| + | |||
| + | **At process level**, the customization applies to all cases, meaning every end user will be impacted. | ||
| + | |||
| + | **Or at case level** (only when using API integration), | ||
| + | ==== 🎯 Process level customization (global configuration) ==== | ||
| + | |||
| + | You can define a customization directly at the process level. | ||
| + | In this case, the configuration is **generic** and automatically applies to all cases initiated from this process. | ||
| + | |||
| + | This allows you to ensure visual consistency without having to configure each case individually. | ||
| + | |||
| + | {{personnalisation1_en.png}} | ||
| + | |||
| + | ==== 🎯 User enrollment level customization (specific configuration) ==== | ||
| + | |||
| + | In addition, you can define a specific customization at the final user level. | ||
| + | |||
| + | This configuration allows you to adapt the visual rendering of the journey for a specific case, depending on your client or your usage context. | ||
| + | |||
| + | To create themes, click on the burger menu at the top right and select **Themes**. | ||
| + | Click on **"Add Theme +"** and configure your theme. | ||
| + | You can create as many themes as needed depending on your interface customization requirements. | ||
| + | |||
| + | {{: | ||
| - | ID360 allows interface customization: | + | Once the themes are configured, the theme IDs are visible in the **" |
| + | In the example above, the IDs are **2** and **3**. | ||
| + | You now simply need to provide this theme ID when creating the user folder (see **Note** in section **" | ||
| ===== Applications Allowed to Use the process ===== | ===== Applications Allowed to Use the process ===== | ||