compliance integrated in your product
Process fully compliant transactions with our crypto wallet identification plugin
Build products compliant by design
Instead of playing a catch-up game, make your product fully compliant from day one
Comply automatically and at scale
Launch a comprehensive compliance mechanism across your entire business
Meet FATF Travel Rule and wallet identification requirements
Integrate once and always comply with the latest regulations
Instantly identify wallet type and regulatory requirements
Identify blockchain address type (custodial, non-custodial) to apply necessary regulatory requirements
Ensure frictionless Travel Rule data collection
If necessary, our dynamic form requests from your customer only the minimum information needed for the Travel Rule
Embed seamless compliance tools in your transaction flows
Integrate our crypto wallet identification plugin with prebuilt dynamic UI components into your product
Comply at scale
Automatically generate Travel Rule transfers. Analyze and transfer data in the background, freeing up your compliance officers to focus on edge cases.
Save valuable time and resources
Pre-built UI components
A fully customizable integration that gives dev teams their time back.
Front-end API
Want to build your own UI? We get it! Our API allows for seamless integration directly into your front-end.
Data integrations
Automatically pull the available data from our integration partners: Chainalysis, Elliptic, TRM Labs and more.
Bank-grade security at every layer
- • Cloud and Infrastructure best security practices
- • Realtime Security Vulnerability Checks before code release
- • All sensitive data is encrypted, at rest and in transport, using battle-tested encryption schemas
• Multiple regions for data storage are available. Full physical data segregation is available for Enterprise customers
Industry’s strongest protection for your customer data
- • SafePII. The industry’s only escrowed exchange of encrypted PII
- • Compliant with EU GDPR, Singapore PDPA
- • Plug-and-play Travel Rule end-user data consent component
Enterprise Ready
- • 24/7 uptime
- • Configurable enterprise SLA
- • SOC2 Type II compliant
• Enterprise-ready authentication mechanisms available
FAQ
Self-Hosted Wallets
Self-hosted wallet verification is the process of verifying the ownership of a self-hosted cryptocurrency wallet. This process is essential for ensuring that only the rightful owner of the wallet can access the funds. Verification is usually done by providing proof of ownership, such as a private key, passphrase, or seed phrase.
The Financial Action Task Force added virtual asset transfers between VASPs and self-hosted wallets to the scope of the Travel Rule in paragraph 179 of the October 2021 updated guidance for VAs and VASPs. Yet, various regulators have varying approaches to transactions between VASPs and self-hosted wallets.
FATF states that when receiving a transaction from a self-hosted wallet, the beneficiary VASP should require their customer (the beneficiary of the transaction) to identify the originator. Additionally, VASPs should take a risk-based approach when interacting with self-hosted wallets and enforce additional risk mitigation measures if necessary.
The FATF and local regulators have generally focused on enforcing AML/CTF controls on transactions that involve intermediaries, such as VASPs or other obliged entities. Thus, crypto transfers between unhosted wallets, so-called peer-to-peer transactions, are not explicitly covered by AML/CTF rules.
The FATF opens the door to a future change of paradigm in case there is a distinct trend toward P2P transactions, as this would necessarily hurt the effectiveness of the AML/CTF frameworks as they exist today.
The FATF and local regulators have generally focused on enforcing AML/CTF controls on transactions that involve intermediaries, such as VASPs or other obliged entities. Thus, crypto transfers between unhosted wallets, so-called peer-to-peer transactions, are not explicitly covered by AML/CTF rules.
The FATF opens the door to a future change of paradigm in case there is a distinct trend toward P2P transactions, as this would necessarily hurt the effectiveness of the AML/CTF frameworks as they exist today.