Why Does a BSC Transaction Show Success but My Tokens Never Arrive?

25 September 2026

A transaction that shows as successful on BscScan but leaves your wallet empty of the expected tokens is almost always a problem with how the token transfer was executed, not a failure of the BNB Chain network itself. The transaction confirmed - the gas was paid, the block was written - but the instructions inside that transaction did not deliver tokens to your address. The most common causes are sending to a contract address instead of a wallet, failing to add the token contract to your wallet, or falling victim to a phishing dApp that drains funds during an approval step.

You Sent Tokens to a Contract Address

This is the single most frequent reason tokens "disappear" after a successful transaction. On BNB Chain, as on Ethereum, tokens are held by smart contracts. When you send BEP-20 tokens to a contract address rather than a personal wallet address, the contract receives them. Unless that contract has a function to forward or refund tokens, they are locked there permanently.

• The transaction will show as successful because the transfer function executed correctly.
• The tokens will appear on BscScan under the contract's token holdings, not your wallet.
• There is no central support team or undo button. No one can reverse it.

Check the recipient address on BscScan before you send. If the address has associated contract code (visible under the "Contract" tab), you are sending to a contract. Send only to addresses that are clearly wallet addresses - typically starting with 0x and having no associated contract code.

You Have Not Added the Token to Your Wallet

Your wallet displays only the tokens you have explicitly added. If you received a BEP-20 token but your wallet does not show it, the tokens may still be at your address. You just cannot see them.

1. Copy your wallet address.
2. Open BscScan and paste your address into the search bar.
3. Look at the "Token Holdings" or "BEP-20 Token Transfers" section.
4. If the token appears there, you own it.
5. Add the token contract address to your wallet manually. For MetaMask, go to "Import tokens" and paste the contract address. For Trust Wallet, use the "Add Custom Token" option.

Do not trust a token list that claims to show all tokens automatically. Wallets rely on token registries, and many legitimate tokens are not registered.

You approved a malicious contract

A successful transaction can also mean you approved a smart contract to spend your tokens, and that contract then transferred them away. This happens in phishing dApps or fake airdrop sites.

• The transaction you signed was an "approve" call, not a transfer.
• After approval, the malicious contract moved your tokens in a separate transaction.
• You may see a transaction from your address to the contract with method approve and a high allowance.

The "success" status means the approval executed. The tokens then left in a transaction you did not personally initiate but authorised.

Never connect your wallet to a site you have not verified independently. If a site asks you to "approve" a token before you have done anything else, close it. Check the contract address on BscScan before approving. If the contract has no source code verified, or if it was created days ago, treat it as suspicious.

You used a cross-chain bridge incorrectly

Bridges between BNB Chain and other networks (Ethereum, Polygon, etc.) often require two steps: send tokens to the bridge contract on the source chain, then claim them on the destination chain.

• The first transaction (sending to the bridge) will show as successful.
• If you do not complete the second step, the tokens remain in the bridge contract.
• Some bridges require a small amount of the destination chain's native token (BNB for BSC, ETH for Ethereum) to pay gas for the claim transaction.

Check the bridge's interface for a pending or unclaimed transaction. If you sent tokens but never claimed them, the bridge's history page or your wallet's transaction log on the destination chain will show nothing. Complete the claim step, and ensure you have enough native token to cover gas.

The Token Has a Transfer Fee or Burn Mechanism

Some BEP-20 tokens include a fee on transfer, a burn, or a reflection mechanism. When you send such a token, the recipient receives less than the amount sent.

• The transaction shows success because the transfer function executed.
• The recipient's wallet shows a lower balance than expected.
• This is not an error. It is the token's intended behaviour.

Check the token contract on BscScan. Look for functions like _transfer, _taxFee, or _burn. Read the token's documentation or source code. If the token takes a percentage on every transfer, you cannot "fix" it. That is how the token works.

The Token Contract Has a Blacklist or Pause Function

Some token contracts allow the owner to pause transfers or blacklist addresses. If your address is blacklisted, or if transfers are paused globally, your transaction will still execute and show as successful, but the tokens will not move.

• The transaction will show a successful status but the token transfer event may be missing or show zero value.
• Check the token contract's paused status and whether your address is in a blacklist mapping.

You cannot bypass this. If the contract owner blacklisted you, or paused transfers, your tokens are stuck until the owner unpauses or unblacklists you. This is a feature of centralised token designs, common in scam tokens.

You Need to Check the Transaction Logs

When a transaction shows success but tokens do not arrive, the transaction receipt's event logs tell the real story. On BscScan, open the transaction hash and scroll to "Logs". Look for a Transfer event (topic 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef).

• If there is no Transfer event, the token transfer did not happen.
• If the Transfer event shows the to address is a contract, you sent to a contract.
• If the Transfer event shows an amount of zero, the token fee consumed everything.

Reading logs is the definitive way to understand what a transaction actually did. The "success" status only means the transaction did not revert. It does not mean the intended outcome occurred.

Back to bnb chain