Outils pour utilisateurs

Différences

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

Lien vers cette vue comparative

Les deux révisions précédentesRévision précédente
Prochaine révision		Révision précédente
en:guide_de_lecture_du_dossier_de_preuve [2025/08/06 16:36] – [Data to Collect and Verify] adminen:guide_de_lecture_du_dossier_de_preuve [2025/10/30 14:53] (Version actuelle) – [📤 Extracted_data Object] admin
Ligne 1: Ligne 1:
-~~NOTOC~~ +[[:guide_de_lecture_du_dossier_de_preuve|French]] | [[:en:guide_de_lecture_du_dossier_de_preuve|English]]
-[[:guide_de_lecture_du_dossier_de_preuve|Français]] | [[:en:guide_de_lecture_du_dossier_de_preuve|English]]+
 ---- ----
-====== Proof slip Information ======+====== Proof File Reading Guide ====== 
 +Each use of a process is linked to a user file. You have full access to all ongoing files, regardless of the users’ preferences.
  
-Each use of a process is linked to a proof slip. You have full access to all active files, regardless of user preferences.   +To view a file, click on the link located at the bottom of the page: **"Download the proof file"**.
-For each completed journey, you can consult a detailed set of information, including:+
  
-{{report.png}}+This file constitutes **the technical and regulatory record** of all operations performed during the process and can serve as **evidence in the event of an audit or dispute**.
  
-====== Report Status ======+====== Structure of the proof file (JSON) ====== 
 +Below is a representative example of the proof file downloaded in JSON format. 
 + 
 +{{:json.png? 550 × 705|}}
  
 +======🛡️ Keys: status and reason ======
 ==== Status ==== ==== Status ====
-**A journey can have several statuses:** + 
-  * **Canceled**: The user exceeded the maximum allowed time to complete the journey +**A process can be defined by several statuses:** 
-  * **Failed**: Internal ID360 error +  * ⬜ **Canceled**: The user has exceeded the maximum time allowed to complete their process. 
-  * **KO**: The file is invalid +  * 🟥 **Failed**: Internal error in ID360. 
-  * **OK**: The file is valid +  * 🟧 **KO**: The file is incorrect. 
-  * **Started**: The user has started their enrollment +  * 🟩 **OK**: The file is correct. 
-  * **New**: The user file has just been created+  * 🟪 **Started**: The user has started their enrollment. 
 +  * 🟦 **New**: The user file has just been created. 
 +  * ❎ Discontinued : The enrollment has been interrupted by the API.
  
 ==== Reason ==== ==== Reason ====
-In the case of a KO file, one or more reasons are provided:+For files with **KO** status, one or more reasons are indicated in the **"reason"** field.
  
