The ticker matches. Does the deposited asset match?
Identify the token by its contract and actual network before asking receiving support to assess it. A familiar ticker or wallet logo cannot establish that the deposit matches the asset the platform accepts.
“The exchange lists this symbol. Why is the deposit unsupported?”
Compare the deposit instructions with the transfer details. A trading-market entry or a similarly named asset on a different chain does not authorize the route you used. Save the token name, contract and destination together so the question concerns a specific asset.
“My wallet shows a price. Does that prove it is the right token?”
A displayed price cannot establish identity. Read the identifiers in the transfer record instead of relying on a valuation or icon. If you cannot find a corresponding supported entry in the receiving account, report that absence.
“Can support return an unlisted asset?”
Ask whether the destination is under the platform’s control and whether it will assess the transfer. Its policy or technical access may prevent handling. An apparent balance does not establish that the token has a usable transfer function or recoverable value.
“Where should I ask?”
Use help inside the receiving application. Reference profiles are available for Bybit, OKX, Bitget, Binance and Gate. Ask for the applicable conditions and terms; neither success nor timing follows from the token’s name.
“Someone offered to arrange it privately. What should I send?”
Do not give that person a seed phrase, private key, verification code or remote access. Decline wallet connections and advance rescue payments suggested in unsolicited messages. Authentication should happen only in a legitimate flow you chose to open, as covered in account protection.
Keep the official case focused on the mismatch.
Review memo and tag when comparing the receipt with receiving instructions.