The client’s personal data.

Requirements: For API integration object is required.

The client’s address details.

Requirements: For API integration that upload person and emailAndPhone data.

The client’s email address and phone number(s).

Requirements: For API integration object is required.

The client’s tax information.
Required in Italy and Portugal

The client’s profession and employment situation.

Italian-market risk factors.

Metadata from the client’s device.

For subsequent requests with the same verificationId, deviceMetaData is merged field by field:
• A provided value replaces the stored value.
• An omitted field or a field set to null keeps the stored value.
• An empty string ("") is stored when the field accepts that value. A field with a format check rejects "". For example, language must be 2 characters, and region must be 2 or 3 characters.
• If deviceMetaData is omitted, the stored deviceMetaData remains unchanged.

person, address, emailAndPhone, tax, profession, and riskRequirements replace the entire stored object. Include all fields that should remain stored.

Important: To update geolocation after the SDK or App Component has stored model, send only latitude and longitude. If you include model in the request, for example Chrome, it replaces the stored device model. As a result, the Qualified Electronic Signature device-model check returns selfie_required.

Stored after the SDK or App Component upload:

{
  "deviceMetaData": {
    "model": "iPhone15,2",
    "language": "nl",
    "latitude": "51.00",
    "longitude": "4.00"
  }
}

Your request that only updates geolocation:

{
  "deviceMetaData": {
    "latitude": "52.37",
    "longitude": "4.89"
  }
}

Stored after that request:

{
  "deviceMetaData": {
    "model": "iPhone15,2",
    "language": "nl",
    "latitude": "52.37",
    "longitude": "4.89"
  }
}

Coordinates are updated. model and language stay, because they were not in the request.