Why token listings get rejected
A "not approved" decision usually isn't personal or mysterious — it almost always traces back to one of a handful of common, fixable issues. Here's what they are.
The most common reasons
Missing or incomplete information
An application with gaps — no whitepaper, unclear tokenomics, no way to reach the team — is hard for an exchange to say yes to, regardless of the project itself.
No security audit
For anything with custom contract logic, exchanges increasingly treat a third-party audit as close to a baseline requirement, not a nice-to-have.
Unclear or risky tokenomics
Heavily concentrated holdings, no vesting on team allocation, or an unclear supply schedule are common red flags exchanges specifically screen for.
Low real activity
Some exchanges weigh existing trading volume, holder count, or community size as a signal of genuine demand — a token with very little activity elsewhere can be a harder sell internally for their team.
Regulatory or jurisdictional concerns
Depending on where an exchange operates, certain token structures or the project team's jurisdiction can trigger a decline regardless of how strong the project otherwise is — this one's often outside your control entirely.
Not a fit for that specific exchange
Every exchange has its own focus — some lean toward specific chains, sectors, or project stages. A decline can simply mean it wasn't the right match, not that anything was wrong.
A decline isn't final
Once an application is resolved — approved or not approved — you're free to submit again for that same token and exchange. If you know why it wasn't approved, that's the moment to fix it before reapplying. See our listing preparation guide for what to have ready, and our FAQ for the resubmission rules.