Deposit Detection

Overview

Deposit detection is the process of identifying an incoming blockchain transaction or ledger credit that may represent a deposit to a monitored account or address. Detection can use nodes, indexers, webhooks, exchange APIs, logs, mempool observation, or ledger files and then progress through execution and confirmation checks.

Detection is not final credit; the transaction can be unconfirmed, failed, replaced, reorganized, unsupported, or unrelated to an active deposit instruction. Related operational concepts include Deposit Mapping and Deposit Attribution. They should remain connected through identifiers and evidence without being treated as the same payment state, control, or financial result.

The workflow for Deposit Detection commonly touches Deposit Mapping and Deposit Attribution . For Deposit Detection, an address-based payment workflow must bind the destination to an exact network, asset representation, account or invoice, custody source, and active period. The authoritative record for Deposit Detection should also show the rule version, responsible system, permitted state transition, and any downstream action such as fulfillment, settlement, refund, or manual review.

Detection is not final credit; the transaction can be unconfirmed, failed, replaced, reorganized, unsupported, or unrelated to an active deposit instruction. Important control concerns include missed blocks, duplicate events, stale indexers, false token logs, unsupported contracts, reorgs, provider disagreement, and credit before execution success. Testing should cover duplicated and out-of-order events, incorrect asset or network data, late transactions, provider outages, retries after uncertain responses, and manual intervention after one subsystem has already changed state.

A production review should make Deposit Detection reproducible from authoritative records, assign an owner for exceptions, and retain the evidence behind each irreversible action. The core control principle is that deposit detection must be durable and reorg-aware, separating observation from successful execution, confirmation, attribution, credit, and settlement.