Discord Bot Verification (2025): Requirements, Checklist, and Fast-Track Tips
If your bot is approaching 100 servers, verification becomes essential. This guide consolidates the current (2025) rules from official resources and gives you a concise, practical checklist to pass on the first try - plus tips to speed things up.
Table of Contents
What Verification Is and When It's Required
Mandatory at 100 servers. Unverified bots cannot join more than 100 servers. You can usually apply early around 75 servers so growth doesn't stall while you wait.
Verification confirms a real, accountable developer is behind the bot (ID check via Discord's provider) and that your bot follows developer policies.
Some features - like Privileged Gateway Intents (e.g., Server Members, Presence, Message Content) - require additional approval for large bots.
Requirements (2025)
Server Threshold
Mandatory at 100 servers. You can usually apply early around 75 servers from the banner in the Developer Portal.
Identity & Team
- Verification is completed by the Developer Team owner in the Developer Portal.
- Government ID is required via Discord's provider (e.g., Stripe Identity).
- If you're under 16, verification must be done by a parent/guardian or co-developer who becomes the team owner and completes ID verification.
Policy Compliance
- Follow the Developer Policy and Developer ToS.
- Have public Privacy Policy and ToS URLs covering your bot's data handling and user terms. You can use the public Privacy and Terms tabs offered by Rank.top on your bot's page.
- Provide a working public support server invite or contact email for users to reach you.
Step-by-Step Checklist
- Move your application to a Developer Team and ensure the correct person is team owner.
- In the Developer Portal → Your Bot, open the verification banner and start the application.
- Prepare a clear government ID for the team owner (no blur or glare; names must match the account/portal form).
- Add Privacy Policy and ToS URLs to your bot's site or documentation; describe what you collect, why, and retention.
- Request only the intents you truly need and justify each with concrete features and data minimization.
- Ensure stability: no crash loops, sensible rate limits, and a healthy reconnect strategy.
- Provide a support server invite or working contact email in your application. This must also be publicly accessible for users to reach you.
- Submit and monitor your email (and the portal) for updates or requests for clarification.
Privileged Gateway Intents
For verified bots, some Gateway intents need explicit approval. Review the official docs for details and keep your justifications precise and minimal.
Server Members
- Required for member-join flows, role sync, per-user features.
- Explain data retention and minimize storage.
Presence
- Only request if you truly react to online/offline/idle.
- Prefer aggregate behavior over storing per-user timelines.
Message Content
- Required for text parsing beyond command prefixes/mentions.
- Public Privacy Policy URL and clear, narrow use-cases help.
Timelines, Rejections, Re-submissions
Typical timeline: Many applications complete in a few business days, but allow extra time during peak periods or if you request privileged intents.
Common delays: missing details, unjustified intents, or mismatched names.
If rejected, you'll receive guidance on what to fix. Address feedback thoroughly, then re-submit with clearer justifications and working links.
Grow Faster After Verification
Verified and ready to scale? List your bot on Rank.top and reach engaged Discord users right away.
Official Resources
Links may change over time; always cross-check in the Developer Portal and official policy pages.