Skip to main content

​
For Users & Traders

Common questions about what token verification means and how it affects your experience.
The green checkmark next to a token’s ticker indicates that it is the canonical version of that token. It helps traders identify the correct token, especially on Solana where anyone can mint a token with any name.The checkmark is visible in Jupiter Wallet and Jupiter Mobile, on Jupiter Spot (token pages and search bar), and on partner platforms that integrate Jupiter’s verified token list, such as Phantom.For more details, see Token Verification.
Look for the green Verified badge next to the ticker: on jup.ag token pages and in the global search results (which can be filtered to verified tokens), in Jupiter Wallet, and in Jupiter Mobile. A token that is not verified shows a Not Verified entry in the JupShield warnings chip next to its ticker on the token page, reminding you to check the mint address before trading. Whether or not a token is verified, always compare its mint address with the one published on the project’s official channels: the badge identifies the canonical token for a ticker, it does not vouch for the project. See Token Page.
No. Verification confirms that a token is the canonical version of a given ticker. It is not an endorsement of the project, the team, or the token’s quality or safety.
Always do your own research before making any decisions. Verified status can be removed.
Yes. Unverified tokens are available on Jupiter as long as their pools have sufficient liquidity on the DEXes Jupiter integrates. Tokens are prioritized in search by text similarity, volume, and liquidity.
Yes. Jupiter periodically reviews verified tokens and can remove the label under strict conditions: the token has no remaining liquidity, has stopped trading entirely, has migrated to a new contract address, or has a ticker conflict with another verified token.For more details, see After Verification.
Yes. Anyone can like a pending submission from its public page on the Submissions page. Likes from wallets identified as Smart by Jupiter feed into a social trust score, which moves submissions up the Standard Review queue.For more details, see Standard Review.
The verified token list is served through the Jupiter Tokens API, which is what partner wallets, DEXes, and screeners integrate. See the Tokens API documentation on the developer portal.

​
For Project Teams & Token Creators

Questions about the verification process, metadata updates, and how to submit or manage your token’s information on Jupiter.
Anyone can submit a verification request for any token, including community members. It is not limited to project teams or token creators. You can optionally connect the project’s X account during the application.Submit your application at verified.jup.ag/tokens/submit.
Both lead to the same outcome: the token is either verified or not. Standard Review is free with no guaranteed timeline; submissions are prioritized by age, trading volume, and Smart Likes. Express Review costs 1,000 JUP and guarantees a first review within 24-48 hours, with up to 2 further reviews at 24-48 hour intervals. The fee buys speed, not verification.See the comparison table under Review Methods.
Standard Review has no guaranteed timeline and depends on the current backlog. Express Review guarantees a first review within 24-48 hours of submission, then up to 2 more reviews at 24-48 hour intervals if the token is not approved. See Review Methods.
1,000 JUP per submission, collected when you submit and burned by Jupiter through a wallet (not retained by the team). The fee is non-refundable whatever the outcome; a refund applies only if the guaranteed first-review window is missed.
Express Review applicants receive a general reason for rejection (e.g., Ticker Conflict, Below Thresholds).There is no formal waiting period, but reapplying without meaningful progress on the flagged metrics will lead to the same result. Reapplying via Express requires a new 1,000 JUP fee. You can also upgrade an existing Standard application to Express at any time.
Before resubmitting, contact support at support.jup.ag to understand the reason for rejection and what to improve.
For more details, see Rejection and Reapplication.
Each submission is automatically scanned by JupShield, which surfaces warnings such as Not Sellable, Not Verified, Low Liquidity, Low Organic Activity, or New Listing. They are visible on the public submission page and help reviewers and the community assess the token’s status at a glance.JupShield warnings do not automatically lead to a rejection, but they are part of the holistic review and can affect the final decision.
These warnings are set by third-party security providers (such as Blockaid) that wallets like Phantom use to screen tokens. Jupiter does not set or control them. Those providers run their own review process, which can draw on a range of sources — including Jupiter’s verified-token list — so verifying your token on Jupiter may help, but it does not guarantee the warning is removed. To dispute a specific warning, request a review directly with the provider that issued it.
Anyone can submit a metadata update request, including community members. This is useful for community-owned tokens, projects that have lost onchain metadata access, or when new social channels need to be added.Each submission requires a 1,000 JUP fee, collected at submission and burned by Jupiter via .
If a previous request was rejected due to a misunderstanding or missing proof, contact support at support.jup.ag before resubmitting. The metadata team can assist without requiring a new payment in those cases.
To submit, open the token’s page on the verification portal and select Update in the Token Data card. For full details, see Token Metadata Updates.
You can update: logo (PFP), name, symbol (ticker), description, socials (website, X account, X community link, Telegram, Discord, Instagram, TikTok, Linktree), and circulating supply.For the full process, see What Can Be Updated.
For security reasons, Jupiter does not automatically pull metadata changes from onchain sources after a token has been verified. All changes go through a manual review process to ensure legitimacy.If you want Jupiter to reflect updated onchain metadata, submit a request from Update on the token’s page, like any other metadata update.