Asset: what does the record represent?
Write down the asset and, where relevant, its exact representation or contract information. A short ticker can be ambiguous. A transfer description should not rely solely on an icon or familiar name.
Network: where is the transaction recorded?
The sending and receiving services must refer to a compatible route. An address format that looks familiar is not enough to establish support. The crypto-payment guide connects the asset and network with the custody arrangement.
Destination: who controls receipt?
A self-managed wallet and a service-controlled deposit account have different responsibilities. A service may also require a memo or tag. Record the applicable requirement from its official instructions; do not guess a missing reference or ask an unrelated person to “fix” the transfer with a new payment.
Status: what stage has been reached?
Submission, network inclusion and credit by a receiving service are different events. Ethereum's transaction documentation explains network processing, but a casino or exchange account adds its own process. Withdrawal timing must include that earlier account stage when the claim concerns a withdrawal.
Our field-completeness test
For a hypothetical record that says only “USDT sent,” the asset label is present but the network, destination requirements and status evidence are missing. The supported conclusion is that the record is incomplete. We do not infer a compatible route or successful credit from the ticker alone.
Keep private keys and seed phrases out of support requests. Technical compatibility does not settle legal eligibility; India-specific research explains that separate question.
Sources and scope
Sources support the specific explanations cited here. They do not certify the platforms in our directory. Rules issued by a national regulator apply within its jurisdiction.
