My Tokens Are Not Showing Up in My Wallet: How to Add a Custom Token Manually?

Troubleshooting Token Visibility Issues

1. Wallets like MetaMask or Trust Wallet do not automatically display all tokens held in your address. They rely on token lists or manual configuration to render balances correctly.

2. If a token is built on Ethereum, BNB Smart Chain, Polygon, or another EVM-compatible network, its absence usually indicates the wallet has not been instructed to monitor that specific contract address.

3. Network misconfiguration—such as being connected to Ethereum Mainnet while holding tokens on Arbitrum—will prevent any balance from appearing, even if the private keys are correct.

4. Some tokens use non-standard ERC-20 implementations or deploy proxy contracts with logic separation, causing detection failures during automatic scanning.

5. Browser extensions may block third-party token list APIs due to strict privacy settings, halting the auto-discovery process for newly deployed tokens.

Step-by-Step Manual Token Addition

1. Open your wallet interface and navigate to the “Add Token” or “Import Token” section—usually found under Assets or Settings.

2. Select “Custom Token” instead of “Token List” to bypass pre-approved entries and proceed with raw contract data entry.

3. Input the exact contract address of the token—this must match the deployment address verified on Etherscan, BscScan, or equivalent explorers.

4. Paste the correct token symbol and decimal count—common mistakes include using 18 decimals for a token that only supports 9, which distorts balance representation.

5. Confirm the addition; the wallet will query the node for the balance at that contract and update your asset list immediately if the inputs are valid.

Verifying Contract Authenticity Before Import

1. Always cross-check the token’s contract address against official project announcements, verified social media channels, or audit reports—not community Discord messages or unverified links.

2. Use blockchain explorers to confirm whether the contract has passed security audits and shows consistent transaction volume across multiple blocks.

3. Look for the “Verified” badge next to the contract source code—unverified contracts pose serious risks including minting control or withdrawal locks.

4. Check the number of holders and transfer events: legitimate tokens usually show organic growth over time rather than sudden spikes followed by stagnation.

5. Avoid contracts with self-destruct functions or owner-only mint capabilities unless explicitly documented and justified by the project’s whitepaper.

Common Network-Specific Pitfalls

1. Attempting to add an Optimism-based token while connected to Base will yield zero balance, regardless of correct contract input.

2. Some wallets require manual RPC endpoint setup before supporting newer chains like Linea or Blast—default configurations often omit them.

3. Tokens deployed on zkSync Era need special ABI handling; standard ERC-20 import flows may fail without enabling zkSync-specific features in advanced settings.

4. Gas token mismatches—for example, using ETH instead of MATIC for Polygon transactions—can stall balance refreshes even after successful import.

5. Legacy wallet versions lack support for certain chain ID formats used by emerging L2s, resulting in silent import failures with no error message.

Frequently Asked Questions

Q: Can I add a token if I only have the token name but not the contract address?A: No. The contract address is mandatory. Without it, the wallet cannot locate or interact with the token’s ledger state.

Q: Why does my manually added token show “0.000000” even though I confirmed receipt on a block explorer?A: This typically means the wallet is connected to the wrong network or the token uses a non-standard interface that requires custom ABI injection beyond basic import.

Q: Is it safe to paste a contract address from a Telegram group into my wallet?A: Never trust unsolicited contract addresses. Phishing groups routinely share malicious clones designed to drain funds upon approval or interaction.

Q: Do I need to approve the token after adding it manually?A: Approval is only required when interacting with decentralized applications—adding the token itself does not trigger any on-chain action or permission request.