Crypto Transfer Confirmed but Deposit Missing: How to Find Out Where Your Money Is

A confirmed crypto transfer can still be missing from your exchange account. Check where the money went, what is delaying credit, and which evidence support needs.

Your sending app says Completed, the explorer shows a confirmation, but the receiving account shows nothing. These report different stages: withdrawal processing, blockchain activity, and exchange credit.

Confirmation does not prove your account was credited. Even a green Success label may describe an operation that did not make your intended payment. Check the actual asset, amount, and recipient before sending again.

Quick check: which problem do you have?

No transaction on the correct network: ask the sender for the correct transaction ID or internal transfer record.
Pending, failed, or reverted: investigate through the sending wallet or service.
Success, but no matching payment: it may be an approval or another operation. Find the actual asset transfer.
Wrong network or unsupported token: check the receiving platform's recovery process.
Too few confirmations: wait for the requirement for that asset and network.
Requirements met, but no deposit: check maintenance and account notices, then ask receiving support to investigate.
Credited, held, or restricted: the platform has a record. Check its status and account location to understand availability.

For a wallet you control yourself, use the blockchain checks first, then the self-custody section below.

Why confirmation and exchange credit are separate

After a transaction reaches the blockchain, the exchange must detect the payment, check its asset, network, amount, deposit instructions, and confirmations, then match it to a customer and complete any reviews before crediting the account. Some checks run together.

Coinbase's developer documentation describes a separate customer ledger for deposits, withdrawals, trades, and fees. An explorer shows blockchain activity, not every entry in that private ledger. Credit and permission to withdraw can also be separate stages.

1. Find the actual transaction ID

In the sending app, look for Transaction ID, Transaction hash, TxID, or a Solana transaction signature. Order numbers, withdrawal references, support references, and block numbers are different identifiers. Keep the withdrawal reference separately.

Use an explorer for the network actually used: for example, Etherscan for Ethereum, TRONSCAN for TRON, or Solscan or Solana Explorer for Solana. Open it through official network resources or your established wallet or exchange. Viewing a public transaction requires no wallet connection or signature.

Copy and check the ID yourself. A sender's Completed screenshot supports the case but does not verify the payment.

If the explorer cannot find it

Wrong network or ID: confirm the chain and that you copied the blockchain transaction ID.
Not broadcast or indexed: the withdrawal may still be processing, or the explorer may be behind. Try another reputable explorer for that network.
Replaced transaction: a speed-up or replacement may have produced a new hash. Ask for the current one.
Internal platform transfer: payments between the service's customers may use its private account system. Ask it to trace the internal reference.

For a Lightning payment, use the invoice and payment record with the provider's support process. A Bitcoin mainnet explorer will not show that individual payment.

Start with the sender or sending service if it cannot provide a verifiable payment record.

2. Check what the transaction actually did

A transaction can appear in a block even if its operation Failed or Reverted. When an entire Ethereum-compatible transaction reverts, its asset movements are undone, but a network fee can still apply. Ask the sending exchange to reconcile any balance deducted for a failed withdrawal.

For a successful transaction, find the specific payment. One transaction may contain several transfers, a swap, an approval, or a smart-wallet operation.

USDT and other tokens on Ethereum-compatible networks

Under Token Transfers, Tokens Transferred, or similar, match the token, amount, and recipient. An illustrative 500 USDT payment on Ethereum can show:

Status: Success.
Main To field: the USDT contract or another contract being called.
Value: 0 ETH.
Token transfer: 500 USDT to your deposit address.

Ethereum's transaction documentation explains that the main value field measures ETH sent with the call. Token amounts and recipients are recorded separately. 0 ETH does not mean 0 USDT, and the main To field is not always the token recipient.

Approval, zero-value transfers, and inner failures

An Approve or Allowance action grants permission to spend tokens. The ERC-20 standard separates approval from transfer and permits zero-value transfer records. Neither an approval alone nor a zero-amount entry proves your payment arrived.

Find the payment after any approval step. Apps can combine actions, so inspect transfers rather than relying on the method name.

Ethereum's EIP-658 defines success at the outer transaction level. A contract can handle an inner failure without failing the whole transaction. Safe documents a wallet attempting to send 1,000 DAI while holding about 2 DAI: Etherscan showed outer success, but the DAI payment failed.

For smart wallets, batch payments, or contract payouts, check the service's activity details and ask for proof of the actual asset movement.

USDT on TRON

