Over the past year, we have been building partner integrations with companies that need to connect with CryptoSwift in different ways.
Some partners serve licensed VASPs and want to offer CryptoSwift capabilities to their own customers. Others are Travel Rule networks that need to exchange data securely with CryptoSwift customers.
These integrations started as specific partner projects. Over time, the pattern became obvious: the market needs a more open and practical way to connect compliance platforms, VASP service providers, and Travel Rule networks.
So we built that into a dedicated Partner API.
Now we have polished the Partner API, published the documentation, and made it easier for more partners to work with CryptoSwift.
No hidden integration ritual. No “email us and maybe we’ll send a PDF.” Just a clearer way to partner and integrate.
The Partner API is built for two main use cases:
- Resellers: platforms and vendors that already serve licensed VASPs and want to offer CryptoSwift to those customers.
- Travel Rule networks: other networks that want to integrate with CryptoSwift so Travel Rule data can move securely across networks.
The public documentation is available here:
Resellers
CryptoSwift works directly with licensed VASPs. But many VASPs also rely on compliance SaaS platforms, custody providers, core banking providers, onboarding vendors, and other service providers as part of their daily operations.
For these compliance SaaS companies, the Partner API makes it possible to resell CryptoSwift capabilities to their VASP customers.
With the reseller model, partners can offer CryptoSwift platform capabilities through their own customer relationship and commercial setup. This can include Travel Rule messaging, self-hosted wallet verification, dashboard access, onboarding flows, and other CryptoSwift features.
The result is simple: VASP customers get CryptoSwift-powered compliance through a provider they already work with. The reseller adds a proven compliance layer without building one from scratch.
Are you serving licensed VASPs?
If you are a compliance SaaS, platform, or vendor and your VASP customers are asking for Travel Rule compliance, self-hosted wallet verification, or related workflows, let’s talk.
CryptoSwift can help you add these capabilities to your offering.
Travel Rule Network Interoperability
Travel Rule compliance works better when networks can talk to each other.
CryptoSwift customers need to exchange Travel Rule data with counterparties across the market. Some counterparties are inside CryptoSwift. Others are reachable through different Travel Rule networks.
That is where network interoperability matters.
The Partner API gives other Travel Rule networks a clear way to integrate with CryptoSwift, so messages and compliance data can move securely between networks.
This is meant for network-to-network integration. If you represent another Travel Rule network, you can connect with CryptoSwift and support secure data exchange between your network participants and CryptoSwift customers.
The interoperability model supports secure Travel Rule message exchange, VASP discovery and routing, pre-transaction and post-transaction workflows, status updates between systems, secure handling of sensitive payloads, and support for partner-side API models where needed.
We do not expect every network to have the same technical model. That would be convenient, so naturally it is not how the world works.
CryptoSwift can work with external network specifications, routing logic, and security requirements to make reliable cross-network communication possible.
Are you representing a Travel Rule network?
Let’s integrate.
If your network needs to exchange Travel Rule data with CryptoSwift customers, reach out to us. We can work with your team on the integration model and support secure network-to-network interoperability.
Security and Access
Partner integrations deal with sensitive compliance and customer data, so the Partner API is built around controlled access and secure data exchange.
Partner-level access is separated from normal customer API access. Environments are separated. Sensitive payloads are protected using modern encryption and signing mechanisms.
In plain English: partner integrations get their own controlled layer, and sensitive data is treated like sensitive data.
Partner Documentation
The public partner documentation is available here:
The Partners documentation area includes partner-specific integration guidance, environments, authentication, supported flows, and payload schemas.
Work With Us
We built the Partner API because partner integrations should be easier to understand, easier to start, and easier to operate.
It is now available for companies that want to:
- Resell CryptoSwift capabilities to licensed VASPs
- Add Travel Rule compliance to an existing platform or compliance offering
- Support self-hosted wallet verification workflows
- Connect another Travel Rule network with CryptoSwift
- Enable secure data exchange across compliance networks
Review the documentation here:
Or contact us directly: