Natural Person Management

This document provides an overview of natural person entity preparation and management processes. For detailed information about specific operations, see the related documentation:

Natural Person Preparation

Natural Person Preparation Steps

To prepare a natural person entity, the partner must follow different steps based on whether the person is an adult or a child. For detailed validation rules and process flows of natural person creation and update, refer to the Natural Person Create Process.

Adult Natural Person

To prepare an adult natural person entity, the partner must:

  1. Send natural person data using the POST /entities/natural-persons endpoint

  2. Option A: Send natural person identification data using POST /entities/natural-persons/{naturalPersonId}/identification

  3. Option A: Upload verification document using POST /v2/documents endpoint with the appropriate resourceType ( NATURAL_PERSON) and resourceId (naturalPersonId)

    Option B: Use external verifier method (see Identification Verification section):

    • Create verification request using POST /entities/identification-verifications
    • Retrieve verification link and complete the process
    • System automatically creates identification document and identity record

  4. Sign required documents using the POST /v2/documents/sign endpoint, providing the partnerDocumentId, naturalPersonId, and optionally customerId for terms and conditions

Child Natural Person

Preparing a child natural person entity (under 18 years old) requires:

  1. Create the child's natural person record using POST /entities/natural-persons
  2. Send identification data using POST /entities/natural-persons/{naturalPersonId}/identification
  3. In the child's contact information, provide the contact details of one of the guardians
  4. Upload required documents for the child entity using POST /v2/documents with document type BIRTH_CERTIFICATE
  5. For the guardian of the child, execute POST /v2/documents/sign which requires the natural person id and partner document id. Additionally, it is required to sign a Terms and Conditions document in the context of the customer (customer id should be set in request body) for which the proxy is being set up. Data Privacy Policy should only be signed if the natural person has not already signed it (without customer context)

Guardians for child natural persons will be created separately and linked through proxy relationships during role assignment.

Identification Verification

During the onboarding process, each natural person must be identified as per KYC requirements. Partners have two options for identification verification:

  1. Document Upload Method: Partners can upload a certificate of identification through the POST /v2/documents endpoint (with document type IDENTIFICATION_CERTIFICATE for adults or BIRTH_CERTIFICATE for minors) and create an identity record through POST /entities/natural-persons/{naturalPersonId}/identification.
  2. External Verifier Method: Partners can use the POST /entities/identification-verifications endpoint to initiate an identification verification process with an external service provider (currently supporting WebID with VIDEO_IDENT identification type).

When using the external verifier method:

  1. Create a verification request using POST /entities/identification-verifications with the natural person ID, external verifier type, and identification type
  2. Retrieve the verification link from the response's identificationUrl field or by using GET /entities/identification-verifications/{identificationVerificationId}
  3. Upon successful completion of the verification process, the system will automatically:
    • Create a document of type IDENTIFICATION_CERTIFICATE attached to the natural person
    • Create an identity record (with identifying document metadata such as passport or national ID information)

The verification process status can be tracked using GET /entities/identification-verifications/{identificationVerificationId}, and a list of all verification attempts can be retrieved using GET /entities/identification-verifications.

Natural Person Document Requirements

Document Requirements for Adult Natural Persons

Required Documents:

  • IDENTIFICATION_CERTIFICATE - Required for all adult natural persons (18 years and older)
  • PROOF_OF_RESIDENCE - Required for non-German main addresses (when main address country is not DE)
  • TIN_NA_CONFIRMATION - Required if NoTinConfirmation is set to true in tax details

Document Requirements for Child Natural Persons (Minors)

Required Documents:

  • BIRTH_CERTIFICATE - Required for all minors (under 18 years old)
  • PROOF_OF_RESIDENCE - Required for non-German main addresses (when main address country is not DE)
  • TIN_NA_CONFIRMATION - Required if NoTinConfirmation is set to true in tax details

Important Notes:

  • IDENTIFICATION_CERTIFICATE is NOT valid for minors - only BIRTH_CERTIFICATE is accepted
  • The system automatically validates that minors use birth certificates and adults use identification certificates

Document Signing Process

For Adult Natural Persons:

  • Use POST /v2/documents/sign endpoint with partnerDocumentId and naturalPersonId
  • Optionally include customerId for terms and conditions

For Child Natural Persons:

  • Guardian must execute document signing on behalf of the child
  • Requires natural person ID and partner document ID
  • Must sign Terms and Conditions document in customer context (customer ID required)
  • Data Privacy Policy should only be signed if not previously signed without customer context

Joint Person Preparation

Joint Person Preparation Steps

To prepare a joint person entity, the partner must:

  1. Create the first natural person using POST /entities/natural-persons
  2. Send identification data for the first person using POST /entities/natural-persons/{naturalPersonId}/identification
  3. Create the second natural person using POST /entities/natural-persons
  4. Send identification data for the second person using POST /entities/natural-persons/{naturalPersonId}/identification
  5. Create a joint person using POST /entities/joint-persons with the natural person IDs (np1Id, np2Id)
  6. Upload verification documents for both persons using POST /v2/documents with resourceType set to NATURAL_PERSON
  7. Sign required documents for both natural persons using POST /v2/documents/sign

Joint Person Document Requirements

Required Documents:

  • IDENTIFICATION_CERTIFICATE - Required for both natural persons (if adults)
  • BIRTH_CERTIFICATE - Required for both natural persons (if minors)
  • PROOF_OF_RESIDENCE - Required for both natural persons (for non-German main addresses)
  • TIN_NA_CONFIRMATION - Required for both natural persons (if NoTinConfirmation is set to true in tax details)

Document Upload Process:

  1. Upload verification documents for both persons using POST /v2/documents with resourceType set to NATURAL_PERSON
  2. Sign required documents for both natural persons using POST /v2/documents/sign

For comprehensive information about natural person lifecycle management, refer to these detailed process guides:

Creation Process

  • Natural Person Create Process - Complete guide covering:
    • Validation framework (static and asynchronous validations)
    • Business process flow and outcomes
    • Duplicate detection and review procedures
    • Geographic compliance and NACE sector validation
    • Manual review processes and admin task handling

Update Process

  • Natural Person Update Process - Detailed documentation for:
    • Document requirements for different field updates
    • Status-based update rules (ACTIVE status requirement)
    • Restricted data changes and manual review triggers
    • Death day update special process
    • Geographic and tax compliance validation