What is CryptoSwift?
Simplifying crypto compliance for every team
CryptoSwift offers a comprehensive Travel Rule compliance platform built for rapid rollout. Product and compliance leads can map policies without touching code, while engineers layer in the API when they are ready.
Throughout the docs we use VASP as shorthand for both Virtual Asset Service Providers and Crypto Asset Service Providers (CASPs).
Who should read this
- Product and compliance: Understand how CryptoSwift supports regulatory obligations and where approval workflows, KYC controls, and escalation paths fit.
- Engineering: See the building blocks you can automate immediately and how they connect to existing systems.
What to review first
- Travel Rule foundations – Start with this overview and the Travel Rule data model so you know which fields your systems must collect.
- Visualise the experience – Share the Travel Rule flow visuals with operations teams to show how messages move between counterparties.
Choose your path forward
- Shape the operating model – Use Workflows & concepts to align stakeholders on policies, approval steps, and compliance triggers.
- Start integrating – Follow Get started to send your first authenticated request, then expand with Travel Rule recipes and Send and receive data examples.
Platform building blocks
API-first integration
The CryptoSwift API exposes every Travel Rule capability through REST endpoints. Pair it with Travel Rule recipes and Send and receive data examples to see end-to-end request and response patterns.
Client Dashboard
The Client Dashboard gives teams a ready-made UI so you can go live without rebuilding every workflow on day one. Automate the high-frequency actions in code and fall back to the dashboard for manual reviews or low-volume scenarios. Every dashboard feature is available via the API, so you can migrate functionality into your own product whenever it makes sense.
How CryptoSwift routes Travel Rule data
Our philosophy is straightforward: compliance should not disrupt the core payment experience. Review the Travel Rule flow visuals for diagrams, then apply the steps below in your own context:
- Collect the Travel Rule payload (originator, beneficiary, beneficiary VASP, wallet details) in your UI or back office tools.
- Execute the blockchain payment as usual.
- Send the Travel Rule message through the CryptoSwift API or dashboard—delivery to the counterparty VASP happens automatically, even if they are not yet on CryptoSwift.
When withdrawals involve self-hosted wallets, pair the flow with self-hosted wallet verification to capture proof of ownership before releasing funds.
Messaging standard
CryptoSwift created the open-source STRIP messaging standard to keep integrations simple, JSON-based, and fully aligned with FATF Recommendation 16 as well as the EU MiCA Transfer of Funds Regulation. It maps directly to the Travel Rule data model documented in this site.