Check execution success and the TRC-20 transfer's amount and recipient. TRON's developer documentation separates broadcasting, block inclusion, execution, stronger confirmation, and app history. A firmly recorded transaction can still contain failed contract execution.

Bitcoin

Find the output paying your exact address and use its amount. Other outputs may pay other customers or return change to the sender; exchanges can batch withdrawals. The total or largest output is not necessarily yours. Note your output number for support.

Solana tokens

A transfer may show a token account instead of your main wallet address. Solana's documentation explains that it records a token's mint address and wallet owner. Check both. The token-account owner differs from the program owner, which may appear as the Token Program.

A matching owner does not guarantee that an exchange supports that deposit method.

3. Compare the recipient with your deposit instructions

Open the receiving platform, select the asset and network, and compare its instructions with the actual transfer. Check the full address. Address-poisoning attacks put lookalike addresses in transaction history; matching only the first and last characters is insufficient.

Use your account's deposit instructions, not recent activity. Keep the instructions or screenshot used when sending, since today's deposit screen may differ.

Exchange labels and shared wallets

An explorer's exchange label may identify an operational wallet, not an address that credits your account. Kraken documents uncredited payments sent to its hot wallets after customers copied addresses from explorers.

Refunds have the same risk: an exchange withdrawal may come from a shared wallet, so its sending address may not be the customer's deposit address.

Older addresses

Kraken documents circumstances where deposit addresses expire. Coinbase Exchange says its generated addresses remain associated with the account and can generally be reused. A changed deposit screen alone does not prove an old address is invalid.

Check saved address history, migration notices, and guidance for the asset and network. Address reuse does not guarantee continued support for a discontinued token or network.

If the recipient is unrelated to your account, contact the destination's operator, if identifiable, or the sender. Deposit troubleshooting cannot redirect the payment. Stop using saved instructions if you suspect address substitution.

4. Match the network and exact token

Selecting USDT is not enough: both platforms must support the same network and token. Read the full network name. ERC-20 is a token standard used on multiple compatible networks, although exchanges often use it as shorthand for Ethereum.

The same address can exist on different networks

A normal private-key wallet can use the same 0x address on several Ethereum-compatible networks, but their balances remain separate. A sender choosing BNB Smart Chain for an Ethereum deposit can therefore use the correct address on the wrong chain.

More confirmations or changing an app's network selector will not move those tokens to Ethereum. If an exchange controls the address, ask about recovery for that exact asset and network. Address similarity does not prove access or recovery support. A smart-wallet contract may not exist or behave identically on another chain.

Verify the contract or mint

Names, symbols, and logos can be copied. Match the network plus token contract address, or mint address on Solana, against the receiving platform and issuer's official information. Tether publishes network-specific identifiers in its integration guidelines; an app's dollar valuation does not establish token identity.

The token contract identifies its software. It is not your deposit address. Do not send funds there to fix a missing deposit.

Native, bridged, and wrapped versions

A bridge can create a version of an asset on another network. Its contract may differ from the issuer's own version. Platforms may accept both, one, or neither. Labels such as USDC or USDC.e help, but the contract or mint is the stronger identifier.

Circle's integration documentation warns Circle Mint users against sending bridged USDC where only its supported assets and networks are accepted. That policy does not apply automatically to every exchange.

Waiting or importing a counterfeit token cannot make it genuine. Recovery of a genuine but unsupported token depends on the receiving platform's access and policy.

5. Check confirmations and finality

Compare the explorer's confirmation count or finality status with the receiving platform's current requirement for that asset and network. Thresholds vary and can change. For example, one confirmation is insufficient if the platform requires twelve; these figures are illustrative.

More blocks generally increase confidence that a payment will remain in the accepted chain: recent blocks can be replaced during a reorganization. Networks also use different stages: Solana distinguishes processed, confirmed, and finalized.

Layer-2 networks and bridges

Early layer-2 inclusion may precede the settlement stage a service requires. Optimism's documentation distinguishes early inclusion, data published to Ethereum, and finalization there.

For a bridge, verify both legs: success on the source chain may only complete the first step. Find the destination payment and match its token and recipient. Keep the official bridge status, transfer reference, and both transaction IDs when available. Contact the bridge provider if the destination payment has not happened.

The seven-day wait for certain Optimism Standard Bridge withdrawals is different from an ordinary exchange deposit on a supported layer-2 network. Do not apply it to every layer-2 transfer.

6. Check the amount that arrived

Compare the actual delivered amount with the deposit minimum. For example, requesting 10 USDT but receiving 9 after a withdrawal fee may miss a 10 USDT minimum. These amounts are illustrative.

