Book Demo

VASP Directory with risk and regulatory context, built for Travel Rule operations

Identify counterparties, validate coverage, and support risk-based decisioning with a directory embedded directly into Travel Rule workflows.

Get started

Why it matters

Counterparty identification is one of the highest-friction points in Travel Rule operations. The directory reduces manual research and improves message delivery by making VASP context available during transaction creation, review, and escalation.

VASP information

Structured records, not a static list

CryptoSwift maintains a directory of 2,500+ crypto service providers, with records that can include contact details, jurisdictions and compliance indicators, web presence, and network participation status.

Book a demo

Risk Score

Risk assessment available as structured data



 

Directory entities include a risk score and severity level, supporting automated policies and consistent review workflows. Risk ratings are enhanced for verified network members.

Jurisdictions and compliance indicators

Regulatory context as a first-class attribute



 

Where available, entities include jurisdiction data and compliance indicators, helping teams quickly assess regulatory posture.

Registered countries and legal entities

Legal entity breakdown for due diligence and audit trails



Entity records include legal name, country, registration identifiers, regulatory references, and regulator details, supporting traceable and auditable counterparty identification.

How it’s used

Improve delivery success by enabling users to select beneficiary VASPs during transaction creation, supporting better routing and reduced failure rates.

Book a demo

Frequently Asked Questions

 

What is the Crypto Travel Rule? The Crypto Travel Rule, introduced by the Financial Action Task Force (FATF), requires Virtual Asset Service Providers (VASPs) to share specific customer information when transferring virtual assets between entities. This rule aims to combat money laundering and terrorist financing by improving transparency in crypto transactions.
Who must comply with the Travel Rule? VASPs, including cryptocurrency exchanges, wallet providers, custodians, brokers, and financial institutions handling virtual asset transactions, must comply. Compliance depends on the jurisdiction, but it generally applies to entities transferring cryptocurrencies above a specific threshold. In the European Union, under the Transfer of Funds Regulation alongside MiCA, there is a 0 EUR threshold, meaning all transfers are subject to the Travel Rule, regardless of the transaction amount.
What customer information must be shared under the Travel Rule? Under the Travel Rule, VASPs must transmit the following information for transactions:
    • Originator Information:
      • Name
      • Account number (or unique transaction identifier)
      • Physical address or national identity number (depending on jurisdiction)
    • Beneficiary Information:
      • Name
      • Account number (or wallet address)
The exact information required may vary depending on the jurisdiction’s regulatory framework.
How does the Travel Rule impact crypto exchanges and banks?
Compliance with the Travel Rule typically requires:
    • Data Collection: ensuring accurate customer information is collected during onboarding and transactions.
    • Secure Transmission: exchanging customer information securely between counterparties.
    • Transaction Monitoring: identifying and flagging suspicious transactions for further investigation.
    • Risk-based decision making: determining whether transactions should proceed, be reviewed, or blocked.
Non-compliance can result in fines, reputational damage, or loss of operational licenses. In the EU, the Travel Rule applies to all transactions, while other jurisdictions may enforce thresholds such as USD 1,000 equivalent.
What are the technical challenges of implementing the Travel Rule?
Key challenges include:
    • Interoperability — ensuring compatibility between multiple Travel Rule protocols and counterparties.
    • Data privacy — protecting customer data while complying with regulations such as GDPR.
    • Real-time compliance — exchanging Travel Rule data without slowing down transaction processing.
    • Counterparty identification — verifying the identity and legitimacy of other VASPs.
    • Automated decision workflows — determining whether transactions should proceed, be reviewed, or blocked based on compliance policies.
What solutions does CryptoSwift.eu offer for Travel Rule compliance?
CryptoSwift provides an end-to-end Travel Rule compliance platform that enables crypto businesses to:
    • Send and receive Travel Rule messages securely between VASPs.
    • Evaluate counterparty risk using Travel Rule risk scoring.
    • Automate compliance decisions using configurable Rule Engine policies.
    • Verify self-hosted wallets through integrated wallet verification tools.
    • Integrate easily via a developer-friendly REST API.
