Binance verification rejected? Read the reason first, then fix your details, re-submit, or appeal

A rejection looks scarier than it is. Eight times out of ten it's something small — a blurry photo, a name that doesn't match your ID, an address proof that's too old, a face scan shot into the light. The system bounces those automatically, and none of it says anything about you or your account. What actually gets people into trouble is what they do next: re-submitting over and over, grabbing at "we'll verify it for you" offers, even thinking about buying a ready-made account. Every one of those turns a simple problem into a messy one.

This walks through it in the order things really happen: what a rejection means, why it happened, then how to fix it and re-submit, and only at the end, what to do if it still won't pass — how to appeal and hand the conversation to a human. The specific rules, timelines, and accepted documents mentioned here all change, so go by whatever Binance's own pages and support tell you at the moment you're doing this. Don't treat any number here as a hard rule.

What a rejection actually means

Let's clear up the thing you're most worried about first: a rejected verification usually does not mean a ban. Almost always it just means "this submission didn't pass." Your account is still there, you can log in and look around as normal, and what's affected are mainly the features that need verification to unlock — deposits, trading, withdrawals — along with the limits tied to them.

After a rejection, Binance normally puts your verification back into a state where you can submit again — so most of the time you can edit your details and have another go. That's the good news: a rejection is a reversible in-between state, not a dead end.

A few situations are worth telling apart:

• Rejected on the documents (unclear ID, mismatched info, an address proof that doesn't qualify) — the most common kind, and fixing the right thing usually gets you through on the re-submit;
• Face / liveness check didn't pass — often just the setting or how it was done. New lighting or a different device on the retry usually sorts it, and it doesn't always count as a "formal" rejection;
• Temporarily limited after repeated failures — too many attempts in a short window, and the system may ask you to wait a while or go through a manual review. Don't keep tapping retry here.

Step one: work out why it was rejected

Of everything you can do to fix this, reading the rejection reason is the step that pays off most. When Binance bounces a submission it usually attaches a short system message — something like "ID details not clear," "name doesn't match ID," or "document has expired." That line is the key. Fixing what it points to beats ten rounds of guessing.

If the message is vague, or you're not sure which case you fall into, run down these common causes one by one:

• ID photo doesn't qualify: glare, blur, a cut-off corner, a finger over the edge, too dark or too bright. The usual ask is all four corners in frame, text readable, no glare;
• Details don't match the ID: name spelling, date of birth, document number — one character or even one extra space off can get it bounced;
• Wrong document type or country: you picked passport but uploaded an ID card, or your country of residence doesn't line up with the country that issued the document;
• Document expired or close to it: it has to be valid, and one that's about to expire is sometimes rejected too;
• Address proof falls short: the name on it doesn't match, it was issued too long ago (the common ask is something recent), or the document type isn't accepted;
• Face / liveness didn't pass: backlight, a hat or mask, the movement not done properly, or the connection dropping;
• The same ID is already on another account: one ID across several accounts trips risk controls, and this one needs a manual check.

Match the system message against that list and most people can pin down which category they're in. For document and detail issues, run through the requirements in our complete guide to Binance identity verification (KYC); if you're stuck on the face scan, every reason face / liveness verification keeps failing, and how to fix each goes into the most detail; and if your address proof got bounced, how to enter address proof, which documents count, and what to do when it's rejected takes that one apart.

If you'd rather not go line by line, our face-fail self-diagnosis tool narrows down the likely cause from the symptoms, so you're not staring at a long list.

How to fix your details and re-submit

Once you know the cause, the fix is pretty direct. It comes down to one thing: fix the one item the rejection points at — don't redo everything from scratch.

• ID unclear: shoot it again. Natural light, a dark background, the document flat, all four corners in frame, text sharp. Skip the direct flash — it tends to cause glare. Use the real document; don't photograph a screen or a photocopy;
• Details don't match: check character by character. Spell the name exactly as it appears on the ID (including case, spaces, and name order), and line up the date of birth and document number;
• Wrong type / country: go back to the selection step and pick again, making sure document type, issuing country, and country of residence all agree with each other;
• Document expired: there's no way around it — use a different one that's still valid;
• Address proof bounced: swap in a document in your own name, recent enough, of a supported type, and upload that.

Once you've fixed it, follow the on-screen steps to submit again — most rejected states let you go straight back in. Before you send, be your own reviewer for a minute: zoom in on the photo to check the corners, and put your entered details side by side with the ID. That keeps you from getting bounced a second time over a different small thing.

After a rejection, correct the material identified on the official page and submit again. Whether a promotion, fee treatment, or other account benefit remains available is outside this article's evidence; use your account page or official support.

Still rejected? How to appeal and reach a human agent

If you're sure your details are correct and you fixed the right thing, but the submission still gets rejected — or the system keeps bouncing it without a clear reason — that's when an appeal is the move. An appeal means one thing: get a person involved to look at what the system couldn't figure out.

The path usually goes like this:

• Find the support chat: Binance's Help Center / support usually has a live-chat entry point. Start by describing the problem to the chatbot;
• Hand it to a human: when the bot can't solve it, follow the prompts to pick options like "agent" or "talk to support," or just type something clear like "I need a human to help with a verification appeal." Most of the time it queues you for a real person;
• Open a ticket / appeal form: in some cases you'll be asked to fill out a form or open a ticket and submit the problem along with your supporting documents.

Whether you get handed to a human smoothly, and how fast the conversation moves, depends a lot on how clearly you put your first message. Support handles a huge volume every day, so the tidier your description and the more complete your info, the more likely you are to get routed accurately and handled quickly. A good description roughly covers: which verification level you're on, the exact wording of the rejection message, what you've already changed, where you're stuck now, and what you'd like them to do.

If putting that into words is a chore, use our appeal message builder: fill in a few fields and it drafts a clear, matter-of-fact message you can copy straight over to support. It works a lot better than a rushed "I can't get verified, please help."

One more thing: stick to the official channels. Right after a rejection is exactly when scammers pounce — anyone promising an "inside track to instant verification" or a "support agent" who messages you out of the blue is almost always phishing. Binance's human agents won't add you privately, won't ask for your password or two-factor code, and definitely won't tell you to transfer money to "unfreeze" anything. Do every appeal through Binance's own in-app support, and don't trust any off-site "fast lane."

Get these ready before you appeal

The worst thing you can do in an appeal is go hunting for documents halfway through the chat — the conversation stalls and the agent just has to wait. Before you start, keep these within reach:

• The exact rejection message: screenshot it or copy it down — it's the first thing the agent will want to see;
• The ID you submitted: a clear photo of the original, so you can send it right away if they ask for it again;
• Address proof (if you're going for advanced verification): the one in your own name, recent enough;
• Basic account info: the email / phone number you registered with, so the agent can locate your account;
• A tidy description of the problem: get the sequence of events straight so the agent isn't asking follow-up after follow-up.

Not sure what you need? Run our face-fail self-diagnosis tool first to rule out the face-scan issues, then use the appeal message builder to draft what you'll send support. With the documents ready and the wording smooth, your odds of settling it in a single conversation go up a lot.

And a note on mindset: an appeal is teamwork, not an argument. An agent can only do so much, so keep the emotion in check and lay out the facts clearly, and they're more willing to give it an extra look. Wait patiently for a reply, and don't open a pile of duplicate tickets out of impatience — multiple tickets actually slow things down.

Once verification passes, check the account page for the functions, limits, and status actually available to you. Do not infer from a guide that a particular function or benefit has necessarily been restored.

A few questions people keep asking