Address Callback

Overview

Address Callback is an asynchronous notification sent when a tracked blockchain address is assigned, receives activity, or changes confirmation status. It is used to inform payment or wallet systems about address-related events without constant polling. It differs from address monitoring, which is the continuous detection capability that may generate the callback.

A typical implementation works as follows: The provider watches the address, detects a qualifying transaction or state change, constructs an event with network and transaction context, and posts it to the configured handler.

Important failure modes include duplicate, delayed, reordered, or reorganized events, wrong network context, reused addresses, and forged messages. These failures can misstate payment status. For Address Callback, the event identifier, signature result, delivery attempt, and resulting business state should remain connected throughout processing.

Core controls require teams to authenticate events, store delivery IDs, validate asset and network, use idempotency, model confirmations, and reconcile with node or provider state. A receiver should treat transport acknowledgement and successful downstream processing as separate states for Address Callback.

Operational evidence should include address, network, asset, transaction ID, event ID, amount, confirmation state, and delivery history. Address Callback should be documented alongside Address Monitor, Address Indexer, and Callback Verification. Recovery for Address Callback should combine replay controls with an authoritative status check rather than trusting delivery history alone.

A Address Callback handler should acknowledge only after durable receipt when the provider’s retry contract depends on the response. Business actions triggered by Address Callback should be idempotent and should verify the current object state before fulfillment or accounting updates.