Submit a transaction for monitoring, including subject, counterparty, payment method, custom properties, wallet-risk snapshots, and travel-rule metadata.
Documentation Index
Fetch the complete documentation index at: https://docs.didit.me/llms.txt
Use this file to discover all available pages before exploring further.
Your unique identifier for this transaction (max 128 characters).
Category of the transaction.
finance, kyc, travel_rule, user_event, audit_trail_event, gambling_bet, gambling_limit_change, gambling_bonus_change Core financial details of the transaction.
The subject (applicant) of the transaction.
When the transaction occurred. Defaults to now if omitted.
IANA time zone identifier, e.g. Europe/Madrid.
The counterparty of the transaction (optional).
Arbitrary key-value pairs attached to the transaction.
Travel Rule compliance metadata.
Pre-computed network graph snapshot.
Per-transaction override for crypto blockchain analytics screening. When true, crypto screening is performed regardless of the application default. When false, crypto screening is skipped even if enabled in the application settings. When omitted or null, the application-level default configured in the Console is used. Crypto screening requires transaction_details.direction, currency_kind: "crypto", a chain/currency, and the wallet address selected by the direction: inbound pre-transfer screening uses counterparty.payment_method.account_id, inbound transaction-hash screening uses subject.payment_method.account_id, and outbound screening uses counterparty.payment_method.account_id. When transaction_details.payment_reference_id contains a blockchain transaction hash, Didit performs transaction screening and returns transaction summary enrichment when available.