CryptoPass

• Name: CryptoPass
• URL: https://cryptopass.com/
• Category: wallet-compliance infrastructure / KYW source-of-funds certification / self-hosted-wallet AML screening API
• Summary: CryptoPass is a small compliance wrapper for self-hosted-wallet proofs and KYW/source-of-funds certificates. The useful cut is the narrowness: three main API functions, a few proof methods, and some AML inputs. Useful if you need that exact workflow; not a broad compliance platform.
• What it does:
  • Offers a wallet-compliance API for businesses integrating self-hosted-wallet verification and screening into their own workflows
  • Exposes a small developer surface centered on three functions: wallet verification, AML screening, and KYW certificate retrieval or generation
  • Positions KYW certificates as reusable source-of-funds documentation for banks, exchanges, tax authorities, and peer counterparties
  • Provides a REST API with a documented https://api.cryptopass.com base URL, /v1 versioning, JSON responses, and separate sandbox and production environments
  • Includes a health-check endpoint and an integration posture aimed at getting a first API call running quickly
• Key claims:
  • The homepage says CryptoPass offers a free AML check for any crypto wallet in about two minutes and helps users prove source of funds with a KYW certificate
  • The same homepage claims support for FATF, MiCA, and 5AMLD compliance positioning, which suggests the product is targeted at regulated or compliance-sensitive workflows rather than informal wallet scoring
  • The developer page says there are “three endpoints” covering wallet verification, AML screening, and KYW certificates, which is a strong clue that the product is intentionally narrow and operational rather than a broad analytics suite
  • The llms-full.txt page snippet says CryptoPass helps verify wallet ownership through the Satoshi Test or WalletConnect QR flows and can produce full KYW certificates with complete AML screening
  • The API docs say CryptoPass lets integrators work with applicant data and transactions through a REST API, uses https://api.cryptopass.com as its base, versions via /v1, returns JSON, and distinguishes sandbox from production environments
  • The docs also expose a simple GET /v1/health example, reinforcing that CryptoPass expects direct machine integration instead of only manual certificate generation through a consumer UI
• Whitepaper: No canonical standalone CryptoPass whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the official site, the developer-facing integrator page, the API docs, and the published llms.txt surfaces, although some of the marketing pages were intermittently fetch-hostile during retrieval; see ../whitepapers/cryptopass-primary-sources-2026-05-04.md.
• Sources:
  • https://cryptopass.com/
  • https://cryptopass.com/integrators/
  • https://cryptopass.com/llms.txt
  • https://cryptopass.com/llms-full.txt
  • https://docs.cryptopass.com/

Internal linkages

• Keep the linkage budget short.
• Best upward reads: aopp for the narrow proof handshake, 21-analytics for the broader self-hosted-wallet verification stack, and verifyvasp for the fuller regulated-transfer workflow layer.

Governance / control risk

• The important questions are which proof methods are accepted, how reusable KYW certificates are trusted by downstream institutions, how AML-screening inputs are sourced, and how far the workflow drifts from prove this wallet into broader identity and funds-legitimacy gatekeeping.

• It is a small tool, but it can still become a hard gate if banks or exchanges start treating its certificate format or accepted proof methods as the default standard.

• Last reviewed: 2026-05-25 UTC