PAY-002Request the remaining payment evidence
Evidence neededTRON · USDT
Follow one small batch from supplied inputs to verified receipts and review follow-up.
Synthetic example · no real payment or live query
Walkthrough needs no login or payment.
Five items total 480 USDT. Two rows reference the same transfer. One has no hash.
| Business ID | Planned (USDT) | Supplied evidence |
|---|---|---|
PAY-001 | 100 | Transfer A |
PAY-002 | 200 | Transfer B |
PAY-003 | 50 | Transfer C (shared) |
PAY-004 | 50 | Transfer C (shared) |
PAY-005 | 80 | No transaction hash |
| Business ID | Verified (USDT) | Finding |
|---|---|---|
PAY-001 | 100 | Matched amount equals plan in supplied transactions |
PAY-002 | 150 | Matched amount below plan |
PAY-003 | 0 | Event shared by business IDs; manual mapping required |
PAY-004 | 0 | Event shared by business IDs; manual mapping required |
PAY-005 | 0 | Payment evidence missing; undetermined |
The shared 50 USDT transfer is excluded from both rows. Missing evidence leaves the final batch difference unconfirmed.
See what needs follow-upFour items need review. Request evidence or assign an owner in Telegram. Human review records do not change chain findings.
PAY-002Request the remaining payment evidence
Evidence neededPAY-003Confirm which business item owns Transfer C
Evidence neededPAY-004Confirm which business item owns Transfer C
Evidence neededPAY-005Provide a transaction hash
Evidence neededActions shown here are examples. Manage your own batch in Telegram after a real check.