Sent tokens to a contract address? Read the receipt first

A token’s contract identifies the asset; your deposit instructions identify where to send it. If those addresses became confused, preserve the receipt before attempting another transaction.

Does the transaction show failure? Save that status together with any event details. A failed transaction needs a different explanation from a completed transfer; avoid describing both as a successful deposit.

Does it show a transfer? Inspect the recipient in the transfer event on the network actually used. Compare it with the destination entered in the withdrawal form and the token contract in the asset details. Keep these fields separately labelled so support can see where the confusion occurred.

Is the recipient a contract? Ask who controls that contract and whether its documented functions permit the asset to leave. A contract can lack a usable withdrawal function. The exchange you intended to use cannot undo the state of an unrelated contract.

“Can you identify whether this destination is controlled by your platform, and whether any documented rescue mechanism applies?” Attach the receipt and event record.

Enter the signed-in application belonging to your intended recipient: Bitget, Binance, Gate, OKX or Bybit.

A stranger’s “rescue transaction” may request permissions you have not understood. Decline unknown signatures, wallet connections, remote access and advance rescue payments. Never hand over a seed phrase, private key or authentication code. Use an authentication challenge only within an official flow you opened yourself; the account security guide explains that boundary.

Even a clearly identified contract leaves an unresolved question: can its authorized controller perform the required action? Preserve the evidence while that question is assessed, without treating a support conversation as a promise of return.

Review memo and tag when comparing the receipt with receiving instructions.