WalletAddressScreeningAlertedEventPayload
Payload of the wallet.addressScreening.alerted webhook event: a screening
verdict alerted by the environment's own policy rather than by the sanctions
floor.
Fires once per user-facing boundary decision, not per provider response,
including decisions served from the screening cache. A floor block emits
wallet.sanctions.blocked instead.
chain is deliberately not required: the column is nullable, so a screen
performed without one emits a payload without it.
User-flow surface that triggered the screening which produced
this ALERTED decision. signIn: user login/session verification.
walletConnect: external wallet connect. checkoutDestination:
a destination address in the checkout flow (checkout
create/update or checkout transaction create).
checkoutSource: the from-address funding a checkout
transaction. flowDestination: flow create destination address.
flowSource: the from-address funding a flow. api: direct
wallet-sanctions API query. backgroundPrefetch: background
cache-warming check (see trigger semantics above).
transactionSigning: a decoded transaction destination screened
before the MPC signing ceremony for an embedded wallet
(hard-enforced server-side). transactionScreenApi: a decoded
transaction destination screened for a connected/external wallet
via the public screen API (best-effort, client-side).
This enum will grow as new screening surfaces are added;
consumers should handle unrecognized values gracefully.
signIn, walletConnect, checkoutDestination, checkoutSource, flowDestination, flowSource, api, backgroundPrefetch, transactionSigning, transactionScreenApi Why a screening policy reached its verdict: which layer matched, and what it matched on in the provider's own vocabulary.
Only provider and matched are always present. The rest depend on the
provider and on which leaf actually fired — a floor match on a Chainalysis
cluster carries a category and no riskType.