Overview — why BNB transfers fail
If you cant send BNB from Crypto.com to MetaMask or you’re trying to send BNB to MetaMask from Trust Wallet and the tokens never show up, the problem is almost always a network mismatch or a settings issue. I’ve run into this myself when I accidentally chose the wrong network on a withdrawal screen; the result was a pending, non‑appearing balance and a support ticket.
Short version: MetaMask is an EVM-compatible, non-custodial software wallet by design. BNB exists on multiple networks (for example, the BNB Beacon Chain and BNB Smart Chain / BEP20). Sending tokens on the wrong network is like trying to mail a letter to the wrong country — the address format might not be understood.
And yes, many people make the same mistake.
Quick checklist (fast fixes)
- Confirm the network you selected at the sending app (BEP20 / BSC vs BEP2).
- Make sure MetaMask is configured for BNB Smart Chain (BEP20) with the correct Chain ID and RPC.
- Verify the destination address (copy/paste, then confirm first 6 and last 4 chars).
- Keep a small BNB balance in MetaMask to pay gas fees.
- Check the transaction hash on the appropriate block explorer.
If those checks don’t help, read the deeper troubleshooting sections below (and don’t panic). But don’t skip contacting the sending platform’s support if funds look lost.
Common causes and fixes
Wrong token standard: BEP2 vs BEP20
Problem: The sender chose BEP2 (BNB Beacon Chain) while MetaMask is expecting BEP20 (BSC) tokens.
Why it breaks: BEP2 addresses and BEP20 (EVM) addresses are incompatible. BEP2 uses a different address format and usually a memo/tag. Sending BEP2 to a 0x... address often fails or results in loss unless the sending platform can recover funds.
Fix: Cancel the withdrawal if possible. If transaction is already broadcasted, contact the sending platform immediately with tx hash. If you control the receiving private keys and the chain supports recovery, a specialist can sometimes help — but recovery is not guaranteed.
Missing or misconfigured BNB Smart Chain (BEP20) network in MetaMask
Problem: MetaMask will not show BEP20 BNB until you add BNB Smart Chain as a custom network.
Fix: Add a custom RPC for BNB Smart Chain to MetaMask (Network Name: BNB Smart Chain; Chain ID: 56; RPC URL: https://bsc-dataseed.binance.org/; Currency: BNB; Explorer: https://bscscan.com) — then switch to that network and your BEP20 BNB balance should appear (if the tx succeeded). See networks and multi-chain for more.
Memo / Tag problems
Problem: Some platforms require a memo/tag on BEP2 withdrawals. If you forget it, funds can land in a custodial pool and require support to reclaim.
Fix: Always check the withdrawal page for a memo/tag requirement. If you forgot the memo, open a support ticket with the sending service and provide your tx hash.
Insufficient BNB for gas or pending transaction conflicts
Problem: You received tokens but can’t send them because there’s no BNB to pay gas. Or a stuck transaction uses your nonce and blocks future sends.
Fix: Move a small amount of BNB to the same MetaMask account (on BSC) to cover gas. For stuck tx, try MetaMask’s "Speed up" or "Cancel" features, or reset your account nonce in settings (see transactions and gas).
Bridge or network mismatches
Problem: A bridge was used but the target network wasn’t selected correctly, or the bridge is delayed.
Fix: Check bridge status and the correct target chain. If you used a bridge, see our bridging overview for common pitfalls.
Step-by-step: send BNB to MetaMask
Send BNB from Crypto.com to MetaMask (step-by-step)
- Open Crypto.com, go to Withdraw > Crypto > BNB.
- Choose the network: select BEP20 (BSC) — do not pick BEP2 unless your receiving wallet supports BEP2.
- Paste your MetaMask address (double-check). Confirm first 6 and last 4 characters.
- Enter amount and confirm fees. Submit withdrawal and copy the transaction hash.
- Monitor on BSC explorer (e.g. bscscan) to confirm completion.
If the transaction never appears, open support and include the tx hash and screenshots. See transfer-from-crypto-com-to-metamask for a deeper walkthrough.
Send BNB to MetaMask from Trust Wallet (step-by-step)
- Open Trust Wallet and choose your BNB asset.
- Tap Send, paste your MetaMask BEP20 address.
- Select the network option (ensure BEP20/BSC), then confirm.
- Wait for on-chain confirmations. If you prefer, you can connect Trust Wallet to MetaMask via WalletConnect for direct interaction.
See transfer-from-trust-wallet-to-metamask for screenshots and tips.
Comparison: quick view of common source differences
| Source wallet / exchange |
Common network options shown |
Most common user error |
Quick fix |
| Crypto.com |
BEP2, BEP20, ERC20 (sometimes) |
Selecting BEP2 when using MetaMask |
Choose BEP20 and re-send; contact support if BEP2 was used |
| Trust Wallet |
BEP2, BEP20 (BSC), BEP20 tokens |
Choosing wrong network or wrong token contract |
Use WalletConnect or select BEP20; add token contract in MetaMask |
(Keep a screenshot of the withdrawal screen before confirming — it helps support.)
![Placeholder image: MetaMask network selector screenshot]
Advanced troubleshooting and recovery options
- If you sent BEP2 to a 0x... address: contact the sending platform immediately. Recovery often requires custodial intervention.
- If tx shows as failed: check MetaMask logs and explorer details. Replace the tx by resubmitting with higher gas (same nonce).
- If tokens don’t appear but explorer shows success: add the token as a custom token (see add-custom-token).
But don't panic yet. Recovery is sometimes possible, but requires patience and support tickets.
Security, backups, and best practices
- Never paste your seed phrase anywhere. Keep it offline (paper or hardware).
- Verify addresses carefully. Use address book features or QR codes.
- Keep a small BNB balance for gas after any transfer — otherwise you can’t interact with DeFi.
- Revoke unusual token approvals after big swaps (revoke-approvals). I once left an approval open and paid for it; learn from my mistake.
Who MetaMask is best for — and who should look elsewhere
Who it fits: Users who want a flexible EVM-compatible software wallet for DeFi, L2s, and swaps. MetaMask is hands-on and connects widely to dApps.
Who should look elsewhere: If you need cold storage-level safety for large sums, consider a hardware wallet paired with MetaMask or a pure hardware workflow (see ledger-and-hardware). If you prefer fully custodial simplicity for fiat conversions, an exchange may suit you better.
FAQ
Q: Is it safe to keep BNB in a hot wallet like MetaMask?
A: Hot wallets trade security for convenience. For small-to-medium balances used in DeFi, they’re practical. For large holdings, consider hardware-backed self-custody. See security-backup.
Q: What if I sent BEP2 BNB to my MetaMask address by mistake?
A: Contact the sending platform immediately with tx hash. Recovery depends on the sender’s policies and may not be possible.
Q: Why is my BEP20 token not visible after transfer?
A: You may need to add it as a custom token (contract address). See add-custom-token.
Q: How do I revoke token approvals that I made earlier?
A: Use the revoke tool guide at revoke-approvals. Regularly check approvals after using DEXs.
Conclusion & next steps
If you cant send bnb from Crypto.com to MetaMask or have trouble when you send bnb to MetaMask from Trust Wallet, start by confirming the network (BEP20 for MetaMask) and that MetaMask is configured for BNB Smart Chain. Follow the step-by-step checks above and keep transaction hashes and screenshots handy when you contact support.
For more hands-on walkthroughs, check the related guides: transfer-from-crypto-com-to-metamask, transfer-from-trust-wallet-to-metamask, and network-transfer-issues.
If you want a guided setup for MetaMask on mobile vs desktop, see metamask-mobile-guide and metamask-extension-troubleshooting. Safe transfers — and always double-check the network before you hit send.
