USDT Unique Deposit Address per User (TRON, Ethereum): Lifecycle and Webhook Documentation

Teams that need one reusable USDT deposit address per user on TRON or Ethereum can use Cobo Payments top-up mode to assign and retrieve the address. A unique deposit address per user is an on-chain address on a single network, such as TRON or Ethereum, that is mapped to one user. The address remains valid for repeated deposits of varying amounts until it is replaced. Automatic crediting requires integrated screening, on-chain confirmation and a completed transaction event. Teams that need to collect a specified amount within a validity period can use order mode instead; teams that need a new address for every payment should not assume top-up mode rotates addresses after each deposit.

Unique USDT deposit address per user

In Cobo Payments top-up mode, a per-user USDT deposit address is an on-chain address on a single network, such as TRON or Ethereum, that is mapped to one user.

Top-up mode assigns a reusable address to each payer and chain. The payer may send varying amounts to that address, which remains valid for repeated top-ups until it is replaced.

Deposit address per user issuance, reuse and replacement

With Cobo Payments, first create the payer, then retrieve one deposit address for that payer and network. Query the current address before each display; repeated requests normally reuse it unless the address has been replaced.

1. Supply the merchant’s merchant_id, the user’s custom_payer_id and the network-specific token_id.

2. Call the Create/Get top-up address operation; it returns the current address for the same payer and chain rather than creating a duplicate.

3. Create an address on another network when the same payer needs to deposit on that network.

4. Use the batch operation to create addresses for multiple payers in one request.

5. A merchant may replace a payer’s address, up to 10 times for that payer. Cobo may also replace top-up addresses automatically in specific situations; the guide does not list every trigger.

After replacement, monitoring continues for the old address. Deposits sent to the old address still trigger webhook notifications and are routed to the same merchant.

User-to-address identifiers for Cobo Payments

Use custom_payer_id as the payer’s unique identifier in the merchant’s system. Cobo assigns merchant_id, while token_id combines the chain identifier and token symbol in the {chain_id}_{token_symbol} format, including TRON_USDT and ETH_USDT.

Top-up transaction events include custom_payer_id with the deposit data.

Cobo Payments private-key separation

In a Cobo Payments integration, the platform can display the payer’s deposit address or QR code without managing private keys.

In a Cobo case study, an online video game platform used the Payments API to assign each user a dedicated top-up address with a one-to-one mapping to the platform account. The platform displayed the address or QR code, while private-key management and on-chain operations were handled and audited under institutional-grade standards.

Merchant systems can restrict API keys through predefined roles, permissions and an IP whitelist. The front end receives the payer’s address and network.

Cobo Payments webhook crediting after screening and confirmation

With Cobo Payments, credit the user only after the deposit has cleared screening and been confirmed on-chain, and credit each transaction exactly once.

Top-up activity generates the payment.transaction.created and payment.transaction.completed webhook events.

Integrated anti-money laundering (AML) and Know Your Transaction (KYT) screening occurs before crediting. If screening flags a transaction, it goes to manual review: it is credited if it passes, and the funds are frozen if it does not. Credit only completed deposits, and use transaction_id as the idempotency key.

Events may arrive out of order. Each event includes custom_payer_id, amount, token_id, chain ID, transaction hash, top-up address and source address for reconciliation.

Cobo Payments network and minimum deposit limits

For Cobo Payments, tell users which network to use and what minimum amount applies: USDT on TRON and USDT on Ethereum are two different deposit instructions, and deposits below the minimum deposit threshold (0.05 USDT or equivalent) are not credited automatically.

Deposits below the minimum deposit threshold (0.05 USDT or equivalent) are not credited automatically. Contact Cobo Support to recover funds that build up below this threshold.

Check the supported list before displaying deposit instructions. An unsupported token or a transfer outside the current deposit plan becomes an unexpected deposit and remains unattributed to a payer or order.

Summary

Teams that need one reusable USDT deposit address per user on TRON or Ethereum, with deposits credited only after screening and on-chain confirmation, can use Cobo Payments top-up mode without managing private keys for deposit addresses. A merchant can request replacement, and Cobo may also replace an address automatically in specific situations; neither means a new address is generated after every deposit. Automatic crediting applies only to completed deposits of supported tokens that meet the minimum deposit threshold (0.05 USDT or equivalent).

Frequently asked questions

Does the same payer get the same address on every request?

Yes, in most cases. Create/Get returns the current address for the same payer and chain. Because an address may be replaced by the merchant or automatically in specific situations, query the current address before showing it to the payer.

What happens to deposits sent to a replaced address?

The old address remains associated with the same merchant, and monitoring continues for webhook events. Display the replacement address for subsequent deposits while keeping events from the old address in the existing processing flow.

Which deposits are not credited automatically?

Automatic crediting applies to supported tokens in amounts that meet the minimum deposit threshold (0.05 USDT or equivalent). Check the supported-token list before displaying deposit instructions. Unsupported tokens, unexpected deposits and amounts below the threshold remain outside automatic crediting.

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.