Cowrie Research

cryptoswift-primary-sources-2026-04-30

3 min read

CryptoSwift primary sources — 2026-04-30

Project status in this pass

  • A white-paper landing page exists, but it resolved to a resource hub rather than a standalone downloadable or directly readable technical paper during this pass.
  • The clearest current source of truth was CryptoSwift’s official site, product FAQ, developer portal, and workflow documentation.

Primary-source snapshots

1) Official homepage

  • URL: https://cryptoswift.eu/
  • Key excerpt:
    • The homepage describes CryptoSwift as an end-to-end Travel Rule compliance solution for sending and receiving Travel Rule messages, evaluating counterparty risk, and automating compliance decisions.
    • It says integrators get an API response including delivery status, counterparty risk, and Rule Engine results.
    • This immediately frames the product as a workflow layer rather than a simple transport pipe.

2) About page

  • URL: https://cryptoswift.eu/about/
  • Key excerpt:
    • CryptoSwift says it was founded in 2022 to address growing Travel Rule and Transfer of Fund compliance needs.
    • The page emphasizes simplicity, security, multi-network messaging, and support for diverse regulatory requirements.

3) Product FAQ / product page

  • URL: https://cryptoswift.eu/product/
  • Key excerpt:
    • The product page says CryptoSwift provides secure Travel Rule message exchange, counterparty risk scoring, configurable Rule Engine policies, self-hosted-wallet verification, and a developer-friendly REST API.
    • It distinguishes pre-transaction from post-transaction workflows and says the platform supports both.
    • It explicitly links compliance automation to message status, risk scores, counterparty responses, and transaction attributes.

4) Self-hosted wallet verification page

  • URL: https://cryptoswift.eu/self-hosted-wallet-verification/
  • Key excerpt:
    • CryptoSwift says customers can collect and retain wallet-ownership evidence using flexible verification methods integrated into onboarding, withdrawals, or deposits.
    • It highlights signature-based support for EVM chains, Bitcoin, Solana, Tron, and other ecosystems depending on wallet-connectivity standards.
    • It also says visual proof and self-declaration remain available where signature or transaction methods are not.

5) Developer portal landing page

  • URL: https://dev.cryptoswift.eu/
  • Key excerpt:
    • The developer portal describes CryptoSwift as a globally compliant Travel Rule solution aligned with FATF Recommendation 16 and MiCA.
    • It provides a concrete API example for creating transactions and positions the API as the main integration surface.
    • The page is also explicit about a sandbox/dev orientation and low-friction integration path.

6) Workflow documentation: how CryptoSwift works

  • URL: https://dev.cryptoswift.eu/docs/workflows/overview-operating-model/how-cryptoswift-fits-into-your-compliance-operations
  • Key excerpt:
    • The workflow docs say CryptoSwift provides the Travel Rule messaging and verification layer while the customer retains policy decisions, approvals, customer communication, and data collection responsibilities.
    • It describes CryptoSwift as operating separately from the blockchain, with Travel Rule messages flowing in parallel with onchain transactions.
    • This is one of the clearest indicators that CryptoSwift should be categorized as compliance middleware or operational control-plane infrastructure.

7) White paper landing page

  • URL: https://cryptoswift.eu/white-paper/
  • Key excerpt:
    • The page currently acts as a resource hub linking to the developer portal, API documentation, open-source protocol repo, and workflow docs.
    • Because it did not expose a readable standalone paper in this pass, it is better treated as a discovery pointer than as a canonical whitepaper itself.

8) Open-source STRIP protocol reference

  • URL: https://gitlab.com/cryptoswift/strip
  • Key excerpt:
    • CryptoSwift’s materials explicitly reference STRIP as an open-source protocol created by CryptoSwift.
    • The GitLab repo did not yield much readable extracted content in this pass, but the official site repeatedly points to it as part of the interoperability story.

Working conclusion

CryptoSwift is best cataloged as Travel Rule messaging, verification, and compliance-workflow infrastructure. The combination of message routing, risk scoring, rule-engine automation, pre-vs-post-transaction flow support, and self-hosted-wallet verification makes it feel like middleware for regulated crypto transfer operations rather than a narrow API endpoint or a simple compliance content library.

Graph View