Each use of a process is linked to a user file. You have full access to all ongoing files, regardless of the users’ preferences.

To view a file, click on the link located at the bottom of the page: “Download the proof file”.

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.

Below is a representative example of the proof file downloaded in JSON format.

A process can be defined by several statuses:

• ⬜ Canceled: The user has exceeded the maximum time allowed to complete their process.
• 🟥 Failed: Internal error in ID360.
• 🟧 KO: The file is incorrect.
• 🟩 OK: The file is correct.
• 🟪 Started: The user has started their enrollment.
• 🟦 New: The user file has just been created.
• ❎ Discontinued : The enrollment has been interrupted by the API.

For files with KO status, one or more reasons are indicated in the “reason” field.

This information is mainly intended for internal use. To precisely identify the reason(s) for the failure, please refer to the dedicated guide: Identify failed steps.

For the complete list of error codes and their meanings, click here.

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:

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.

The identity is populated using documents in the following order of priority:

1. Digital identity → First name, last name, gender, date and place of birth
2. Physical identity → First name, last name, gender, date and place of birth
3. Entered data → First name, last name, gender, date and place of birth
4. Proof of address → Address
5. Entered data → Address, email

How are first names and last name populated in the Identity block?

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.

In the proof file (JSON), each collected document contains a “url” field. This field indicates the API path used to access the corresponding file.

This path is found in the following structure: documents → [document type] → files → url

Below are some examples of documents:

In Identity: Id_document_result: Extraction of the information present on the identity document.

In Identity: Id_document_image: Uploaded identity document. This entry appears twice if the identity document contains both a front and a back side.

In Selfie: Selfie_image: User photo processed by the ID360 system.

In Selfie: Selfie_uploaded_image: User photo uploaded or captured during the identification process.

Steps correspond to the checks carried out on the documents as well as the extraction of information.

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.

Face_comparison: The face on the identity document matches the one in the selfie or uploaded photo.

Fake_photo_id: This check detects whether the face comes from an authentic identity document, applying countermeasures against forgery.

Phone_detection: When this check is validated (OK), no presentation attack attempt has been detected (the ID was not presented via another screen).

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.

Birth_date, first_name, name: These data fields have been correctly populated.

To identify the type of identity document submitted, refer to the structure of the extracted data:

"extracted_data": {
   "identity": [
      {
         "type": "ID"
      }
   ]
}

The first two characters of the MRZ allow the document type to be determined:

• D1 = Driver’s license
• ID = Identity card
• C = Italian national identity card
• I = Portuguese national identity card
• P, P* = Passport
• IR, TS = Residence permit

⚠️ 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