Find the transaction ID from the sending wallet. Confirm it exists on the correct blockchain and that the destination address, asset and any required memo match the Binance deposit page. Then compare confirmation status with account history.
Read the transaction status before sending again
No transaction exists: the sending platform may not have broadcast the withdrawal. A request ID or email is not a TxID. Return to the sender’s withdrawal status and do not open a Binance deposit case as though funds were already on-chain.
Pending or unconfirmed: the transaction exists but has not reached the finality required by the network or receiving platform. Monitor it through an independent explorer reached from the network’s official route. Anyone offering to “speed it up” in exchange for a seed phrase or extra deposit is unsafe.
Confirmed to a different address or network: stop.
Gather the exact destination, asset, network and TxID. Recovery may be unavailable and depends on control of the destination and platform support. Do not send another transfer to test ownership.
Confirmed to the displayed Binance deposit details: compare confirmations, deposit status, memo or tag and any platform maintenance notice. Binance’s missing-deposit guide explains why network confirmation and account crediting are separate. This is the branch where an official support case may be useful.
Compare the deposit details at both ends
| Field | What to compare | Common false match |
|---|---|---|
| Asset | Exact token and contract where relevant | Same ticker used by another token |
| Network | Sender network and Binance deposit network | Assuming compatible-looking addresses prove compatibility |
| Address | Full destination, not shortened display | Matching only the first and last characters |
| Memo or tag | Required extra identifier and value | Treating it as an optional note |
| Amount | On-chain amount and platform rules | Ignoring fees or minimum-credit conditions |
Reopen the current deposit page rather than relying on an old screenshot. Addresses, supported networks and requirements can change. Do not copy an address from search results, chat or a previous user’s deposit instructions.
When the ticker matches but the asset does not
A symbol alone may not uniquely identify a token. On programmable networks, compare the contract address shown by the sending wallet or explorer with the asset information supported by the current Binance deposit page. A token with the same name on an unsupported contract is not made compatible by sharing a network.
Do not interact with an unknown token contract or recovery website merely because the balance is visible on an explorer. Preserve the contract, transaction and destination details and ask official support whether the specific asset-network combination is supported. Platform acceptance can change, so use the current signed-in page.
When the MEMO or Tag is missing
On shared-address systems, the address can identify the platform while the memo, tag or payment ID identifies the account.
A transfer can therefore be confirmed to the correct platform address without automatic credit. Compare the exact deposit instructions and preserve the TxID, asset, network, address, amount and missing or incorrect identifier.
Use the official missing or incorrect MEMO recovery instructions when that route is available for your deposit. Recovery may require evidence and may not be available. Never repeat the same mistake with a larger transfer, and do not pay a person in private chat to alter the ledger.
Why a successful transaction may still be waiting
A block explorer may mark a transaction successful once included, while a platform waits for additional network confirmation or internal risk checks. The required state can vary by asset and network. Check the current deposit page or status information for the account rather than quoting a fixed confirmation number from a tutorial.
Network reorganization, congestion, maintenance and wallet processing can affect timing. Avoid promising a credit time. If Binance shows the deposit as processing, preserve that status and wait for the official next step unless the displayed estimate has passed.
If another exchange sent the funds
The sending service controls the withdrawal record until broadcast. Ask it for the actual TxID and the selected network. A platform-specific transfer ID cannot be searched on a public explorer. If it batched withdrawals, the on-chain amount or destination structure may differ from a simple wallet transfer, so use the official records from both services.
Do not let the sender and receiver redirect you indefinitely. State the observable branch: no broadcast, pending chain transaction, wrong destination, or confirmed correct deposit. Each party can then investigate the stage it controls.
Check the wallet and deposit-history filters
A completed external deposit can be credited to an account wallet that is not the one currently filtered on screen. Search deposit history by asset, network, TxID and date before concluding it is absent, then inspect the wallet destination shown by the record. Do not initiate another on-chain transaction simply to move between internal wallet categories.
Distinguish this from depositing to another Binance user or to a different account under your control. The blockchain destination and memo determine the credited account; changing the visible wallet filter does not repair wrong routing. If the TxID is associated with an account you cannot access, use official support and account-recovery procedures rather than asking another person to forward funds.
What to send in an official support case
- Asset and exact network selected at both ends.
- Full TxID copied from the sending record.
- Destination address and memo or tag, with unrelated data redacted.
- Amount, timestamp and timezone.
- Explorer status and Binance deposit status.
- Sender withdrawal ID if another platform was used.
Share this only through official support. Never include passwords, verification codes, seed phrases, private keys or authenticator backups. Avoid public transaction screenshots that connect an address to your identity.
Use an explorer without oversharing
A public explorer needs only a TxID or address; it never needs a wallet seed, private key or exchange password. Be aware that posting the link can connect account identity with transaction history. Share the minimum record in official support and redact unrelated addresses from screenshots.
After the deposit is credited
Match the credited asset and amount with the on-chain record and note any difference explained by the sending side. Save the original transaction record for accounting. If the transfer was a test, confirm the route again before a larger amount; a successful test reduces some address-entry risk but does not guarantee future network availability or platform eligibility.