# 01-Policy



01-Policy [#01-policy]

1\. Intro [#1-intro]

1-1. Core Concept [#1-1-core-concept]

* When a legal entity is the sender or receiver of digital assets, &#x2A;*the Travel Rule process remains the same.**
* Just like when a natural person initiates a transfer, a legal entity follows the same sequence— wallet verification → asset transfer authorization → report result — and calls the APIs accordingly.

2\. Policy Alignment [#2-policy-alignment]

2-1. With Corporate Support [#2-1-with-corporate-support]

<Mermaid
  chart="mindmap
    root((Legal Entity Account Support))
        Deposit
            Q1_D[&#x22;Do you accept 'Legal to Legal' deposit?&#x22;]
            Q2_D[&#x22;Do you accept 'Legal to Natural' deposit?&#x22;]
            Q3_D[&#x22;Do you accept 'Natural to Legal' deposit?&#x22;]
        Withdraw
            Q4_W[&#x22;Do you accept 'Legal to Legal' withdraw?&#x22;]
            Q5_W[&#x22;Do you accept 'Legal to Natural' withdraw?&#x22;]
            Q6_W[&#x22;Do you accept 'Natural to Legal' withdraw?&#x22;]
        Optional
            Q7_O[&#x22;If a legal entity has multiple representatives, do you store all of them?&#x22;]
            Q8_O[&#x22;Do you verify all representatives' data for deposits?&#x22;]
            Q9_O[&#x22;Do you send all representative's data for withdrawals?&#x22;]"
/>

The policies to be configured when supporting corporate members are as follows.

In particular, regarding multi-representative entities, CodeVASP's guideline states: 'When processing a withdrawals, include information for all representatives, and when processing deposits, verify all of them.' However, since policies for multi-representative verification are still being established, a flexible approach may be needed in the initial phase. For detailed guidance, please contact the CodeVASP team.

2-2. Without Corporate Support [#2-2-without-corporate-support]

<Mermaid
  chart="mindmap
    root((No Legal Entity Account Support))
        Deposit
            Q1[&#x22;Do you accept 'Legal to Natural' deposit?&#x22;]
        Withdraw
            Q2[&#x22;Do you accept 'Natural to Legal' withdraw?&#x22;]
            Note[&#x22;★Withdrawals to multi-representative entity&#x22;]"
/>

Even if corporate members are not supported, it is still necessary to establish a policy on whether deposits and withdrawals will be allowed when the counterparty is a legal entity.

In particular, when processing a withdrawal to a multi-representative entity, please note that the counterparty VASP may require Travel Rule information for all representatives, depending on its verification policy.

2-3. Common Considerations [#2-3-common-considerations]

* If corporate deposits and withdrawals are allowed, the format of the 'originator' and 'beneficiary' objects may differ. The development team should be aware of this in advance.
* Also, consider whether the UI needs to be updated to allow entry of multiple representatives when handling legal entity withdrawals. Depending on the type of legal entity, there may be more representatives than expected.

3\. Check Counterparty Policy [#3-check-counterparty-policy]

For the implementation of legal-to-legal Travel Rule transactions, it is important not only to design our internal policy properly but also to check the counterparty VASP's policy.

To ensure consistent guidance, CodeVASP is currently collecting and consolidating each VASP's internal policies. If you have established its corporate Travel Rule policy, please share it with us. If you need information about another VASP's policy, please contact the CodeVASP team!
