# 01-Integration-Process



01-Integration-Process [#01-integration-process]

<Mermaid
  chart="graph TD
%% Stage 1: CodeVASP Due Diligence
    subgraph Stage1 [1. CodeVASP DD]
        A1[&#x22;CodeVASP DD Assessment Complete&#x22;]
    end

%% Stage 2: Development Integration
    subgraph Stage2 [2. CodeVASP Dev Integration]
        B1[&#x22;API Integration&#x22;]
        B2[&#x22;Dev env Tx/Rx Test&#x22;]
        B3[&#x22;Checklist Review&#x22;]
        B4[&#x22;Dev Integration Done (Prod Deployment)&#x22;]

        B1 --> B2
        B2 --> B3
        B3 --> B4
    end

%% Stage 3: Member Review
    subgraph Stage3 [3. Member VASP Review]
        C1[&#x22;VASP DD Assessment&#x22;]
        C2[&#x22;Assessment Passed&#x22;]
        C3[&#x22;Integration Complete 🎉&#x22;]

        C1 --> C2
        C2 --> C3
    end

%% High-level Process Flow
    Stage1 -.-> Stage2
    Stage2 -.-> Stage3

%% Text Mapping and Contextual Notes
%% Node A1: Represents the completion of initial Due Diligence.
%% Node B1-B4: Represents the technical execution and deployment phase.
%% Node C1-C3: Represents the final regulatory/member assessment and finalization."
/>

1\. CodeVASP DD [#1-codevasp-dd]

CodeVASP conducts our own due diligence on VASPs prior to integration to ensure regulatory compliance and the establishment of a reliable environment. The document submission process for DD is managed through CodeVASP's dashboard. Additionally, we support our member VASPs to carry DD Assessments and document sharing via the CodeVASP Dashboard.

2\. CodeVASP Dev Integration [#2-codevasp-dev-integration]

Once integration is complete, a transmission and reception test will be conducted in the development environment. For these tests, we verify that the API traffic is functioning properly and ensure that all conditions for Travel Rule compliance are met. Before going live, please review the Integration Checklist. Upon completion of these steps, the system will be deployed to the production environment, making it technically capable of communicating with the CodeVASP Travel Rule Alliance.

3\. Member VASP Review [#3-member-vasp-review]

Completing the API integration process with CodeVASP does not automatically enable transactions with all member VASPs. For actual transactions to be enabled, each member VASP typically has an internal review process for connecting with newly onboarded VASPs. This process may include AML/CFT risk assessments, evaluations of business considerations, and reviews of development readiness and operational stability.

VASP entities operating under licensing regimes in regulated jurisdictions generally have their own due diligence procedures. The review process and timeline vary depending on each VASP's internal policies, and the decision to enable transaction integration—along with its timing—is determined based on the outcome of each VASP's due diligence.