> ## Documentation Index
> Fetch the complete documentation index at: https://docs.swipelux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Travel Rule Compliance

> FATF Recommendation 16 compliance for crypto transfers.

## Travel Rule Compliance

Swipelux applies FATF Recommendation 16 controls when transfers exceed the applicable local threshold.

* **VASP-to-VASP:** Swipelux identifies the counterparty VASP and transmits Originator/Beneficiary data via protocol (TRISA/Notabene)
* **Unhosted Wallets:**
  * (a) Swipelux collects required Originator/Beneficiary information
  * (b) No data is transmitted since no receiving VASP exists
  * (c) Transfers may be blocked if blockchain analytics indicate high-risk exposure

Related API workflows: [recipients](/integration/recipients) and [send funds](/integration/send-funds).


## Related topics

- [Overview](/knowledge-base/compliance/overview.md)
- [Governance and Roles](/knowledge-base/compliance/governance-retention-and-privacy.md)
- [Update rule](/api-reference/rules/patch-v3-customers-by-customer-id-rules-by-rule-id.md)
- [Archive rule](/api-reference/rules/delete-v3-customers-by-customer-id-rules-by-rule-id.md)
- [Get rule](/api-reference/rules/get-v3-customers-by-customer-id-rules-by-rule-id.md)