-{{statusKO.png?400%}}+This information is mainly intended for internal use. To precisely identify the reason(s) for the failure, please refer to the dedicated guide: [[https://wiki.id360docaposte.com/doku.php?id=identifier_les_etapes_en_echec|Identify failed steps]].
  
-This information is mainly intended for internal use.   +For the complete list of error codes and their meanings, click [[https://id360docaposte.com/fr/documentation/status-codes|here]].
-You can access it through an error code available in the proof file.   +
-To consult this file, simply click the link at the bottom of the user file page:+
  
-{{proofslipbutton.png?250%}}+======👤 Identity Object ====== 
 +The **Identity** block provides at-a-glance access to the individual’s identity information. This section contains the personal information of the user collected or entered during the process. It includes:
  
-In the variable `all_status_codes`:+{{:identity.png?300%|}}
  
-<code> +//The address will be retrieved from a proof of address if requested, or from the identity document if the configuration of your process allows it.//
-         "all_status_codes": [ +
- { +
- "status_code": { +
- "code": "VLD_VALIDATION_KO", +
- "message": "1 validations failed: IDENTITY_DOCUMENT.expired. max allowed: 0" +
- }, +
- "where": "ID360" +
- }, +
- { +
- "status_code": { +
- "code": "VLD_ID_INVALID", +
- "message": "the ID document id_document_result of type CIF is expired" +
- }, +
- "where": "validation" +
- } +
-   ] +
-</code>+
  
-In this example, the success threshold defined in the journey was not met and the identity document has expired.   +The identity is populated using documents in the following order of priority: 
-To view the full list of error codes and their meanings, please click [[https://id360docaposte.com/fr/documentation/status-codes|here]].+  - Digital identity → First name, last name, gender, date and place of birth 
 +  - Physical identity → First name, last name, gender, date and place of birth 
 +  - Entered data → First name, last name, gender, date and place of birth 
 +  - Proof of address → Address 
 +  - Entered data → Address, email
  
-====== Identity ======+//**How are first names and last name populated in the Identity block?**//
  
-The **Identity block** gives you at a glance access to the personal identity information retrieved through identification (ID card or via a MIE provider):+First names and last name are extracted from both the MRZ (Machine Readable Zone) and the VIZ (Visual Inspection Zone). \\ 
 +We compare the first 10 letters of the MRZ with the VIZ:   
 +  * If the score is 100%, the VIZ is used;   
 +  * Otherwise, the MRZ data is retained.   
 +This avoids truncated first names.
  
-{{identitybloc.png?500%}}+======📄 Documents Object ======
  
-//The address will be extracted either from a proof of address document if required, or directly from the ID card depending on the journey configuration.//+In the proof file (JSON), each collected document contains a **"url"** field.   
 +This field indicates **the API path** used to access the corresponding file.
  
-====== Items to be collected and controlled ======+This path is found in the following structure: 
 +**documents → [document type] → files → url**
  
-This section allows you to view the extracted data from submitted documents, as well as the checks performed.+{{:documents_json.png?300%|}}
  
-==== Steps ====+Below are some examples of documents:
  
-Steps correspond to the controls applied to documents and the extraction of related data.+**In Identity: Id_document_result**: Extraction of the information present on the identity document.
  
-{{items.png}}+**In Identity: Id_document_image**: Uploaded identity document. This entry appears twice if the identity document contains both a front and a back side.
  
-**Id_document**: The identity document is considered valid (OK). The information was successfully extracted and can be viewed by clicking the eye icon in the "Result" column. +**In Selfie: Selfie_image**: User photo processed by the ID360 system.
- +
-**Face_comparison**: Confirms that the face on the identity document matches the face in the selfie or uploaded photo. +
- +
-**Fake_photo_id**: Detects whether the face comes from a legitimate identity document by applying anti-fraud measures. +
- +
-**Phone_detection**: When this control is validated (OK), it means no presentation attack has been detected (e.g., ID shown via another screen). +
- +
-**Id_photo_checker**: Analyzes an image to check whether it meets the criteria for an identity document (correct face orientation, no major alterations or objects), then returns a cropped face image with a uniform background. +
- +
-**Birth_date, first_name, name**: These fields were correctly populated. +
- +
-==== Documents ==== +
- +
-You have access for 2 months to all documents uploaded by the user. You can click on each document individually or click **Download** to retrieve them: +
- +
-{{:documents.png|}} +
- +
-**Id_document_result**: Data extracted from the identity document. +
- +
-**Id_document_image**: The uploaded identity document. This entry appears twice if the document has a front and back side. +
- +
-**Selfie_image**: User photo processed by the ID360 system. +
- +
-**Selfie_uploaded_image**: User-uploaded photo or selfie captured during the identification process. +
- +
-====== Cross-checks and Validations ====== +
- +
-This section includes individual and cross-validation checks. In the example below (simplified version), the dossier is considered valid, hence all `"is_valid"` fields are set to `"true"`. +
- +
-The following checks are performed: +
- +
-  * Validity of the MRZ (Machine Readable Zone) +
-  * The identity document was not issued in the future +
-  * The identity document is not expired +
-  * Comparison of names, first names, and birth dates provided vs. those extracted from the document +
- +
-<code> +
-    "validations": [ +
-    { +
-      "id": "7235127-1831865-3", +
-      "ref": "IDENTITY_DOCUMENT.mrz_valid", +
-      "fields": [ +
-        { +
-          "document_type": "IDENTITY_DOCUMENT", +
-          "name": "MRZLINE1", +
-          "path": "$.result.extraction.MRZ_line1", +
-          "value": "IDFRADUPONT<<<<<<<<<<<<<<<<57B026" +
-        }, +
-        { +
-          "document_type": "IDENTITY_DOCUMENT", +
-          "name": "MRZLINE2", +
-          "path": "$.result.extraction.MRZ_line2", +
-          "value": "070897C000956TEROLIMON<<<<<3812014M4" +
-        } +
-      ], +
-      "is_valid": true +
-    }, +
-    { +
-      "id": "7235127-1831865-4", +
-      "ref": "IDENTITY_DOCUMENT.future", +
-      "fields": [ +
-        { +
-          "document_type": "IDENTITY", +
-          "name": "emission_date", +
-          "path": "emission_date", +
-          "value": "2007-06-01" +
-        } +
-      ], +
-      "is_valid": true +
-    }, +
-    { +
-      "id": "7235127-1831865-5", +
-      "ref": "IDENTITY_DOCUMENT.expired", +
-      "fields": [ +
-        { +
-          "document_type": "IDENTITY", +
-          "name": "expiration_date", +
-          "path": "expiration_date", +
-          "value": "2026-06-30" +
-        } +
-      ], +
-      "is_valid": true +
-    }, +
-    { +
-      "id": "7235113-1831862-1", +
-      "ref": "IDENTITY.BIRTH_DATE.birth_date", +
-      "fields": [ +
-        { +
-          "document_type": "IDENTITY", +
-          "name": "birth_date", +
-          "path": "birth_date", +
-          "value": "2006-01-01" +
-        } +
-      ], +
-      "is_valid": true +
-    }, +
-    { +
-      "id": "7235109-1831862-1", +
-      "ref": "IDENTITY.NAME.name", +
-      "fields": [ +
-        { +
-          "document_type": "IDENTITY", +
-          "name": "name", +
-          "path": "name", +
-          "value": "DUPONT" +
-        } +
-      ], +
-      "is_valid": true +
-    } +
-  ]  +
-</code> +
- +
-====== Information in the Proof File (JSON) ====== +
- +
-Below is a representative example of the proof file downloaded in JSON format.+
  
-{{:json.png?550x705|}}+**In Selfie: Selfie_uploaded_image**: User photo uploaded or captured during the identification process.
  
-===== Identity Block ===== +======📋 Steps Object ====== 
-  : Virtual identity of the user+Steps correspond to the checks carried out on the documents as well as the extraction of information.
  
-A user identity is created from the collected documents, including:+{{:steps.png?300%|}}
  
-  * Type of identity document collected +**Id_document**: The identity document is deemed compliant (OK). Information has been correctly extracted and is accessible by clicking on the eye icon in the “Result” column.
-  * Last name +
-  * Email +
-  * Phone number +
-  * Birth name +
-  * First name(s) +
-  * Address +
-  * Zip code +
-  * City +
-  * Country +
-  * Date of birth +
-  * Gender +
-  * City of birth +
-  * Country of birth+
  
-The identity is filled using documents in the following priority order:+**Face_comparison**: The face on the identity document matches the one in the selfie or uploaded photo.
  
-  - Digital Identity → Last name, first name, gender, date and place of birth   +**Fake_photo_id**: This check detects whether the face comes from an authentic identity document, applying countermeasures against forgery.
-  - Paper ID → Last name, first name, gender, date and place of birth   +
-  - User Input → Last name, first name, gender, date and place of birth   +
-  - Proof of address → Address   +
-  - User Input → Address, email  +
  
-===== Document Block ===== +**Phone_detection**: When this check is validated (OK), no presentation attack attempt has been detected (the ID was not presented via another screen).
-List of documents collected during the process+
  
-===== Steps Block ===== +**Id_photo_checker**: This check analyzes an image to ensure it meets the required criteria for an identity document (correct face orientation, absence of objects or major alterations) and returns a cropped version of the face with a uniform background.
-Document identity control steps+
  
-===== Extracted_data Block ===== +**Birth_date, first_name, name**: These data fields have been correctly populated.
-Data extracted by ID360 from each document required during the process.+
  
-**/!\ In the proof file, you may notice the presence of certain data not listed in the extraction table. This is because ID360 certifies the integrity of the data within the following blocks: Identity (identity), Documents (documents), and Extracted Data (extracted_data).**+====== 📤 Extracted_data Object ======
  
-To identify the type of identity document uploaded, refer to the extracted data structure:+To identify the type of identity document submitted, refer to the structure of the extracted data:
  
 <code> <code>
Ligne 243: Ligne 105:
 </code> </code>
  
-The first two characters of the MRZ line indicate the document type:+The first two characters of the MRZ allow the document type to be determined:
  
-  * D1 = Driver’s license   +  * D1 = Driver’s license 
-  * ID = National ID card   +  * ID = Identity card 
-  * C = Italian national ID card   +  * C = Italian national identity card 
-  * I = Portuguese national ID card   +  * I = Portuguese national identity card 
-  * P, P* = Passport   +  * P, P* = Passport 
-  * IR = Residence permit  +  * IR, TS = Residence permit
  
-===== Finalizer_report Block ===== +====== 🚨 Point of Attention ======
-Control results carried out at the end of the enrollment. It mainly includes the blocks: `validations`, `comparisons`, and `customs`.+
  
 +⚠️ In the proof file, you may notice the presence of certain data not specified in the extraction table. This is because ID360 guarantees the integrity of the data contained in the following blocks:
 +  * **Identity**
 +  * **Documents**
 +  * **Extracted_data**
  

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also, you acknowledge that you have read and understand our Privacy Policy. If you do not agree, please leave the website.

Plus d’informations