Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


If you have a crypto deposit confirmed on-chain but not credited, first prove what the blockchain recorded, then compare it with the receiving platform's exact deposit requirements. A successful explorer status does not prove that the platform supports the asset-network pair, recognized the destination account, accepted the amount, or posted it to its internal ledger.
Key Takeaways
- Verify the TxID, network, token contract, destination address, amount, and confirmation count independently.
- Compare those facts with a fresh deposit instruction from the receiving account.
- Treat memo/tag errors, unsupported networks, minimum deposits, maintenance, and account review as different branches.
- Contact only official support and never disclose a seed phrase, private key, password, or verification code.
The online security guide explains the independent-channel habit used here: open the platform yourself instead of trusting a support link sent in a message.
It proves that a transaction matching the TxID was included in the selected blockchain according to that network's current rules. It does not prove that the receiving company has credited a customer balance.
Coinbase explains that a transaction can remain pending until it reaches the required confirmations and that the required number can vary by asset. It also advises checking whether the recipient supports the network used.[1] Once the explorer shows success, the investigation moves from “was it included?” to “does this transaction satisfy the receiver's credit rules?”
Use three layers:
| Layer | Evidence | Question answered |
|---|---|---|
| Transaction | TxID and independent explorer | What happened on the network? |
| Deposit route | Current platform deposit instructions | Was this asset, network, address, and memo supported? |
| Account ledger | Deposit history, alerts, and support case | Did the platform recognize and credit the transfer? |
Do not collapse these layers into one status. “Success” on an explorer and “missing” in an exchange account can both be accurate at the same time.
Copy the TxID from the sending wallet or exchange and open a reputable explorer for the actual network. Confirm that the explorer's network matches the network selected by the sender; similar-looking address formats do not establish that match.
Record:
The TxID, addresses, amount, and public token contract are usually public blockchain data. Your seed phrase, private key, password, API secret, recovery code, and one-time code are not required to inspect them. Anyone asking for those secrets is not performing a normal deposit trace.
Take screenshots only if support requests them, and redact unrelated balances or transactions. Plain text TxIDs reduce transcription mistakes and are easier for support to search.
Generate or view a fresh deposit instruction inside the authenticated receiving account. Do not reuse an address from an old message, screenshot, or contact entry until the platform confirms it is still valid for the same asset and network.
Compare the on-chain transaction with the current instruction field by field:
| Field | Required comparison | Common mismatch |
|---|---|---|
| Asset | Same token or coin | Similar ticker, different token contract |
| Network | Same supported chain | Correct address shape, wrong chain |
| Address | Exact destination | Truncated copy or another account |
| Memo/tag | Exact value when required | Missing, wrong, or placed in message field |
| Amount | Meets current minimum after deductions | Network fee leaves net amount below minimum |
| Contract | Official supported token contract | Bridged, wrapped, or counterfeit token |
Binance lists unsupported coins or networks, an incorrect address or memo, deposits below the minimum, and wallet maintenance among reasons a transfer may not be credited automatically.[2] These categories are useful as a checklist, but the receiving platform's current instructions control your case.
If the address itself does not match, stop treating this as an ordinary delayed deposit. Determine who controls the actual destination before taking further action.
Yes. Some platforms set asset- and network-specific minimum deposits. The relevant number is the amount received under the platform's rules, not necessarily the amount the sender entered before withdrawal or network charges.
Check the current minimum shown on the deposit page and compare it with the net on-chain transfer. Do not “top up” automatically: some platforms aggregate later transfers, some do not, and sending more through a wrong route increases the loss. Ask official support whether the deposit is eligible before making another transfer.
Wallet maintenance can pause automatic crediting even while the blockchain operates normally. Look for a notice in the authenticated app or official status page. Record the maintenance message and time, but do not accept a social-media account's claim that it can manually unlock the wallet.
When maintenance ends, the platform may process a backlog. A public estimate is not a guarantee for your account, so preserve the case reference and check the deposit history rather than repeatedly resending.
An unsupported route is not the same as a slow supported deposit. The blockchain may have delivered tokens to an address associated with the platform, while the platform's deposit system does not monitor or credit that token contract on that network.
Binance's self-service recovery documentation describes limited categories that may be eligible for an application, while explicitly stating that recovery is not guaranteed.[3] Eligibility, fees, processing, and technical access depend on the platform and the transaction.
Use this decision boundary:
Do not import a seed phrase into an unfamiliar “recovery wallet,” pay a stranger to contact a validator, or send another token as a supposed unlocking fee.
It can. A platform may show a deposit as pending, reviewing, restricted, or unavailable while it performs account, transaction, sanctions, fraud, or source-of-funds checks. The blockchain cannot display the result of an internal compliance decision.
Check account notifications, verification requests, email received from the platform, and the support case inside the official app. Verify the sender independently before uploading documents. A genuine review may require transaction context or identity evidence, but it does not require your wallet seed phrase or remote access to your device.
Answer requests accurately and retain copies of what you submit. If the request is unclear, ask which policy, transaction, and document field it concerns. Do not invent a payment purpose or edit transaction evidence to speed up review.
Open one case rather than splitting the evidence across duplicate tickets.
Copy-ready support template: “Account ID: [ ]. Asset/network/amount: [ ]. TxID/address/memo: [ ]. Explorer status/confirmations: [ ]. Sender reference/time: [ ]. Deposit-history status and notices: [ ]. Checks completed: [ ]. Please identify any mismatch or internal stage and confirm whether automatic credit, manual credit, or an official recovery process applies. No wallet or account secrets are included.”
Do not send the same deposit again merely to see whether it works. If the route was wrong, repetition compounds the problem; if the platform is delayed, a second transaction creates another case to reconcile.
Do not publish full account screenshots in public forums. A TxID may already reveal addresses and amounts, and combining it with your name, email, exchange, and account balance makes targeted impersonation easier. The Bitcoin privacy explainer shows why public blockchain data should not be mistaken for anonymity.
Ignore unsolicited direct messages from “support,” recovery agents, or administrators. A fraudster may copy your TxID from a public post and use accurate transaction facts to appear legitimate. Open the provider's site yourself and verify the case there.
There is no universal time. Required confirmations, platform processing, maintenance, account review, and the asset-network pair all matter. Use the receiving platform's current status and support information rather than a generic promise.
Yes. Success shows that the network recorded the transaction. The receiving platform may still reject, delay, or fail to recognize it because of its supported network, token contract, address, memo, minimum, maintenance, or account rules.
Not until you know why the first one was not credited. Repeating an unsupported route or incorrect memo can increase the loss, while a processing delay does not need another transaction.
The transfer may reach the platform's shared address without being mapped to your account. Follow the platform's official memo/tag recovery process and provide the TxID and account details; do not send a new transaction unless instructed through that process.
No. Some networks use compatible-looking addresses. Verify the chain, token contract, and supported deposit route in addition to the destination string.
Support cannot reverse a final blockchain transfer. A custodian may sometimes credit or return assets it controls through a manual recovery process, but availability and success are not guaranteed.
Never send a seed phrase, private key, account password, API secret, full recovery code, or one-time verification code. Legitimate transaction tracing uses public identifiers and authenticated account records.
No. A VPN cannot change blockchain confirmations, supported networks, token contracts, a custodian's ledger, wallet maintenance, or account review. Resolve the actual transaction and platform state.
Disclaimer: This article provides general technical and consumer information, not financial, legal, tax, or recovery advice. Platform rules and recovery eligibility vary, and a confirmed transaction may still be unrecoverable.
Sources:
Sources checked 6 September 2026.
Related articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.





