waas.* and wallet.* namespaces. They cover blocked transactions, transaction review decisions, and screening verdicts on wallet addresses.
For the shared event envelope, endpoint setup, retries, and signature verification, see Setting up webhooks and Event delivery & best practices. The current list of event types is always available from the event types endpoint.
Policy violations
object
Occurs whenever a transaction is blocked by a configured policy rule. This event provides detailed information about the violation including the denied addresses, all counterparties involved in the transaction, and the reason for blocking. Useful for building allow-only rules, security monitoring, and debugging policy configurations. See Policy Violation Webhooks for more details.
Screening verdicts
object
Occurs whenever one of a user’s wallet addresses is blocked by sanctions /
address screening on a
BLOCKED verdict. Fires once per BLOCKED screening
decision in a user flow (the winning result), not per provider response, and
is not re-emitted on a cache-hit BLOCKED. Only BLOCKED outcomes emit:
OK, FLAGGED, REVIEW, and ERROR do not. The payload contains
walletAddress (lowercase, normalized), chain, sanctionsProvider,
sanctionCheckRequestId, categories (the vendor-returned categories that
triggered the block), origin (the user-flow surface that triggered the
screening, for example signIn, walletConnect, checkoutDestination,
checkoutSource, flowDestination, flowSource, api,
backgroundPrefetch, transactionSigning, or transactionScreenApi; this
enum will grow as new screening surfaces are added), keyOwner (dynamic
or customerProvided), and screenedAt.object
Occurs whenever a wallet address is blocked by a verdict from your own
address screening policy rules or address lists. Split out from
wallet.sanctions.blocked, which now covers only sanctions and the
immutable floor, so you can subscribe to your own policy decisions without
also receiving every sanctions block. Same payload shape as
wallet.sanctions.blocked.object
Occurs whenever a wallet address triggers an
ALERT verdict from your own
address screening policy. Same payload shape as
wallet.sanctions.blocked.Example screening payload
sanctions.wallet.blocked is the deprecated alias of
wallet.sanctions.blocked. Existing subscriptions on the old name keep
receiving the event; it is not advertised in the event types catalog, so new
subscriptions should use wallet.sanctions.blocked.Transaction review
waas.transaction.review.approved and waas.transaction.review.denied are
emitted when a transaction review resolves, but are not selectable in the
event types catalog today.Policy configuration events
Changes to policies, screening policies, and BYOK screening keys by dashboard admins emitadmin.* events: admin.waas.policy.*, admin.addressScreening.policy.*, and admin.addressScreening.byok.*. These are documented with the other admin events under Admin and environment events.