Frequently asked questions

Below are answers to the questions we hear most often from engineering and compliance teams integrating CryptoSwift.

CryptoSwift is a Travel Rule compliance platform that combines a developer-friendly API with an operations-ready Client Dashboard. You can automate the end-to-end lifecycle of Travel Rule messages, while operations teams rely on the dashboard for manual reviews and low-volume workflows.

CryptoSwift is built to satisfy the FATF Travel Rule, EU MiCA Transfer of Funds Regulation, and other global Travel Rule frameworks. The platform uses the open-source STRIP JSON messaging standard to keep integrations simple and compatible with regulatory data requirements.

No. Provide the beneficiary VASP name, email, or other contact details and CryptoSwift will deliver the Travel Rule payload, even if the counterparty has not yet joined the CryptoSwift network.

Reach out to the CryptoSwift team to provision your organisation. We issue separate API keys for the isolated Test and Live environments, each with its own base URLs and dashboard, as described in the API reference.

Every request to the CryptoSwift API must include your environment-specific secret in the x-api-key header. Requests missing the header—or using an outdated key—return 401 Unauthorized. See Getting started for example calls.

Not immediately. The Client Dashboard lets teams send Travel Rule messages, review incoming data, manage wallets, and monitor webhooks without building custom screens. You can migrate functionality into your own product over time while keeping the dashboard for fallbacks.

CryptoSwift supports cryptographic signatures, micro-transaction (Satoshi Test), screenshot uploads, and self-declaration flows for wallet ownership checks. You can implement the flows with the Wallet Verification Widget or integrate directly with the Wallet Verification API.

Outgoing transactions always include the required originator data. For incoming messages, PII is only exposed after the destination wallet is confirmed—check the blockchainInfo.isDestinationConfirmed flag in the transaction payload. Until then, only high-level participant types are visible. Learn more in PII data handling.

Provide high-quality metadata whenever possible:

• Specify whether the destination wallet is CUSTODIAL or NON_CUSTODIAL in blockchainInfo.
• Include the beneficiary VASP name (and email) using the Entities endpoint or data from your blockchain analytics tools.
• Keep your own wallet list current via the Wallets API or dashboard so incoming transfers are recognised immediately. See Improving data quality for additional guidance.

Use the Claim Transaction endpoint to submit the transaction hash and wallet details. CryptoSwift searches for existing Travel Rule data, notifies you if any is found, and follows up with the originator VASP when information is missing.

Register a webhook URL to receive JSON payloads for Travel Rule transactions and self-hosted wallet verification events. Verify authenticity with the CryptoSwift-Signature header as outlined in Webhook signatures. Setup steps are covered in Webhooks.

Yes. Our engineering team routinely supports customers with solution design, implementation reviews, and custom integration questions. Contact us to discuss how we can help.