CryptoSwift

• Name: CryptoSwift
• URL: https://cryptoswift.eu/
• Category: crypto compliance / Travel Rule messaging / self-hosted-wallet verification / compliance workflow infrastructure
• Summary: CryptoSwift is Travel Rule workflow middleware. The useful part is the messaging, scoring, rule-engine, and self-hosted-wallet-verification layer in front of ordinary transfers. Small but real. Not a settlement rail and not some grand new protocol.
• What it does:
  • Sends and receives Travel Rule messages between VASPs through an API and dashboard layer designed to fit alongside existing onchain transaction flows
  • Returns delivery status, counterparty risk signals, and rule-engine outcomes so customers can automate approvals, holds, reviews, or blocks
  • Supports both pre-transaction and post-transaction Travel Rule workflows depending on how tightly the customer wants compliance checks coupled to fund movement
  • Provides self-hosted-wallet verification flows with signature-based, visual-proof, self-declaration, and other evidence options that can be embedded in onboarding, withdrawal, or deposit journeys
  • Publishes developer-facing operational guidance, workflow docs, and references to an open-source Travel Rule protocol called STRIP
• Key claims:
  • The homepage says CryptoSwift is an end-to-end Travel Rule compliance solution for secure VASP-to-VASP data transmission, counterparty-risk evaluation, and automated compliance decisions
  • The About page says CryptoSwift was founded in 2022 to help crypto service providers comply with Travel Rule and Transfer of Fund regulations through a simple, secure API
  • The product FAQ says the platform supports secure message exchange, risk scoring, configurable Rule Engine policies, self-hosted-wallet verification, and easy REST API integration
  • The workflow docs say CryptoSwift provides the messaging and verification layer while customers retain policy decisions, approvals, customer communication, data collection, and risk thresholds
  • The self-hosted-wallet-verification page says evidence options can be matched to risk level and customer capability, with signature-based support spanning EVM networks, Bitcoin, Solana, Tron, and more
  • The product materials explicitly mention support for multiple Travel Rule protocols including STRIP, TRP, TRUST, Sygna Bridge, TRISA, and VerifyVASP
• Whitepaper: A white-paper landing page exists, but in this pass it behaved more like a resource hub than a standalone downloadable technical paper. The clearest current sources of truth were the official homepage, About page, product FAQ, developer portal, and workflow documentation; see ../whitepapers/cryptoswift-primary-sources-2026-04-30.md.
• Sources:
  • https://cryptoswift.eu/
  • https://cryptoswift.eu/about/
  • https://cryptoswift.eu/product/
  • https://cryptoswift.eu/self-hosted-wallet-verification/
  • https://cryptoswift.eu/white-paper/
  • https://dev.cryptoswift.eu/
  • https://dev.cryptoswift.eu/docs/workflows/overview-operating-model/how-cryptoswift-fits-into-your-compliance-operations
  • https://gitlab.com/cryptoswift/strip

Internal linkages

• Keep this note pointed upward: notabene, sumsub, and trisa.

Control surface

• The leverage sits in message-routing coverage, rule-engine defaults, risk-scoring thresholds, which self-hosted-wallet proof methods are accepted, and how tightly those checks are wired into pre- or post-transaction flow.

• Treat CryptoSwift as compliance middleware in front of settlement. The transfer itself is ordinary; the vendor value and risk live in gating, scoring, and workflow defaults.

• Last reviewed: 2026-06-13 UTC