Network and account checks
| Asset / network | Confirmation context | Fee evidence | Limits / identity |
|---|---|---|---|
| BTC / Bitcoin | Variable wait; about 10 minutes is an average block interval, not a credit deadline. | Wallet network estimate and any service fee are separate. | Receiving service terms; not defined by Bitcoin. |
| LTC / Litecoin | About 2.5-minute target blocks; required confirmations vary by recipient. | Use the current wallet quote and service schedule. | No universal service limit or KYC exemption. |
| USDT / Ethereum ERC20 | Check transaction status and the recipient confirmation requirement. | Ethereum gas is paid in ETH; account charges may differ. | Exact token and network support must match. |
| USDT / Tron TRC20 | Check chain status and the recipient crediting policy. | Bandwidth/Energy resources; TRX may cover a resource shortfall. | Do not infer support from the USDT ticker alone. |
Read the right record
Begin with the sender receipt, then check the transaction identifier on the correct network. Record the receiving address, token and network exactly as supplied by the receiving service. Do not infer that an account balance must update as soon as a transaction appears in an explorer.
For MMA or boxing accounts, record settlement and payment issues separately. A pending withdrawal can involve an internal review even when the blockchain is operating normally; ask for the stage and written reason instead of accepting an unspecified delay.
Find the waiting stage
If the sender has not issued a transaction identifier, ask whether broadcast has occurred. If a hash exists, check it on the corresponding chain. If confirmations are present but the balance is missing, ask the receiving service about its crediting requirement.
Do not confuse fee quotations
A sender wallet estimate concerns network inclusion. A service can separately show a withdrawal charge or conversion. Record the amount and unit of each entry instead of adding unlike amounts into a misleading total.
Escalate with a concise record
Supply the hash, correct network, timestamp and destination to verified support. Ask whether the case concerns a network state, account review or unsupported asset. A second transfer is not a reliable way to repair an unidentified first transfer.
Evidence and review scope
Reviewed 20 October 2026. Protocol references below do not certify current account fees, limits or eligibility at a particular service.