Do not automatically subtract gas from a token payment: it is often paid separately in the network's native asset. Check the sender's fee breakdown and the transfer itself. Check the receiver's deposit screen for its minimum and any deposit or address setup fees.

A second deposit may not rescue the first. Kraken's policy says below-minimum deposits are not credited and are permanently lost; a later qualifying deposit does not make the first creditable.

Other routes may have different rules, and old advice can become outdated after system changes. Before sending more, check whether the minimum applies per transfer, whether amounts accumulate, and whether the original payment is recoverable.

7. Check the memo or destination tag

Some exchanges share one address among customers and use a memo or destination tag to assign deposits, commonly for XRP or XLM. The address can be correct while the customer reference is missing or wrong.

Check whether a reference was required, whether it was sent, and whether its value and type match. It must be in the transaction's actual memo or tag field, not a private note in the sending app.

If the platform controls the receiving address, support may be able to match the payment manually and may request proof from the sending account. Recovery is not guaranteed. A confirmed memo cannot be edited, and a second transfer cannot amend it.

8. Investigate the receiving platform

Once the payment meets the address, asset, network, amount, reference, and confirmation requirements, check the account side.

Deposit history and account location

Open deposit history, clear date filters, and check the correct account or subaccount. Bybit says deposits can go to Funding, Unified Trading, or Earn depending on settings. A missing fiat quote does not prove tokens are missing; later trades or transfers can also explain today's balance.

Status labels matter. Kraken's guide defines Credited as available for trading but not yet withdrawal, Successful as available for both, and On hold as needing manual review. Other platforms use different labels. Tell support whether the entry is absent, pending, held, or credited but unavailable.

Maintenance and processing delays

Trading can work while one network's deposits are paused. Check the official status page and deposit-screen notices. OKX documents both network-specific suspensions and delays while its blockchain infrastructure and platform synchronize.

Keep any incident reference and follow updates. If the published processing window passes without credit, contact support.

Account reviews and sender information

Crypto.com documents deposits awaiting origin information in relevant jurisdictions. Bybit documents Travel Rule verification and credit limits on some routes. Requirements depend on the customer, location, and transfer.

Complete requests through your official account. More confirmations cannot supply missing information, complete an account review, or remove a platform limit. Even without a visible request, ask support whether a review is pending and what it needs.

Unsupported transfer methods

The asset and network can be supported while the payment route is not. Contract-originated ETH may appear under Internal Transactions: actions inside a blockchain transaction, distinct from private transfers between exchange customers.

Some platforms restrict contract payouts or other methods. Ask which route they support. A warning about smart-contract deposits is not a universal ban on ERC-20 payments, which themselves use contracts.

Funds moved out of the deposit address

Exchanges may collect deposits into operational or storage wallets, a sweep, while tracking customer balances privately. Kraken's Unified EVM migration guide notes that its older API flow sometimes returned the later hot-wallet transfer ID instead of the original deposit ID.

A custodial deposit address returning to zero therefore does not by itself prove theft or failure. Preserve incoming and later transfers separately; ask support to trace the original payment and account credit. Unexplained outflows from a wallet you control yourself need a separate security investigation.

If the destination is your own wallet

Check the wallet account and network.
Verify the asset balance, incoming payment, and any later outgoing transfer on an independent explorer.
If the asset is present but hidden, use the wallet's token-display or import feature with the verified contract or mint.
Refresh or update the wallet through its official distribution channel.

MetaMask documents automatic detection and manual token display. Importing a token changes its display; it does not move, convert, or recover funds sent elsewhere.

A normal private-key account may be accessible through the same wallet on another compatible network. Follow the wallet's official instructions; this does not automatically apply to exchange addresses or smart wallets.

Receiving an ordinary token payment does not require buying gas to make the balance appear. Later transfers, bridge claims, or other blockchain actions may cost a fee. Check what action is actually requested.

Example: USDT transfer successful but not received

In this illustrative case, you request 500 USDT from Exchange A to Exchange B. A deducts a 2 USDT withdrawal fee and marks the transfer complete, but B shows no deposit.

A supplies a transaction ID on TRON.
The successful transfer shows 498 USDT delivered.
The contract matches genuine TRON USDT and the token B accepts.
B's deposit instructions support TRON, and the recipient matches.
The delivered amount, any required reference, and confirmations meet B's requirements.

If all five checks pass, ask B to investigate detection, account matching, or a hold. Another 500 USDT payment would not diagnose that problem. If a check fails, follow the relevant section above.

