Jupiter verification is missing
The token can have valid metadata and a Solscan page without the upstream recognition Phantom recommends.
Diagnose the cross-platform gap between a visible Solscan token and missing, hidden or incorrect Phantom display.
CheckMyMint prioritizes evidence and dependencies so you can avoid repeating a valid update or paying the wrong platform.
The token can have valid metadata and a Solscan page without the upstream recognition Phantom recommends.
Different names, symbols, logos or official URLs can resemble spam or impersonation patterns.
Once upstream information is corrected, Phantom may still need time to rerun its internal systems.
A token appearing correctly on Solscan but not Phantom is not contradictory: the products apply different display, reputation, and upstream-recognition rules. Solscan confirms that the mint and some metadata can be indexed, but it does not establish that Phantom's classification inputs are satisfied.
Use Solscan as one observation, not as the universal source of truth. Read the canonical metadata, check Jupiter and CoinGecko recognition, and determine whether Phantom has hidden or flagged the token. The likely fix is often upstream consistency plus automatic reevaluation, not a request to copy Solscan's display.
Compare the full mint address in Solscan and Phantom. New tokens with reused names or symbols can lead users to inspect different assets without noticing.
Read the mint's Metaplex or Token-2022 fields and test the JSON and image. Confirm that Solscan is not merely displaying an older cached logo while the canonical source is broken.
Compare the name, symbol, logo, website, and socials in the upstream sources Phantom recommends for recognition. Note missing listings and every conflicting field.
Determine whether the token is hidden or flagged as spam using Phantom's official support guidance. Classification requires a different response from an ordinary stale image.
Correct the relevant source through its official workflow and keep identity fields consistent. Allow Phantom's automatic classification process to rerun rather than repeatedly changing healthy on-chain metadata.
Each platform uses its own data and policy signals, so one correct explorer page cannot certify another wallet's classification.
Name and symbol matches are insufficient; troubleshooting and upstream updates must use the exact mint address.
A spam or hidden classification can make the asset absent even when the technical logo URL is valid.
Solscan displays the mint and logo, but Phantom hides the token; Jupiter has incomplete metadata and CoinGecko has no matching asset.
Solscan indexing is healthy, while Phantom lacks consistent upstream recognition and may be applying its classification rules.
Complete the relevant Jupiter metadata or verification workflow, ensure all fields match the canonical mint, review Phantom's hidden-token guidance, and wait for automatic reevaluation.
No. The platforms apply separate systems and Phantom references upstream recognition such as Jupiter or CoinGecko.
Phantom does not describe a universal direct logo submission route. It recommends accurate, consistent metadata and verification through recognized upstream platforms.
Yes. Solscan and Phantom apply different source, recognition and safety systems, so visibility in one interface does not guarantee identical treatment in the other.
Phantom does not provide a universal completion time for every token state. Correct upstream evidence first, then monitor rather than repeatedly changing already-valid metadata.
Third-party workflows change. CheckMyMint links to official documentation and displays when the platform rules were reviewed.