Use this webhook if your application benefits from knowing about a deposit as soon as it appears on chain, even before it’s finalized. Ideal for UX that wants to pre-notify users of inbound funds, or to start monitoring for large incoming payments.
Important disclaimer: risk of loss!
A transaction that is
Bridge is not responsible for Developer actions or omissions or losses that occur in reliance of these webhooks.
detected here may not ultimately be finalized due to chain reorganization. Please understand your risk and liability before utilizing this webhook.Bridge is not responsible for Developer actions or omissions or losses that occur in reliance of these webhooks.
detected webhook events for a transaction occurring in multiple branches. I.e. transaction with hash X may be seen on a block with hash A and again on a block with hash B. In such a case, two detected webhook events will be sent.
For the purpose of tracking deposits uniquely, be sure to take into account the block_hash, tx_hash, anlog_or_instruction_index.
Be aware that this information is provided to help developers track the status of a deposit on the blockchain, not the state of a transaction within the Bridge system. Even though an indexed deposit is detected or finalized , the transaction may still be incomplete. Use caution when utilizing the information from this webhook.
Applicable deposits
| Chain | Assets |
|---|---|
| Base | USDC EURC |
| Ethereum | USDC USDT |
| Polygon | USDC |
| Solana | USDC |
| Tron | USDT |
| Worldchain | USDC |
Deposit states
Indexed deposits are categorized in one of two states:detected- The deposit has been detected on chain, but has not achieved finality. It is possible that this deposit may not be incorporated into the canonical chainfinalized- The deposit has achieved finality, indicating a higher degree of confidence that it will be incorporated into the canonical chain.
Payload Structure
Webhook payload
| Name | Type | Description |
|---|---|---|
| amount | string | Amount of deposit, e.g. 12340000 USDC would appear as “12.34” |
| to_address | string | Blockchain address of the recipient |
| from_address | string | Blockchain address of the sender |
| block_hash | string | Hash of the block containing this transaction |
| block_number | string | Number of the block containing this transaction (For Solana, this is the slot) |
| block_timestamp | string | Timestamp of the block containing this transaction, e.g. “2025-06-10 15:27:54 UTC” |
| state | string | Either “detected” or “finalized” |
| chain | string | The chain on which the transaction occurred, e.g. “base”, “solana”, “polygon”, etc. |
| currency | string | Currency of the deposit, e.g. “usdc” |
| log_or_instruction_index | string | Top level index of the log or instruction, e.g. “3” |
| memo | string | null; not yet implemented |
| tx_hash | string | Hash of the transaction |
Enabling the Indexed Deposits Webhook
To receive indexed deposit webhooks, you must explicitly enable theindexed_depositevent category on your webhook.
If you already have a webhook configured, update it to include indexed_deposit in event_categories using the Update a Webhook endpoint.
If indexed_deposit is not included, no indexed deposit events will be sent, even if the webhook endpoint exists.
Example