Give support agents enough information to answer when a customer asks about a TRON USDT deposit or payout. A read-only wallet support view should show the matched transaction, the latest state the platform could verify, and the time of that check. When the records disagree or the status remains unresolved past your team's review threshold, send the case to payment operations.
Open the transaction from the support case
Suppose a verified customer asks why a 75 USDT payout on TRON is still missing. The agent opens the case in the internal console. The support backend uses the customer already associated with the verified case to resolve the authorized account and wallet. It checks the agent's role and access to the case before querying the API. If the agent enters a reference supplied by the customer, the backend uses it only to search within the authorized account and wallet context. The backend also checks that any returned record, including one fetched directly by ID, belongs to that customer before showing it to the agent.
The matched record shows a payout of 75 USDT on TRON with status PENDING at 14:20 UTC. The agent can say, “At 14:20 UTC, your 75 USDT payout on TRON was still pending. We'll check it again at the time agreed for this case.” The console shows the internal reference, operation type, network, asset, amount and status. It records the time of the successful read separately from the transaction's updatedAt and converts amountAtomic using the applicable asset precision. A pending status alone leaves the reason for the delay and the time of completion unknown.
Decide what support sees and when to escalate
| Case evidence | Frontline support | When payment operations takes over |
|---|---|---|
| One matching deposit or payout | See the reference, type, network, asset, amount, status and time checked. | The status remains unresolved past your review threshold, or a failure requires investigation. |
| No clear match or a failed read | See that verification is incomplete. Customer data outside the case stays hidden. | The lookup still fails or the transfer cannot be matched after checking the authorized records. |
| Accounting evidence required | See that accounting review is needed. | Check the related ledger entries when the displayed balance and transaction state disagree or the case needs evidence of a posting. |

In the example, the customer also says their available balance changed. If the agent cannot explain the change from the permitted view, send the case to payment operations with the transaction and wallet IDs, the observed state, the check time and the specific discrepancy. Operations can compare the expected balance effect with the related entries. A POSTED entry records an accounting effect. Use the transaction record and the applicable network evidence to assess confirmation.
Map API scopes to your own access rules
The BroSettlement production OpenAPI v1.0 snapshot from 18 November 2026 documents transactions:read for GET /api/v1/transactions and GET /api/v1/transactions/{id}. The list supports filters including accountId, walletId, clientReference and txHash. The ledger read, GET /api/v1/wallets/{walletId}/ledger-entries, requires wallets:read and supports the transactionId filter. An authorized operations reviewer can use the wallet ID from the verified transaction and its ID as the ledger filter. Production OpenAPI · Operational ledger · Reconciliation
Your integration controls support roles, case-level permissions, server-side filtering and audit logs. Keep API credentials on the server and log the operator, case, record reference, time and access outcome. Keep payout creation, approval and signing in the separately authorized payments workflow. Before rollout, verify effective permissions and field availability in your target environment. Check the active contract for the evidence required to report a payout as confirmed or a deposit as credited. Set escalation time limits in your own support process.
FAQ
Can the console show ledger entries with transactions:read?
The wallet ledger endpoint requires wallets:read. Transaction details can include balanceEffects depending on state. Decide which of those fields, if any, frontline support needs to see.
What if the ledger view is unavailable?
Distinguish an access restriction, a failed read and a successful read with no matching entries. When the case depends on accounting evidence, record which outcome occurred and send the case to payment operations.
For crediting rules, read the TRON USDT deposit integration guide. For the steps before network confirmation, see how to approve USDT payouts on TRON.