The platform is compatible with major regulatory frameworks including FATF Recommendation #16 and the EU MiCA Transfer of Funds Regulation.
What is the difference between pre-transaction and post-transaction Travel Rule workflows?
Post-transaction workflows send the Travel Rule message after the blockchain transaction has already been broadcast. This is often the fastest way to become compliant with minimal changes to existing withdrawal flows.Pre-transaction workflows send the Travel Rule message before the blockchain transaction. This allows platforms to evaluate counterparty risk, receive Travel Rule responses, and apply compliance policies before funds move. CryptoSwift supports both approaches.
What is the Travel Rule risk score?
The Travel Rule risk score evaluates the risk profile of the counterparty VASP or wallet associated with a transaction.VASPs can use the score to:
    • automatically approve low-risk transactions
    • flag medium-risk transactions for review
    • block high-risk counterparties
Risk scoring can be used directly through the API or combined with the CryptoSwift Rule Engine to automate compliance workflows.
What is the CryptoSwift Rule Engine?
The Rule Engine allows compliance teams to define automated policies for Travel Rule transactions.Rules can combine signals such as:
    • Travel Rule message status
    • counterparty responses
    • risk scores
    • transaction attributes such as amount
Based on these rules, transactions can automatically proceed, be reviewed, wait for additional information, or be blocked. Rules are configured in the CryptoSwift client dashboard.
Is the Travel Rule only for international transactions?
No, the Travel Rule applies to both domestic and international transfers. In the EU, MiCA mandates that all transactions, irrespective of the amount or origin, comply with the Travel Rule. In other jurisdictions, the rule may apply to transactions exceeding specific thresholds, so it is essential to verify local regulations.
What is the threshold for Travel Rule applicability?
Under FATF guidance, the recommended threshold is USD 1,000 or €1,000 equivalent. However, MiCA in the EU sets a 0 EUR threshold, meaning all transactions, regardless of amount, are subject to compliance. Thresholds in other jurisdictions may differ based on local regulations.
Does the Travel Rule apply to DeFi transactions?
Currently, the Travel Rule primarily applies to VASPs, not decentralized finance (DeFi) platforms. However, regulatory scrutiny of DeFi is increasing, and future guidance may impose similar requirements on some DeFi-related services.
How does the Travel Rule align with GDPR and data privacy laws?
CryptoSwift.eu helps customers align Travel Rule compliance with GDPR and other data privacy requirements by:
    • minimizing the data collected and transmitted
    • using encryption to secure sensitive information
    • supporting jurisdictional privacy requirements while maintaining transparency for regulators
What protocols are available for Travel Rule compliance?
Several protocols have emerged to standardize Travel Rule compliance, including: Different Travel Rule solutions may support one or more of these protocols.
How can I start implementing the Travel Rule in my organization?
To start:
  1. Conduct a gap analysis of your current compliance processes.
  2. Choose a Travel Rule solution provider, like CryptoSwift.eu, that aligns with your operational needs.
  3. Integrate the chosen solution into your transaction workflows.
  4. Train your compliance and technical teams on the new processes.
  5. Monitor and adapt to regulatory changes.
How can CryptoSwift.eu help me stay ahead of regulatory changes?
CryptoSwift.eu monitors global regulatory developments and updates its solutions accordingly. With our platform, you gain access to up-to-date compliance tools that help you remain aligned with evolving requirements, including the strict MiCA and Transfer of Funds Regulation requirements in the EU.
Can I test CryptoSwift.eu’s Travel Rule solution before full integration?
Yes, CryptoSwift.eu offers a sandbox environment for testing. This allows your compliance and technical teams to:
    • simulate Travel Rule transactions
    • validate data security and accuracy
    • test counterparty interoperability before live deployment
    • validate risk scoring and compliance workflows
How do I get started with CryptoSwift.eu?
Contact us through our Book a Demo page to schedule a demo or request more information. Our team will guide you through onboarding and help tailor the solution to your specific compliance needs.