When to wait or contact support

There is no universal number of minutes for a confirmed deposit to appear. Use the receiving platform's requirements for your route.

Wait while a correct payment is below the required confirmation or finality threshold.
Follow maintenance updates for an incident affecting your asset and network.
Contact receiving support after the required stages and normal processing window pass without credit.
Request recovery promptly for a wrong network, unsupported token, incorrect memo, or expired address. Confirmations cannot fix these.
Contact the sender or bridge provider if the destination payment cannot be verified.

If support only confirms the blockchain status, ask: Has this deposit been detected, matched to my account, and credited? Which check is incomplete? Add new evidence to the same case where possible.

Cancellation, fees, and recovery

A payment already included in the accepted chain cannot normally be canceled through the sending app. Fee replacement or acceleration applies to transactions awaiting inclusion; it cannot force exchange credit after arrival and sufficient confirmations. A return requires a separate transaction from whoever controls the funds.

Recovery may involve matching a missing memo, manually crediting an accessible unsupported deposit, or returning funds. It cannot rewrite the original transaction. Ask about eligibility, fees, timing, and a suitable return address, network, and memo before agreeing. Do not assume the original sender address is a safe return address.

No outside recovery company can guarantee that an exchange will credit its private ledger.

Send evidence safely

Open support inside the official app or website yourself. A public reply or unsolicited message does not prove the sender represents the exchange. Never disclose a recovery phrase, private key, password, API secret, or one-time login code.

Verify any recovery fee or wallet-ownership check through your signed-in account. Do not send another payment because an unsolicited message promises to release the first.

Hide unrelated balances and personal information in screenshots. Keep the relevant transaction ID, addresses, asset, network, amount, and time readable for support. Send identity documents only through the designated verification process.

Make the next transfer easier to track

Save deposit instructions, match networks, and check the amount after deducted fees. A test payment must meet the receiving minimum; wait for account credit before sending the main amount.

Coinnoti can notify you of supported blockchain activity so you can follow a transfer without repeatedly refreshing an explorer. An address alert cannot prove the exchange has credited your private balance or made funds available.

Support-ticket template: confirmed transfer, missing deposit

Use the receiving platform's official support form. Replace brackets; write unknown or not applicable where needed. Use the original incoming transaction ID even if the exchange later swept the funds.

Subject: Missing [asset] deposit on [network] | [amount delivered] | [transaction ID]

Hello, my deposit has not appeared as expected. The sender shows [status]; the blockchain shows [execution result and confirmation/finality status].

Account and transfer

Account ID/customer reference: [ID requested by the platform]
Asset and symbol: [name]; contract, mint, or other identifier: [identifier or native asset]
Network actually used: [full name]; network in your deposit instructions: [full name]
Sending wallet/platform: [name]; withdrawal reference: [reference]
Original transaction ID: [full ID]; explorer: [name and transaction URL if requested]
Actual asset sender: [address]; actual recipient: [full address]
Deposit address supplied for my account: [full address]
Required memo/tag: [value and type, or not required]; sent: [value and type, or missing]
Amount requested: [amount and asset]; deducted fee: [amount and asset]; delivered: [amount and asset]
Submitted: [date, time, zone]; first block inclusion: [explorer timestamp and zone]
Current confirmations/finality: [status], checked at [time and zone]
Your confirmation threshold and deposit minimum: [requirements]

Additional technical details, if relevant

Transfer method: [direct native-coin transfer, token transfer, smart-wallet/contract payout, bridge, or unknown]
Block number/equivalent: [value]; output number or transfer-event index: [value]
Solana token account and wallet owner, or Bitcoin input details if requested: [details]
Bridge: [name, order/message reference, source and destination networks and transaction IDs, exact status]

Account status and evidence

Deposit-history status: [no entry or exact displayed text]; account sections checked: [funding, trading, subaccount, or other]
Maintenance notice/incident: [reference or none found]
Verification/sender-information request: [exact request and completion status]
Older saved deposit instructions used: [details]; existing support case: [number, if any]
Attachments: [withdrawal record, deposit instructions, actual transfer details, and deposit-history status]

Please confirm whether the incoming payment was detected and matched to my account. If it is uncredited, identify the incomplete check, unsupported detail, or hold and the action needed.

If normal credit is unavailable, please confirm recovery or return eligibility, fees, timing, and the next step. Confirm the appropriate return address, network, and memo before returning funds to an address from the original transaction.