Proxy Onboarding Process

This document describes the overall process for onboarding existing proxies on the platform, from initial data submission, through validation stages, to the final onboarding of the proxy record or handling of exceptions.

Overview

The Proxy Onboarding Process ensures the integrity and compliance of proxy data modifications by performing comprehensive validation procedures. This process maintains data quality standards, ensures regulatory compliance, AML/KYC compliance verification and handles proxy relationship updates efficiently across all platform operations.

Prerequisites

Partners need to:

  • Have an existing proxy with appropriate status for onboarding (CREATED)
  • Gather all required onboarding information
  • Ensure proper authorization to onboard the proxy
  • Provide required documents for onboarding

Validation Types

The proxy onboarding process includes two types of validations:

1. Asynchronous Business Validations

These validations are performed asynchronously after the endpoint returns a successful response. Results are delivered via webhooks or notification systems. They include complex business logic and compliance checks specific to proxy onboarding.

Asynchronous validations include:

  • Existing proxy and related entity retrieval and status verification
  • Proxy type-specific onboarding validations
  • Document type and resource type validation for required documents

2. KYC Validations

This validation is done asynchronously after business validation are completed successfully. This step aims at verifying customer identity.

Business Process Flow

The onboarding process follows a structured workflow:

  1. Command Event Publishing - Proxy onboard command event is published
  2. Asynchronous Business Validation - Comprehensive verification and routing decisions
  3. KYC - KYC verification and routing decisions
  4. Proxy Onboarding - Official onboarding in the system
  5. Exception Handling - Management of rejected or problematic cases

How to Call the Onboard Endpoint

The onboard request is performed by calling the endpoint:

POST /roles/onboardings

Validation Framework

Data Quality Assurance

The validation process performs thorough checks to ensure data accuracy and completeness:

Business Validation Steps (Asynchronous)

  1. Proxy Existence and Status Validation

    • Retrieves the existing proxy by UUID
    • Verifies proxy exists and belongs to the correct partner
    • Verifies proxy status allows onboarding (CREATED)
    • Returns validation error if proxy is not found, not accessible, or has inappropriate status

  2. Related entity Existence and Status Validation

    • Retrieves the existing related entity by UUID
    • Verifies related entity exists and belongs to the correct partner
    • Verifies related entity status allows onboarding (ACTIVE)
    • Returns validation error if related entity is not found, not accessible, or has inappropriate status

  3. Natural Person Validation

    • Verifies natural person status allows onboarding (CREATED, PENDING or ACTIVE)
    • Verifies IDENTIFICATION_VERIFICATION document is uploaded for the np
    • Verifies np has identification added
    • Verifies np has all partner documents signed

  4. Proxy type specific validation

    • If proxy type is GUARDIAN:
      • if custody type is SINGLE_CUSTODY, proxy need document of type PROOF_OF_SINGLE_CUSTODY uploaded
      • if last name of proxy np and related natural person does not match, proxy need document of type PROOF_OF_CUSTODY uploaded
    • if proxy type is GENERAL_POWER_OF_ATTORNEY:
      • if custody type is IN_CASE_OF_DEATH and custody type is SINGLE_CUSTODY, proxy need document of type INHERITANCE_LEGITIMATION uploaded

KYC Steps (Asynchronous)

KYC (Know Your Customer) verification is an integral part of this process, ensuring compliance and mitigating risks. It involves validating the identity of natural persons and ensuring all necessary identification and partner documents are in place and verified

Business Outcomes

1. Asynchronous Validation Failure

When it occurs:

  • Proxy not found or not accessible by partner
  • Proxy has inappropriate status for onboarding
  • Related entity customer not found or not accessible by partner
  • Related entity customer has inappropriate status for onboarding
  • Related entity has inappropriate status for onboarding
  • Proxy natural person not found or not accessible by partner
  • Proxy natural person has inappropriate status for onboarding
  • Proxy natural person does not have IDENTIFICATION_CERTIFICATE document
  • Proxy natural person does not have identification
  • Proxy natural person did not sign all partner documents

Business Impact:

  • Proxy onboarding is rejected
  • Partner receives detailed validation error notification via webhook/notification
  • Proxy remains in its original state

Next Steps:

  • Address the specific validation failure based on error details received in webhook
  • Ensure proxy has appropriate status for onboarding
  • Resubmit proxy onboarding request after resolving validation issues

3. Successful Onboarding

When it occurs:

  • All validations pass (asynchronous and KYC)

Business Impact:

  • Proxy is successfully onboarded in system
  • Partner receives success notification via webhook/notification

Business Rules

Onboarding Eligibility

  • Proxies can only be onboarded if status is CREATED
  • Partner must have proper authorization to onboard the proxy

Natural Person Identification Requirements

  • Document with type IDENTIFICATION_VERIFICATION must be uploaded for proxy np
  • Natural person must have identification added

Partner documents signatures

  • Proxy natural person must have all partner documents signed

Guardian Proxy Rules

  • If proxy custody type is SINGLE_CUSTODY, proxy must have document of type PROOF_OF_SINGLE_CUSTODY uploaded
  • If proxy last name is different than related natural person last name, proxy must have document of type PROOF_OF_CUSTODY uploaded

Signatory Proxy Rules

There are no additional rules for signatory proxy

General Power of Attorney Rules

  • If proxy validity type is IN_CASE_OF_DEATH, proxy must have document of type INHERITANCE_LEGITIMATION uploaded