Getting started with the Travel Rule & Our solutions

Recommended to read first

If you’re new to the Travel Rule or VerifyVASP, explore these resources to understand its core concepts and integration framework. Grasping the background and big picture before starting integration will provide valuable clarity and guidance.

Before starting integration, understand travel rule and VASPs' duties.

Let’s start with the big picture—architecture, main flows, and security features.

Identify your VASP's implementation scope first

For Travel Rule obliged VASP developers

Developers integrating TravelRule can refer to these resources for a step-by-step guide to its core functionalities, architecture, and integration requirements. The documentation includes API specifications, the integration guide, process flows, and architectural details to help you implement TravelRule efficiently and ensure compliance with the Travel Rule and regulatory standards.

Learn the best practice of integration with sequence diagram.

Review the TO-BE VASP architecture and define the implementation scope.

Let's start integration with onboarding. See all action items here.

API specifications that your VASP must provide.

Enclave API specification that helping your VASP connect with counterparty VASPs.

Start your VerifyName integration here: for Travel Rule obliged VASP developers.

For Travel Rule non-obliged VASP developers

If you’re a VASP developer integrating VerifyName, these resources will help you understand its key features, implementation framework, and best practices.

Differences between Post-verification and Pre-verification

Review the TO-BE VASP architecture and define the implementation scope.

Start your VerifyName integration here: for Travel Rule non-obliged VASP developers.

FAQ

Explore the Onboarding FAQ for unresolved answers.

Explore the Implementation FAQ for unresolved answers.

Explore the Maintenance FAQ for unresolved answers.