Wallet Intelligence (KYW)

Wallet Intelligence, also called KYW or Know Your Wallet, is a built-in AML Check endpoint for classifying a wallet address before you decide how to handle a transaction. It returns whether CryptoSwift identifies the wallet as CUSTODIAL, NON_CUSTODIAL, or UNKNOWN, together with confidence, attribution, audit, risk, and entity data when available.

KYW does not require an external KYT provider to be activated. It will still use our built-in blockchain analytics tools as an additional source of signal.

Use KYW when you need to:

• decide whether a counterparty wallet is likely custodial or self-hosted
• choose the right Travel Rule or self-hosted wallet workflow before funds move
• store an auditable wallet classification result with your transaction decision
• explain why a wallet was classified in a particular way

Relevant API reference: Get Wallet Intelligence.

GET {{apiBaseUrl}}/aml/kyw/{blockchain}/{address}

curl --location 'https://api-dev.cryptoswift.eu/aml/kyw/Ethereum/0x742d35cc6634c0532925a3b844bc454e4438f44e' \
  --header 'x-api-key: $API_KEY'

Path parameters:

Use the Blockchains API (GET /blockchains) to fetch the current list of blockchain names known to the CryptoSwift platform. Use the returned name value as the blockchain path parameter in the KYW URL.

KYW accepts all blockchains returned by the platform. Coverage depth can vary by blockchain: widely used networks are more likely to have full blockchain analytics and behavioral heuristic support, while less common networks may return a more limited classification based on the signals available to CryptoSwift.

Query parameters:

CryptoSwift validates that the address matches the provided blockchain. Invalid address/blockchain combinations return a validation error. Unknown wallet classifications are returned with HTTP 200 and walletType: "UNKNOWN".

KYW evaluates the wallet through several signal layers:

1. Completed self-hosted wallet verifications. A previous verified self-hosted wallet match is the strongest signal and classifies the wallet as NON_CUSTODIAL.
2. Wallets registered by CryptoSwift platform tenants. A tenant wallet match can identify a custodial counterparty or another known platform entity.
3. Partner-network attribution. When available, network data can connect a wallet to a known entity.
4. Blockchain analytics. When enabled, analytics can identify entity names, entity types, risk scores, and wallet type signals.
5. Known self-hosted wallet apps. Some resolved entities are wallet applications rather than custodians, so KYW classifies them as NON_CUSTODIAL.
6. Behavioral heuristics. If no owner or entity is resolved, KYW analyzes wallet behavior and returns the best available classification with a confidence score.

Every response is persisted as an AML Check history record. The id and auditLogId refer to that stored record.

walletType values:

confidenceScore maps to confidence as follows:

Common attributionReasonCode values:

When KYW resolves the wallet to a known entity, entityInfo can include:

{
  "id": "0f59b0db-3c42-4f2f-9a1f-35c6ccbc4f46",
  "address": "0x742d35cc6634c0532925a3b844bc454e4438f44e",
  "blockchain": "Ethereum",
  "walletType": "CUSTODIAL",
  "confidenceScore": 75,
  "confidence": "HIGH",
  "isVerified": true,
  "attributionReason": "Blockchain analytics identified the wallet owner as Example Exchange.",
  "attributionReasonCode": "DETECTED_VIA_BLOCKCHAIN_ANALYTICS",
  "riskScore": 18,
  "auditLogId": "0f59b0db-3c42-4f2f-9a1f-35c6ccbc4f46",
  "entityInfo": {
    "entityId": "14f4fb9d-4c69-5843-8b18-dbb77540182b",
    "name": "Example Exchange",
    "legalName": "Example Exchange OÜ",
    "type": "exchange",
    "isVerified": true,
    "inNetwork": true,
    "updatedAt": "2026-06-01T10:00:00.000Z",
    "isRiskAssessed": true,
    "description": "Example custodial virtual asset service provider.",
    "isMicaCompliant": true,
    "belongsToWarningList": false,
    "countries": ["Estonia"],
    "url": "https://example.com",
    "riskAssessment": {
      "riskScore": "LOW"
    }
  }
}

{
  "id": "b2ff7a37-42d8-4b2c-9a36-3caa7d8d63d0",
  "address": "0x32Be343B94f860124dC4fEe278FDCBD38C102D88",
  "blockchain": "Ethereum",
  "walletType": "NON_CUSTODIAL",
  "confidenceScore": 90,
  "confidence": "HIGH",
  "isVerified": true,
  "attributionReason": "The wallet has a completed self-hosted wallet verification.",
  "attributionReasonCode": "VERIFIED_SELF_HOSTED_WALLET",
  "riskScore": null,
  "auditLogId": "b2ff7a37-42d8-4b2c-9a36-3caa7d8d63d0",
  "entityInfo": null
}

{
  "id": "7b181f74-6c8f-4c62-8e87-67a8d0797dd3",
  "address": "bc1qexampleaddress000000000000000000000000",
  "blockchain": "Bitcoin",
  "walletType": "UNKNOWN",
  "confidenceScore": 25,
  "confidence": "LOW",
  "isVerified": false,
  "attributionReason": "Behavioral heuristics were inconclusive.",
  "attributionReasonCode": "INCONCLUSIVE_BEHAVIORAL_HEURISTICS",
  "riskScore": null,
  "auditLogId": "7b181f74-6c8f-4c62-8e87-67a8d0797dd3",
  "entityInfo": null
}

For outgoing withdrawals:

1. Collect the destination wallet address and blockchain.
2. Call KYW before initiating the blockchain transfer.
3. If KYW returns CUSTODIAL, continue with your Travel Rule counterparty identification and message flow.
4. If KYW returns NON_CUSTODIAL, apply your self-hosted wallet policy. You may run Wallet Verification if proof of control is required.
5. If KYW returns UNKNOWN, follow your escalation policy. Common options include asking the user to identify the wallet type, running wallet verification, or manual compliance review.
6. Store auditLogId, walletType, confidence, and attributionReasonCode with your transaction decision.

For incoming deposits, use KYW as one signal when deciding whether the origin wallet looks custodial, self-hosted, or unknown. Combine it with Travel Rule message status, transaction risk, customer statements, and your internal AML policy.

• Wallet Intelligence in Compliance Workflows
• Wallet Verification
• Travel Rule Message Flows
• Get Wallet Intelligence API reference