# Types of Travel Rule transfers

Generally speaking, Travel Rule implementation impacts two primary transaction types:&#x20;

* [**VASP-to-VASP Transfers**](https://docs.ospree.io/ospree-api/api-integration-flows#vasp-to-vasp-withdrawal) – When transferring virtual assets between two regulated VASPs, both parties must securely exchange originator, beneficiary, and transaction details to meet compliance requirements.<br>
* [**VASP-to-Self-Hosted Wallet Transfers**](https://docs.ospree.io/ospree-api/api-integration-flows#self-hosted-wallet-withdrawal) – Transactions where a VASP sends or receives funds from a self-hosted (non-custodial) wallet, requiring additional due diligence depending on regulatory requirements. Unlike VASP-to-VASP transactions, transfers involving self-hosted wallets pose additional compliance challenges, as the receiving or sending entity is not a regulated institution. <br>

<figure><img src="https://4249894339-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQg7OS46Jha8pRGgGDSDo%2Fuploads%2FrYCc8UuEtLSdJA1qnZi3%2FOspree%20address%20(2).png?alt=media&#x26;token=3c77d842-04f2-4e50-91a0-fe0759374a4f" alt=""><figcaption></figcaption></figure>
