v.1.5.0

2025-10-06 - Live

2025-09-23 - Test Environment

Added

• Requestor ID Validation: A unified validation mechanism for requestorId has been Implemented across all relevant endpoints.

  General rule:

  • requestorId must be a UUID of a Natural Person in ACTIVE status.

  • If an endpoint modifies an entity or a role, the requestorId must either:

    • directly represent this entity, or

    • be a Natural Person with a proxy role for this entity.

  Examples of stricter bindings:

  • Customer context (Customer or its Proxy):

    • Create Market Order POST /digital/orders/market

    • Upload Document POST /v2/documents with resourceType = CUSTOMER

    • Create Customer Product POST /customers/{customerId}/products

    • Update Customer Product PATCH /products/{customerProductId}

    • Update Customer PATCH /roles/customers/{customerId}

    • Start Offboarding POST /roles/offboardings (roleType = CUSTOMER)

    • Cancel Offboarding DELETE /roles/offboardings/{offboardingId} (roleType = CUSTOMER)

    • Create Transfer POST /transfers

  • Proxy context (Proxy Natural Person for given Customer/Entity):

    • Upload Document POST /v2/documents with resourceType = PROXY

    • Update Proxy PATCH /roles/proxies/{proxyId}

    • Start/Cancel Offboarding for Proxy role

  • Natural Person context (self or via Proxy):

    • Upload Document POST /v2/documents with resourceType = NATURAL_PERSON

    • Sign Document POST /v2/documents/sign

    • Update Natural Person PATCH /entities/natural-persons/{naturalPersonId}

    • Create Identification Verification POST /entities/identification-verifications

    • Create Natural Person Identification POST /entities/natural-persons/{naturalPersonId}/identification

    • Start Onboarding POST /roles/onboardings (resourceType = PROXY when Customer Proxy is a Natural Person)

  • Legal Entity context (via Proxy):

    • Upload Document POST /v2/documents with resourceType = LEGAL_ENTITY

    • Update Legal Entity PATCH /entities/legal-entities/{legalEntityId}

    • Update Beneficial Owner PATCH /entities/beneficial-owners/{beneficialOwnerId}

    • Update/Delete Legal Representative

    • Start Onboarding POST /entities/onboardings (entityType = BENEFICIAL_OWNER)

    • Start/Cancel Offboarding for Beneficial Owner

  • Joint Person context:

    • Update Joint Person PATCH /entities/joint-persons/{jointPersonId}

    • Start Onboarding POST /roles/onboardings (resourceType = PROXY when Customer Proxy is a Joint Person)\

• Trading Profile Management: New endpoints have been implemented to create and update the basic trading profile for a natural person.

• Natural Person Data Expansion: Added gender and firstName as new updatable parameters to the Update Natural Person endpoint.

  • Description: Updating these fields requires the submission of a KYC document (e.g., new ID, name/gender change certificate).

    • The natural person's status will change to REVIEW.

    • Updating firstName also triggers a re-verification.

• Fictive UBO Validation: Added new validations for updating the uboRelationship on a FICTIVE_UBO.

Changed

• KycNow Service Integration: Expanded integration with an additional transparency register module, enabling the retrieval of more documents.

• National Identifier Recalculation: National identifiers of type CONCAT are now automatically recalculated when a natural person's firstName, lastName, or nationality is updated.