# Build a TRON deposit notification backend

Updated: 2026-10-19. https://tronhooks.com/docs/use-cases/platform-deposits/

Use tronhooks.com as the notification component of a TRON deposit workflow. It watches USDT/TRX addresses and delivers finalized transfer events; your application owns user-to-address mapping, accounting and reconciliation.

## Responsibilities

| tronhooks | Your application |
|---|---|
| Scan finalized blocks and match watched addresses | Decide which address belongs to which customer |
| Sign and retry callbacks | Verify raw bytes and protect signing secrets |
| Expose delivery history and events | Deduplicate and apply business accounting rules |
| Notify Telegram when selected | Decide how staff respond; don't treat a chat message as a ledger |

tronhooks does not custody funds, generate deposit addresses, transfer assets or guarantee your receiver's availability. A future commercial SLA must not be inferred from a pricing card.

## A dependable receiver pattern

1. Verify the raw request signature before accepting input.
2. Insert the event into a durable inbox with a unique `event_id`; atomically schedule your processing work.
3. Return 2xx once the event is durably accepted, not after a slow downstream workflow.
4. Apply accounting once and keep a reconciliation trail. Preserve decimal strings.
5. Periodically compare your inbox with `GET /v1/events`, paging using `next_cursor`. Missing callbacks and DEAD deliveries need reconciliation, not a second chain transfer.

See [receiver examples](/docs/ai/examples/), [signature verification](/docs/webhooks/) and [API reference](/docs/api/).

## Capacity and scope

Free accounts have three active watches with no daily event cap. Rate limits apply to API calls; receivers and notification channels still have operational limits. Watch creation is not historical indexing. Only currently watched, matching finalized transfers become your events.

Start with an isolated receiver test, then a reviewed watch configuration. No real transfers or notification tests are required to verify the sample integration. [Ask your coding assistant to integrate](/docs/ai/).