Ctrlk

Natural Person Update process

Prerequisites

Partners are required to create a Natural Person, upload necessary documents and then initiate the update process.

Required Documents

For specific types of Natural Person data updates, providing an appropriate document confirming the change is required:

  • title - document confirming obtaining the title, document type: KYC

  • lastName - document confirming the name change, document type: KYC

  • nationalities - ID document or passport, document type: KYC

  • mainAddress outside Germany - proof of residence document, document type: PROOF_OF_RESIDENCE

  • deathDay - death certificate, document type: OTHER

The document identifier (documentId) must be provided in the update request for the above-mentioned fields.

Update Processes

There are 2 different flows for updating a Natural Person:

  1. Death day update - requires only the death day field to be updated,

  2. Update for other data than death day.

Death Day Update

The death day update process is asynchronous and involves several steps:

  1. Partner calls the Natural Person update endpoint with the deathDay field and appropriate documentId,

  2. The system verifies if everything is present and checks if there are any entities (legal entities, natural persons, or joint persons) that have this Natural Person as a proxy and do not have any other active proxy. For each such entity, an admin task is opened,

  3. The Natural Person's death day is updated, statuses for the Natural Person, proxy role, customer role, and the underlying entity (legal entity, natural person, or joint person) are updated, and the process finishes.

Other Data Updates

The process for updating data other than death day depends on the Natural Person's status:

For Natural Persons with ACTIVE status:

  1. Partner calls the Natural Person update endpoint,

  2. The system verifies if everything is present. If an update with restricted data is detected, an admin task is opened,

  3. If the admin rejects the update, the process finishes and a validation error is returned. If the admin approves, the Natural Person data is sent to the KYC system for reverification,

  4. If the KYC response shows issues, a second admin task is opened with the option to globally reject or accept the update,

  5. If the admin rejects, the Natural Person is globally rejected and the process finishes. If the admin approves, the Natural Person is updated and the process finishes.

For Natural Persons with status other than ACTIVE:

  1. Partner calls the Natural Person update endpoint,

  2. The system verifies if everything is present. If an update with restricted data is detected, an admin task is opened,

  3. If the admin rejects the update, the process finishes and a validation error is returned. If the admin approves, the Natural Person is updated and the process finishes.

  4. For persons with status other than ACTIVE, KYC verification is not performed.

How to Call the Update Endpoint

The update is performed by calling the endpoint:

The request structure should contain a NaturalPersonUpdate object with the appropriate fields to be updated:

Last updated