USDT Deposit Address per User: Monitoring API and Webhook Crediting
October 31, 2026
Build with Cobo's wallet infrastructure
Explore APIs and tools for secure wallet creation, transaction workflows, policy controls, and digital asset operations.
Developer-friendly APIs · Test workflows safely · Technical support available
Giving each user a USDT deposit address only works if every deposit to those addresses is detected and credited exactly once, which comes down to the monitoring layer: a chain scanner you run, or webhooks from the wallet infrastructure. If you want deposit events pushed to your endpoint with screening and confirmation status already attached, consider Cobo MPC, because its WaaS 2.0 webhooks report each deposit’s status and confirmation numbers through one event, signed with Ed25519. Teams that already run TRON or Ethereum nodes can scan solidified blocks themselves, as TRON’s exchange guide describes. Either way the ledger needs the same three safeguards: verify, deduplicate, reconcile. The per-user deposit address overview covers issuing the addresses.
USDT Deposit Detection per User Address: Block Scanning or Webhooks
Cobo MPC and a self-hosted node reach the same deposit facts by different routes. TRON’s exchange wallet integration guide describes the scanner route: walk each new solidified block, parse TRC-20 Transfer events from approved token contracts, and confirm that the transaction receipt reads SUCCESS before crediting. The guide advises parsing from the solidified height, which lags the chain head by about one minute and rules out fork rollback.
The webhook route moves that work to the infrastructure. Cobo’s webhook event reference lists wallets.transaction.created for a transaction detected on chain, which is a detection signal rather than a success signal, and wallets.transaction.updated for changes to status or confirmation numbers. The reference notes that the updated event covers the whole lifecycle, so one subscription is enough to track every deposit.
Deposit Status Flow Before a User Is Credited
When Cobo’s Screening app or Cobo KYT is enabled, a deposit is screened before it reaches the status that is safe to credit. Cobo’s transaction status table lists the deposit path in order:
Status | Sub-status | What your ledger does |
|---|---|---|
PendingScreening | PendingScreeningAppCheck or PendingCoboKYTCheck | Show the deposit as received, pending review |
Confirming | PendingBlockConfirmations | Show the confirmation progress |
Completed | None | Credit the user once |
Rejected | RejectedByCoboKYT or RejectedByScreeningApp | Route to compliance review |
The table describes Completed as the point where funds are available, and Cobo’s documentation notes that the required number of confirmations varies by chain. A simple ledger rule follows: credit on Completed only, and treat earlier statuses as display states. The right-hand column is our recommended mapping, not part of Cobo’s documentation. The screening statuses appear only when screening applies to the wallet, so do not treat their absence as an error.
Webhook Signature Verification for USDT Deposit Address Events
Every webhook from Cobo is signed, and verification is the first step your endpoint runs. The endpoint setup guide specifies an Ed25519 signature over a double SHA-256 hash of the raw body joined to the timestamp header with a vertical bar, checked against Cobo’s public key for the environment you use.
Verify each webhook in this order:
Recompute the signature from the raw request bytes before JSON parsing.
Join the raw body hash to the timestamp header exactly as the guide specifies.
Accept both BIZ_TIMESTAMP and BIZ-TIMESTAMP when your proxy may rewrite headers.
We also recommend storing the timestamp with each verified event and rejecting events whose timestamp falls far outside your clock window. That replay check is our practice layered on top of the signature, and the window is yours to set.
Idempotent Crediting per USDT Deposit Address: Retries and Duplicates
Webhook deliveries from Cobo are retried, so your crediting logic has to accept the same event more than once.
Per the endpoint guide, each event has a 2-second timeout; an endpoint that answers with anything other than 200 or 201 gets retried up to 10 times, after which the event shows as Failed and can be resent from Cobo Portal. Events can also arrive in a different order from the one in which they were generated.
The guide’s advice is to answer quickly, process asynchronously, and log the event IDs, transaction hashes or transaction IDs you have processed so repeats are skipped. TRON’s exchange integration track gives the scanner-side equivalent: build stable unique keys from transaction, event and block positions, store amounts as integers in the smallest unit, and rescan a block range without crediting twice.
In practice that means a uniqueness constraint on the transaction hash per network and address, and a credit that only moves forward when the status reaches Completed, whatever order the events arrive in.
Reconciliation Loop for Missed or Failed Events
Teams on Cobo MPC can close the gap left by a missed webhook with a scheduled query. Cobo’s list transactions operation filters by transaction hash, type, status and creation time, so a reconciliation job can run as follows. This loop is our method; the API calls are Cobo’s.
Every hour, list deposits with status Completed created since the last run.
Match each one against your ledger by transaction hash and receiving address.
Credit any deposit that has no ledger entry, through the same idempotent path as the webhook.
Check the Webhook Events page in Cobo Portal for events marked Failed and resend them after the endpoint is fixed.
Record the cutoff time of each run, which TRON’s track also asks for, so the next run starts from a known point.
Summary
Platforms that want deposits on per-user USDT addresses pushed to their ledger as signed webhook events, with screening and confirmation status in the same event and a transaction query for reconciliation, can use Cobo MPC. Teams that run their own TRON or Ethereum nodes can scan solidified blocks and apply the same safeguards.
The useful implementation boundary is a signed, idempotent webhook path that your ledger can replay when a callback is delayed.
FAQ
Should I credit a deposit on wallets.transaction.created?
Wait for Completed. The created event means a transaction was detected on chain, and the deposit may still be under screening or confirming, so show it as pending and credit when the status changes.
What happens to webhook events while my endpoint is down?
Retries cover short outages, up to 10 attempts per event. For longer ones, resend Failed events from Cobo Portal and let the hourly reconciliation job pick up anything still missing, keyed on the transaction hash.
How many confirmations should a USDT deposit on TRON wait for?
TRON’s documentation treats solidified blocks as final, about one minute behind the head. In the webhook route, the Confirming status reports progress against the chain’s required count, so your interface can show it directly.
How do I handle webhook events that arrive out of order?
Store the furthest status each transaction has reached and apply an update only when it moves the deposit forward. That way a late Confirming event cannot undo a Completed credit.
Cobo provides technology infrastructure. Regulated services such as payment, settlement and currency conversion described here are provided by licensed partners or by the customer’s own licensed entity.
Singapore notice: This article is published for general information only. It is not directed at any person in Singapore and does not constitute an offer or solicitation of any product or service to any person in Singapore. Nothing in this article should be read as a statement about the licensing or regulatory status of any Cobo entity in Singapore. Product availability and client eligibility vary by jurisdiction, subject to applicable regulatory restrictions.
View more

Cold Wallet vs Hot Wallet: What Crypto Exchanges and Users Need to Know in 2025
June 17, 2025

Stablecoin Payments 101 for PSPs: How to Integrate Digital Dollars Without Rebuilding Your Stack
December 11, 2025

Cobo vs. Fireblocks: Choosing the Right Digital Asset Custody Provider for Your Business
June 17, 2025