Sources checked

How we checked this

We reviewed the linked sources and keep this page updated when the record changes. Use the source list below to verify the details.

Source links attached Safety context included Corrections open

Short answer

A transfer can appear complete to you without being fully resolved from the platform’s side. In practice, the safest first move is not to guess whether the problem is user error, delay, or something worse, but to preserve a clean record of what you sent, when you sent it, and which instructions you followed. Use only the exchange’s verified support route, and do not share seed phrases, private keys, passwords, or remote-access control with anyone claiming they can fix the issue for a fee.

Context

When users say a deposit has “cleared,” they may mean different things: a wallet shows sent, an app shows completed, or a blockchain explorer shows a successful transaction. Those records can be useful, but they are not the same as an exchange account credit. If the exchange balance does not update, the first priority is to document the event carefully rather than assume theft, misconduct, or guaranteed recovery.

This evidence-first approach also helps if the real risk is not the transfer itself, but a follow-up scam. Cybersecurity and public-sector safety guidance consistently favors preserving records, using official channels, and avoiding unverified helpers who move conversations into private messaging or ask for sensitive credentials.

Which records matter first

Before contacting support, gather the records that let you explain the problem clearly and consistently:

  • transaction hash or explorer link
  • asset name as shown in your wallet or transfer record
  • network used
  • recipient address
  • memo, tag, or payment identifier if one was used
  • amount sent
  • date and time sent
  • screenshots of the deposit instructions you followed
  • wallet confirmation screenshot
  • any case or ticket number once you contact official support

Do not send private keys, seed phrases, passwords, device unlock codes, or remote-desktop access to anyone offering help.

Step-by-step guide

1. Preserve the transfer record before you retry anything

Save the transaction reference, screenshots, and timestamps first. Good records reduce confusion later, especially if you end up comparing what your wallet showed with what the platform asked you to do.

2. Compare what you sent with the instructions you actually used

The most useful comparison is not memory versus memory. It is your transfer record versus the deposit instructions visible at the time you checked them. If you relied on an old screenshot, an old bookmark, or a copied address from a previous transfer, note that for support rather than guessing.

3. Contact support only through verified channels

Use the exchange website or app directly. Avoid replies in comment threads, direct messages, chat apps, or accounts that appear only after you publicly complain. If someone immediately asks for wallet credentials or promises a paid “manual unlock,” treat that as a serious warning sign.

4. Keep your explanation factual and narrow

A short, well-organized report is usually more useful than a long emotional one. Include the transaction reference, amount, date, receiving details, and screenshots. Avoid speculating about hacks, insider theft, or guaranteed reversal unless you have evidence from official records.

Comparison table: what each record helps prove

RecordWhat it can help showWhat it does not prove by itselfWhy it matters early
Transaction hashThat a transfer record exists and can be referenced consistentlyThat the exchange has credited your accountIt gives support a concrete starting point
Recipient addressWhere you intended funds to go according to the transfer recordThat the destination was mapped correctly inside the exchangeIt helps compare your transfer with deposit instructions
Memo, tag, or payment IDWhether extra routing information was included in your recordsThat a platform accepted or processed it correctlyIt can be critical when support checks routing details
Wallet confirmation screenshotWhat your wallet displayed at the time of sendingThat the platform’s internal systems recognized the depositIt preserves visible details before apps update or logs change
Deposit instructions screenshotWhat information you relied on when making the transferThat support must resolve the case in your favorIt is often the best evidence for a later comparison
Support ticket numberThat you reported the issue through an official routeThat the case will end successfullyIt creates a traceable support record

A single record rarely proves the whole case. The goal is to build a consistent file that shows what happened, what you followed, and what still needs clarification.

Checklist: the first 15 minutes

  1. Save the transaction hash and a direct link to the transfer record if available.
  2. Record the asset name, amount, and time sent.
  3. Capture the recipient address and any memo, tag, or payment identifier.
  4. Screenshot the deposit instructions you used.
  5. Screenshot your wallet or app confirmation page.
  6. Contact support through the exchange’s verified website or app.
  7. Save the case number and every reply.
  8. Ignore anyone asking for payment, seed phrases, or remote access to “recover” the deposit.

Red flags after a missing-deposit complaint

A missing-deposit problem often attracts impersonators and recovery scammers. Be cautious if someone contacts you first, shifts you to a private chat app, asks for urgent payment, or requests wallet secrets or remote control of your device. Public-interest cybersecurity guidance consistently treats those behaviors as warning signs, not normal support practice.

Bottom line

If a deposit appears to have cleared but your exchange account still does not show it, the most useful first step is record preservation, not speculation. Build a simple evidence pack, use verified support channels only, and treat any request for wallet secrets or paid “recovery” access as a danger signal.

Sources

Update log

  1. 10 Jul 2026Published with source tracking and reader-safety context.
  2. CorrectionsIf a source changes or a claim needs clarification, this page can be updated from the editorial desk.