Each use of a process is linked to a proof slip. You have full access to all active files, regardless of user preferences. For each completed journey, you can consult a detailed set of information, including:

A journey can have several statuses:

• Canceled: The user exceeded the maximum allowed time to complete the journey
• Failed: Internal ID360 error
• KO: The file is invalid
• OK: The file is valid
• Started: The user has started their enrollment
• New: The user file has just been created

In the case of a KO file, one or more reasons are provided:

This information is mainly intended for internal use. 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:

In the variable `all_status_codes`:

         "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"
		}
	  ]

In this example, the success threshold defined in the journey was not met and the identity document has expired. To view the full list of error codes and their meanings, please click here.

The Identity block gives you at a glance access to the personal identity information retrieved through identification (ID card or via a MIE provider):

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.

This section allows you to view the extracted data from submitted documents, as well as the checks performed.

Steps correspond to the controls applied to documents and the extraction of related data.

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.

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.

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:

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.

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

    "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
    }
  ] 

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

: Virtual identity of the user

A user identity is created from the collected documents, including:

• Type of identity document collected
• 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:

1. Digital Identity → Last name, first name, gender, date and place of birth
2. Paper ID → Last name, first name, gender, date and place of birth
3. User Input → Last name, first name, gender, date and place of birth
4. Proof of address → Address
5. User Input → Address, email

Where to identify the types of identity documents uploaded in the proof file?

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

The type corresponds to the first two characters of the MRZ strip – ICAO 9303 standard:

• D1 = Driving licence
• ID = Identity card
• C = Italian identity card
• I = Portuguese identity card

How is the first name populated in the Identity block?

First names are extracted from both the MRZ strip and the VIZ area.
We compare the first 10 letters from the MRZ with the VIZ:

• if the score is 100%, the VIZ is used;
• otherwise, the MRZ data is kept.

This prevents truncated first names.

List of documents collected during the process

Document identity control steps

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).

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

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

The first two characters of the MRZ line indicate the document type:

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

Control results carried out at the end of the enrollment. It mainly includes the blocks: `validations`, `comparisons`, and `customs`.