On this page

Wallet Intelligence webhooks

Subscribe to the wallet events on an endpoint in the same environment as the screening. Sandbox and production endpoints and deliveries are separate. Verify the normal webhook signature and deduplicate by the envelope id.

Event	When it arrives
`wallet.screening.completed`	An address result is available.
`wallet.screening.review` / `wallet.screening.declined`	The completed address or transaction result requires review or was blocked.
`wallet.screening.failed`	An address screen failed.
`crypto.transaction.screening.completed`	A crypto transaction result is available.
`crypto.transaction.screening.failed`	A crypto transaction screen failed.

The event body includes the environment, organisation and screening IDs, masked wallet, network and asset, transaction hash when applicable, risk score and level, decision, triggered rule IDs and occurrence time. It does not contain the raw analytics response, secrets or internal cost data. Fetch the screening result for exposures and rule explanations.

json

{
  "environment": "sandbox",
  "organisationId": "org_example",
  "screeningId": "wsc_example",
  "assessmentId": "ras_example",
  "wallet": { "maskedAddress": "0xaaaa…aaaa", "blockchain": "ETH", "asset": "USDT" },
  "transaction": null,
  "risk": { "score": 95, "level": "CRITICAL", "status": "SCREENED" },
  "decision": "BLOCK",
  "triggeredRuleIds": ["wallet_sanctions_direct"],
  "occurredAt": "2026-09-30T12:00:00.000Z"
}

The delivery worker uses the existing signed webhook envelope, retries and idempotency behaviour. screening.* events for ongoing entity screening and fraud.transaction.assessed for transaction decisions remain available. A wallet screening event reports the intelligence result; use the transaction assessment event for the final action on a monitored transaction.

See Webhooks and Wallet screening.