> For the complete documentation index, see [llms.txt](https://docs-legacy.dfns.co/d/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-legacy.dfns.co/d/integrations/travel-rule/overview.md). # Overview ## What is a Travel Rule The Travel Rule is a key anti-money laundering (AML) and counter-terrorist financing (CFT) regulation extended to the cryptocurrency industry. Its fundamental purpose is to increase transparency by requiring Virtual Asset Service Providers (VASPs)—such as crypto exchanges and wallet providers—to collect, verify, and transmit information about the originator (sender) and beneficiary (receiver) for digital asset transfers. The Travel Rule is now a global standard. Digital asset transactions are expected to meet the same identity-sharing requirements as traditional finance. For VASPs, it’s no longer optional. Key regions are leading the way:\ 🇪🇺 EU: Applies to every crypto transfer\ 🇺🇸 US: FinCEN is stepping up enforcement\ 🌏 SG, HK, JP: FATF-based rules are in place Non-compliance can result in fines, suspended licenses, or losing access to banking and payment networks. ## Dfns Travel Rule Support Dfns now offers seamless Travel Rule compliance for its users through a native integration with Notabene, the leading crypto regulatory technology provider. This powerful collaboration embeds Notabene's comprehensive compliance solutions directly into the Dfns Transfers API, enabling developers and financial institutions to effortlessly meet global regulatory requirements. To automate Travel Rule compliance, simply include the optional `travelRule` object when initiating a transaction via the Dfns Transfers API. Our integration then automatically sends the required compliance message to the counterparty and manages their response. This automated compliance check is a component of the Dfns policy engine, handling the entire asynchronous workflow, including webhook notifications, for a seamless experience. #### --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs-legacy.dfns.co/d/integrations/travel-rule/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.