Document Management

Overview

The document management system has been restructured to align with the entity-role architecture separation, providing more precise document categorization based on the associated entity or role type.

Document Endpoints

The document management API uses the following key endpoints:

Upload Document: POST /v2/documents/ - Used to upload documents for entities and roles with appropriate resourceType and resourceId
Sign Document: POST /v2/documents/sign - Used to sign documents by natural persons
Get Document: GET /v2/documents/{documentId} - Used to retrieve document metadata
Get Document File: GET /v2/documents/{documentId}/file - Used to download document file content

When uploading or managing documents, always specify the correct resource type that matches the entity or role the document belongs to.

Document Types

Complete Document Types Overview

Document Group	Document Type	Entities/Roles
Company documents	`CURRENT_REGISTRY_EXTRACT` `CHRONOLOGICAL_REGISTRY_EXTRACT` `SHAREHOLDER_LIST` `PARTNERSHIP_AGREEMENT` `TRANSPARENCY_REGISTER_EXTRACT` `STATUTE`	`LEGAL_ENTITY`
Company documents	`BUSINESS_REGISTRATION`	`NATURAL_PERSON` `LEGAL_ENTITY`
Kyc documents	`IDENTIFICATION_CERTIFICATE` `PROOF_OF_RESIDENCE` `KYC`	`NATURAL_PERSON` `PARTNER_USER`
Kyc documents	`BIRTH_CERTIFICATE`	`NATURAL_PERSON` (Minor)
Kyc documents	`DEATH_CERTIFICATE`	`NATURAL_PERSON`
Tax documents	`TIN_NA_CONFIRMATION`	`NATURAL_PERSON`
Tax documents	`W_8BEN_E`	`LEGAL_ENTITY`
Financial situation documents	`SOURCE_OF_INCOME` `SOURCE_OF_FUNDS`	`CUSTOMER`
Proxy documents	`PROOF_OF_SINGLE_CUSTODY` `PROOF_OF_CUSTODY`	`PROXY` (Guardian)
Proxy documents	`INSOLVENCY_ORDER`	`PROXY` (Liquidator)
Proxy documents	`INHERITANCE_LEGITIMATION`	`PROXY` (Power of Attorney in case of death)
General documents	`OTHER`	`NATURAL_PERSON` `JOINT_PERSON` `LEGAL_ENTITY` `PARTNER_USER` `CUSTOMER` `PROXY`

Document Status and Notifications

During the onboarding process, documents go through various status changes:

CREATED - Document has been uploaded
PENDING - Document is being processed during onboarding
APPROVED - Document has been approved and validated
REJECTED - Document failed validation

Partners receive Document Notification webhooks for all status changes throughout the document lifecycle.

Warning

Important: Document processing is asynchronous. After uploading a document via POST /v2/documents/, the document does not immediately reach CREATED status. Partners must wait for the Document Notification webhook confirming the CREATED status before initiating onboarding. Starting the onboarding process before all required documents have reached CREATED status will result in onboarding rejection with a validation error indicating that required documents do not exist for the entity.