Crypto Travel Rule compliance solution

CryptoSwift is an end-to-end Travel Rule compliance solution designed to help Virtual Asset Service Providers (VASPs) meet regulatory requirements while securely sending and receiving Travel Rule data, evaluating counterparty risk, and automating compliance decisions for digital asset transfers.

Integrate with CryptoSwift to send and receive Travel Rule data via our API

CryptoSwift delivers your messages, forwards incoming ones from other VASPs, and evaluates counterparty risk

Track transactions and automate compliance decisions using the CryptoSwift client dashboard

Trusted by crypto companies worldwide

Travel Rule Messaging and Compliance Automation

CryptoSwift enables Virtual Asset Service Providers (VASPs) to send and receive Travel Rule data while evaluating counterparty risk and automating compliance decisions for digital asset transfers.

Core Platform Capabilities

Our platform combines secure Travel Rule messaging with risk intelligence and automated policies to help businesses remain compliant with global regulations.

Travel Rule Messaging
Securely send and receive Travel Rule data between VASPs through a global messaging network.
Counterparty Risk Evaluation
Assess the risk profile of beneficiary VASPs or wallets before funds move using the Travel Rule risk score.
Automated Compliance Decisions
Define policies using the CryptoSwift Rule Engine to automatically proceed, review, wait, or block transactions.

Built for developers

Deliver faster with APIs designed for simplicity and efficiency

Save valuable engineering time with a unified Travel Rule API. CryptoSwift handles the complexity of different blockchains, wallets, and Travel Rule networks, allowing your platform to securely send and receive Travel Rule data while focusing on core product development.

Open-source Travel Rule protocol
The CryptoSwift API is built on our open-source protocol STRIP (Simple Travel Rule Information Protocol). STRIP is designed specifically for Travel Rule messaging and is compatible with major regulatory frameworks, including FATF Recommendation #16 and the EU’s MiCA Transfer of Funds Regulation.

Automate your workflows
Using the CryptoSwift API, platforms can create Travel Rule messages, retrieve counterparty risk scores, and automate compliance workflows as part of their transaction processing systems.

curl --location --request POST 'https://api.cryptoswift.eu/transactions' \
--header 'x-api-key: a70fcedf-416b-4f83-845c-a05aba0d7da4' \
--header 'Content-Type: application/json' \
--data-raw '{
    "asset": "BTC",
    "amount": "0.00341",
    "blockchainInfo": {
        "origin": "0xb794f5ea0ba39494ce839613fffba74279579268",
        "destination": "0x71C7656EC7ab88b098defB751B7401B5f6d8976F"
    },
    "originator": {
        "name": "Marwin Hillar",
        "accountNumber": "04143282398",
        "address": "Alexanderplatz 25, Berlin",
        "country": "Germany"
    },
    "beneficiary": {
        "name": "Hanne Nikol",
        "accountNumber": "AB54234232"
    }
}'

CryptoSwift client dashboard

Stay in Control of Your Travel Rule Workflows

Real-Time Monitoring
Track outgoing and incoming Travel Rule transactions in real time and receive instant notifications when message statuses change or counterparties respond.
Automated compliance decision
Define automated policies using the CryptoSwift Rule Engine. Combine signals such as counterparty responses, risk scores, and transaction attributes to automatically proceed, review, wait, or block transactions.
Comprehensive VASP directory
Search and identify thousands of Virtual Asset Service Providers (VASPs) participating in the CryptoSwift network, helping your compliance team quickly determine counterparties and reduce friction in Travel Rule workflows.
AML monitoring integrations
Use your existing AML provider by connecting your own API keys for wallet screening and transaction monitoring. CryptoSwift integrates AML checks directly into Travel Rule workflows without forcing you to change vendors.
Overcome Travel Rule’s “sunrise” challenge
Send and receive Travel Rule data with any counterparty, even if they have not yet implemented a Travel Rule solution. 
Historic transaction lookup
Search historical Travel Rule transactions and view activity from other VASPs on the CryptoSwift network, including transactions broadcast before your integration date.

Wallet verification widget

The easiest way to validate self-hosted wallets

Our wallet verification widget simplifies the verification of self-hosted (non-custodial) crypto wallets as required by Travel Rule regulations. It supports multiple verification methods and integrates easily into your onboarding and transaction workflows.

The widget supports all major wallets and verification methods, including:

cryptographic signature verification (QR code signing)
Satoshi tests
visual proof
user self-declaration

The widget can be used either as a standalone verification tool or embedded directly into your web application as a Web Component.

All functionality is also available through the CryptoSwift API, allowing you to integrate wallet verification directly into your existing transaction flows.

Designed for seamless Travel Rule compliance

Compliance Made Simple, Security Built In

Your business comes first

CryptoSwift integrates into your existing systems without changing your business logic.

Our API is designed for seamless integration, allowing you to keep your current transaction workflows while adding Travel Rule compliance, risk evaluation, and automated decision policies.

Uncompromised Security

CryptoSwift is designed to work with your existing compliance stack. Connect your preferred AML provider using your own API keys and integrate Travel Rule workflows directly into your platform.

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:

- STRIP — open-source protocol created by CryptoSwift
- TRP — OpenVASP Travel Rule Protocol
- TRUST — Travel Rule Universal Solution Technology (closed network)
- Sygna Bridge
- TRISA
- VerifyVASP

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:

Conduct a gap analysis of your current compliance processes.
Choose a Travel Rule solution provider, like CryptoSwift.eu, that aligns with your operational needs.
Integrate the chosen solution into your transaction workflows.
Train your compliance and technical teams on the new processes.
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.