Self-hosted wallet verification, designed for regulated customer journeys
Collect and retain wallet ownership evidence using flexible verification methods integrated into onboarding, withdrawals, or deposit workflows.
A flexible, best-in-class verification experience
A ready-to-use verification experience
Use a responsive, multi-language widget to guide customers through verification. The interface can be themed with your branding, including logo, fonts, and colours.
Trusted by crypto companies worldwide
Fully customisable
Consistent UX without sacrificing control
Apply branding and configuration through theme settings, including logos, typography, and colour schemes.
Try Demo below ↓
Customise the widget
Brand
Logo URL used for branding.
Brand
Logo URL used for branding.
Paste a direct image URL. Clearing the field removes the logo attribute from the widget.
No logo URL set
Typography
Font family, weight, and base sizing.
Typography
Font family, weight, and base sizing.
Search Google Fonts and apply the selected family.
400
16px
Sets the base size.
Colors
Text, button, and widget background colors.
Colors
Text, button, and widget background colors.
Layout
Control how the widget uses the available preview space.
Layout
Control how the widget uses the available preview space.
Make the widget expand to the available parent height and width.
Buttons
Shape and emphasis for primary actions.
Buttons
Shape and emphasis for primary actions.
20px
Multiple verification methods
Evidence options matched to risk level and customer capability
- Cryptographic signature proofs: verification of wallet ownership through cryptographic message signing using the wallet’s private key
- Micro-transactions: small transfers monitored and validated automatically
- Visual proof: supports multi-file uploads (photos and videos) for manual verification workflows
- Self-declaration: a fallback option when stronger evidence is not available
All verification methods can be managed and reviewed through the Client Dashboard, enabling compliance teams to assess, approve, or escalate verification results within a controlled workflow.
Integration options
Embed or redirect: choose the rollout path that fits your stack
Embed the widget as a Web Component for in-app use, or use a hosted redirect flow with a secure verification link. Results are returned via webhook to your backend. For advanced use cases, integrate directly via API.
Supported blockchains
Signature-based verification supports major blockchain ecosystems, including EVM-compatible networks, Bitcoin, Solana, Tron and others depending on wallet connectivity standards.
Where signature or transaction-based methods are not available, the verification flow remains blockchain-agnostic through visual proof and self-declaration options, ensuring consistent coverage across all wallet types.
Audit readiness
Store verification outcomes alongside transaction data and align validity rules with your risk policy to ensure traceability and evidence for compliance decisions.
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)
- Originator Information:
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.
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.
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
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
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
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.