Why it didn’t pass: reading a rejection

First: turned down, or still waiting?

On screen these two look almost the same, and they ask for opposite things. One wants you to change something. The other wants you to leave it alone. Three rows will usually settle it.

Where to look	Looks like still running	Looks like a decision
Notifications	Nothing in email or push that states an outcome	One message that states an outcome
The line on the page	Describes a state and nothing else	Names a reason, or asks you for something
What you should do	Change nothing yet	Identify the cause, fix it, then resubmit

If it fits neither column, treat it as the left one for now. Binance shows an estimated 15 minutes on the review screen while its help page says submitted documents are usually reviewed within 48 hours; those are two different numbers about two different things, and how long verification takes pulls them apart.

Then: pick your entry point from the wording

• Photo, document, unclear, corners, or information that doesn’t match — start with the checklist in 12 reasons and fixes, which is grouped by cause. If your name is written in Devanagari, Arabic or Urdu on the document, read that first section carefully; transliteration is the single most common mismatch in this audience.
• Face, movement, lighting, camera — go to fixing the liveness check. The section on old handsets and in-app browsers is the part people skip.
• Address, bill, document too old — back to what counts as proof of address, and pick a different document against the validity window for your country.
• No reason at all, only a status — read how long verification takes before doing anything.
• You already know what went wrong and only want to know when to send it again — resubmitting after a rejection.
• Somebody has offered to get you verified, or to sell you an account that already is — read this one before you reply to them.

Three ideas that make it worse