How to fix Phantom wallet not showing my SPL token after receiving it?

Troubleshooting SPL Token Visibility in Phantom Wallet

1. Verify the token’s contract address matches the one registered on Solana Explorer. Phantom only displays tokens with verified metadata hosted on the official token-list repository.

2. Confirm the transaction was confirmed on-chain by checking the signature hash on solscan.io or explorer.solana.com. Unconfirmed or failed transactions do not trigger token display logic.

3. Ensure the wallet is connected to the correct network—Phantom must be set to mainnet-beta, not devnet or testnet, as SPL tokens deployed on alternate clusters remain invisible in production views.

4. Manually add the token using its mint address via Phantom’s “Add Token” > “Custom Token” flow. Some newly launched SPL tokens lack community-maintained entries in the default token list.

5. Clear Phantom’s local cache by disconnecting all dApps, closing the extension, and reopening it. Persistent UI rendering bugs sometimes freeze token balance updates without a full reload.

Token Metadata Requirements for Automatic Detection

1. The SPL token must have a valid token-list.json entry submitted to the solana-labs/token-list GitHub repository.

2. Metadata fields including name, symbol, logoURI, and decimals must be present and correctly formatted in the JSON object.

3. The logoURI must point to a publicly accessible HTTPS endpoint returning a valid PNG or SVG file under 1MB in size.

4. The mint address listed in the token list must exactly match the on-chain program-derived address—not a wrapper or proxy contract.

5. Phantom pulls this list during wallet initialization; changes require a full extension restart or browser session refresh to take effect.

Common Transaction-Level Misconfigurations

1. The sender used a wrapped version of the token (e.g., Wormhole-wrapped) instead of the native SPL mint, causing Phantom to treat it as a distinct asset with no auto-discovery support.

2. The recipient account was created with an older version of the SPL token program, leading to incompatible account data layouts that prevent balance parsing.

3. The transfer instruction included a memo or custom compute budget that triggered silent failure in post-processing hooks, resulting in zero balance change despite transaction success.

4. The token has a freeze authority enabled and the account was frozen prior to receipt, locking visibility until thawed through an authorized signer.

5. The transaction was bundled with other instructions across multiple programs, causing Phantom’s internal parser to skip SPL balance reconciliation due to incomplete instruction tracing.

Browser Extension vs. Mobile App Behavior Differences

1. Phantom Mobile does not auto-sync token lists from the same source as the browser extension—it relies on a separate, infrequently updated internal cache.

2. Browser extension versions prior to v6.6.0 ignore tokens with decimals greater than 9, truncating balances to zero and omitting them from the asset list.

3. Mobile users must manually trigger “Refresh Balances” from the wallet settings menu, while desktop users rely on automatic polling every 30 seconds.

4. iOS Safari Web Clip installations bypass Phantom’s background service workers, disabling real-time balance listeners entirely.

5. Chrome-based browsers allow deeper integration with Solana’s RPC layer, enabling richer token detection compared to WebView-based mobile environments.

Frequently Asked Questions

Q: Why does my SPL token appear in Solflare but not in Phantom?A: Solflare maintains its own independent token registry and supports manual override of missing metadata. Phantom strictly enforces the official Solana token list and rejects entries with malformed URIs or mismatched checksums.

Q: Can I see unverified SPL tokens using Phantom’s developer mode?A: No. Phantom does not expose a developer toggle for unlisted tokens. Its UI layer filters assets at render time based solely on presence in the canonical list.

Q: Does Phantom support tokens deployed via Token-2022 extensions?A: Phantom currently ignores accounts initialized with Token-2022 features such as transfer fees or confidential transfers. Only legacy Token-2022-compatible mints without extensions are rendered.

Q: Why does the token show 0 balance even after successful confirmation?A: Phantom calculates balance by reading the associated token account’s amount field. If the account was initialized with zero lamports or lacks proper ownership delegation, the parser returns null instead of zero, suppressing display.