A USDT debit on a sending platform does not establish that the recipient has confirmed receipt. Keep the original transaction details and pause duplicate withdrawals or another “test transfer” while you identify the stage involved. If you have already arranged a transaction with Funshell, use the official contact page to ask the team to check that transaction.
This guide concerns transfers already sent. It does not choose a network for you, promise an arrival time or guarantee recovery. Ethereum and TRON appear as technical examples; they do not establish that Funshell accepts those networks or has received your USDT. Confirm accepted networks and receiving details with the team.
Separate the four processing stages
Follow the stages: platform withdrawal processing → network broadcast → on-chain confirmation and execution → recipient processing. Keep the platform's wording, blockchain observations and recipient's reply separate. One type of “success” does not complete every stage.
| What you see | What you can establish so far | Who to ask and what to check |
|---|---|---|
| Platform review, hold or processing; no TXID | Start with the platform's withdrawal process; a debit alone does not prove broadcast | Ask the sending platform's official support whether it broadcast the withdrawal and can provide a TXID |
| A TXID exists, but the matching network shows no record | That lookup has not found a record; it does not prove failure or loss | Recheck the network, TXID and observation time; ask the sender to verify broadcast details and service notices |
| A record is pending or not yet in a block | Network inclusion is not complete | Check the sending service's guidance and keep the original TXID; do not independently resend or add funds |
| A block exists, but execution failed or reverted | Execution has a failure result; do not treat the token transfer as successful | Ask the sending platform or wallet's official support to check the reason, balances and any consumed fees |
| Execution succeeded, but asset, network, address or amount differs | Further investigation is needed | Contact the original sender and intended recipient; preserve records and do not send a replacement yourself |
| The correct token movement, address and amount match, but the recipient has not confirmed | On-chain evidence is available for reconciliation; recipient processing remains unconfirmed | Give the recipient's official support the network, TXID, quantity and transaction reference |
| Recipient confirmed receipt; cash settlement remains outstanding | This concerns settlement of the existing transaction | Ask the original branch or team; another token transfer is not needed |
Platform labels have their own definitions. For example, Kraken's withdrawal status documentation separates internal processing, broadcast and blockchain confirmation. It describes Kraken's process, not a universal arrival standard or Funshell's acceptance requirements.
Find the TXID and match the network
Open the original withdrawal's details in your platform or wallet and look for “transaction hash” or “TXID”. An internal withdrawal reference and a blockchain TXID serve different purposes. If you only have an internal reference, ask the sending platform to clarify. Kraken's official TXID guide illustrates finding it in transaction details; other interfaces differ.
Read the full network name rather than just “USDT”. Tether's official protocol information lists token details on different networks. Match the actual network when looking up a transaction. Open an explorer through your wallet or platform's official interface or verified network information, not an unsolicited recovery message.
Viewing public transaction data should not require a private key, recovery phrase, verification code or signed approval. Stop if someone asks for an “unlock payment” or control of your wallet, and verify through the original official channel.
Read the relevant transaction fields
| Field | What to compare | Common mistake |
|---|---|---|
| Network and TXID | The original withdrawal details | Searching an internal reference or the wrong chain |
| Block and execution status | Inclusion and execution outcome separately | Treating any visible transaction as a completed token transfer |
| Token and contract | Official token details for that network | Trusting only the USDT name or icon |
| Recipient in the token movement | The full address confirmed for this transaction | Mistaking a contract call's top-level To field for the token recipient |
| Token quantity | Transfer details and the withdrawal deduction method | Reading a native-coin value of zero as zero USDT transferred |
| Confirmation state and observation time | Record both; ask the recipient about its requirements | Applying a universal confirmation count or fixed number of minutes |
For an Ethereum token transaction, the top-level To field can identify a contract. Check the recipient in the relevant token movement. See the Ethereum transaction documentation and ERC-20 Transfer event definition for the technical distinction.
TRON's official confirmation documentation also distinguishes broadcast, transaction records and execution receipts. Finding a TXID alone does not prove successful execution or replace the recipient's confirmation. If the fields are unclear, give official support the page link and relevant view instead of guessing.
An illustration of a status report
The following is an editorial illustration, not a blockchain lookup, customer case or redacted screenshot. Its illustrative observation time is 21 October 2026 at 14:00 Hong Kong time (UTC+8). The network only demonstrates how to label fields; it does not promise service support. No real TXID, receiving address or confirmation count is supplied.
| Illustrative field | How to record it |
|---|---|
| Asset and network | USDT; Ethereum mainnet, solely as an example |
| TXID | Copy the full value from the original withdrawal; no real or simulated hash is supplied here |
| Sending time | Use the original platform's time and specify its timezone |
| Observation | Assume the correct token movement shows successful execution, but the recipient has not yet confirmed |
| Address and quantity | Compare the actual full details; this illustration supplies neither |
| Confirmation state | Record the displayed state and observation time; do not assume the store's requirements |
| Next action | Ask the recipient to reconcile those details; do not send another transfer |
Describe this as “on-chain details available, awaiting recipient checks”, rather than “Funshell has received it and only cash payment remains”. The original team must confirm the transaction record and settlement arrangements.
A support request you can copy
Please check an existing transfer. I am not sending another one.
Original branch / transaction reference, if any:
Sending platform or wallet:
Asset and full network name:
Withdrawal reference and platform status:
TXID / matching explorer page, if available:
Requested quantity, fee and displayed delivered quantity:
Receiving address originally confirmed:
Sending time and timezone:
Latest observation time, execution result and confirmation state:
Please check broadcast status, matching transfer details and recipient processing.
Provide necessary details privately through a verified official channel. Do not post account-linked transaction information in public comments or groups. Hide unrelated names, phone numbers, email addresses and account balances in screenshots. Never provide private keys, recovery phrases, login passwords, verification codes or remote-control access.
If you suspect the wrong network, an incorrect address or an impersonated support account, preserve the records and contact the relevant official teams promptly. Available remedies depend on the circumstances; a screenshot alone cannot support a guarantee of recovery.
Next: check the existing transaction or read the buyback process
If this concerns a Funshell transaction, use the official contact page to check it. Troubleshooting does not require a new appointment. If you have not arranged a transaction, read the USDT buyback process: Funshell buys customers' own USDT for HKD cash and does not sell USDT to customers. Confirm the network and receiving details before sending anything.
For a mismatch involving quantity, fees or expected net HKD, see the quote and net HKD checklist.
For the broader in-store process, read the Hong Kong crypto OTC guide. For TRON resource and fee concepts, see the TRX energy and transfer cost guide. An existing transfer still needs the evidence and stage checks above; avoid another transfer or payment while the cause remains unclear.
