Binance troubleshooting
& support
The most common issues on Binance and how to fix them — error codes and their meaning, KYC rejections by cause, how to spot phishing and fake sites, and how to reach support so you get a fast, clear answer.
Common error codes explained
The messages most reported on Binance and how to resolve them. If you see the same code, check this table first.
| Error message | Meaning | How to fix |
|---|---|---|
| Service unavailable in your region | Some features are restricted for your region/IP | Turn off VPN, close incognito, clear cache, and check your account's country setting |
| Login failed (Code: 100007) | Wrong password / new IP detected | Reset your password and click the 'approve new IP' email sent to your account |
| 2FA code incorrect | 2FA time mismatch | Turn on automatic phone time sync and sync the OTP app's time |
| Withdrawal suspended for 24h | 24h restriction after a password/2FA/email change | Wait 24 hours (can't be lifted, a security policy) |
| Min withdrawal amount not met | Below the minimum withdrawal amount | Check the minimum withdrawal amount per coin (e.g. BTC 0.0005) |
| Network is busy / Try again | That coin's network is congested | Retry after 5–10 min, or choose another network (BEP20, etc.) |
| Risk control triggered | Abnormal activity detected → temporary lock | Request unlock after email verification + selfie identity check |
| Identity verification failed | KYC verification rejected | See the 'Handling KYC rejections' section below |
| Order does not exist / Already filled | Already filled or canceled | Check the status in Order History |
| Insufficient balance | Not enough balance | You may need to 'Transfer' funds between your Funding and Spot wallets |
Not signed up yet?
Enter the code below at sign-up for a permanent trading-fee discount. It only applies to new sign-ups.
Handling KYC rejections by cause
The four cases people get stuck on most. Match the reason in the rejection message and respond accordingly, and almost all pass on the next try.
① "Document is blurry / not clear"
Meaning · The ID photo is blurry or text recognition failed.
Fix
- Shoot in bright natural light or white LED
- Flash OFF (reflections hide the text)
- Make sure all 4 corners of the ID are visible
- Photograph the physical ID (scans not recommended)
② "Name does not match"
Meaning · The name you entered doesn't match your ID.
Fix
- Use your passport (name is stated clearly)
- Confirm the spelling matches exactly
- Watch the order: First name = given name, Last name = surname
③ "Liveness check failed"
Meaning · The selfie live check (turning your head/blinking) failed.
Fix
- Remove any glasses, hat, or mask
- Face forward under bright lighting
- Turn your head slowly as requested (not too fast)
④ "Country of residence mismatch"
Meaning · Your selected country doesn't match your IP location.
Fix
- Turn off VPN and select your actual country
- Enter your real country of residence accurately
- Country of residence is hard to change later, so choose carefully
How to spot phishing and fake sites
The scam patterns that catch people most. Recovery is nearly impossible once you're hit, so learn the patterns in advance.
Fake domain patterns
The only official one is binance.com. Variant domains are fake.
- ❌ binance-app.com / binance-vip.com
- ❌ binance-event.com (impersonating events/airdrops)
- ❌ bᎥnance.com (a look-alike character instead of the letter i)
- ❌ any "regional branch" domain (e.g. binance-xx.com)
Check before connecting
- Read the domain in the address bar directly (don't click search ads)
- Access only from a bookmark
- HTTPS lock icon + the domain exactly 'binance.com'
Messenger impersonation scams
Anyone claiming to be a 'Binance regional branch' or 'official Binance staff' on a messenger is a scam.
- ❌ 'You won an event, verify now' → lures you to enter your seed
- ❌ 'We'll help unblock your withdrawal' → forces a deposit
- ❌ 'I'm a Binance employee' → asks for permissions/codes
- ❌ 'Signal room / guaranteed profits' → vanishes after you deposit funds
Official policy
- Binance staff never contact you first
- They never ask for your 2FA code, password, or seed
- 1:1 support happens only in the on-site live chat
Fake deposit-notification scam
In a P2P sale, a buyer sends a forged deposit notification and takes your crypto before the money actually arrives.
How to prevent
- Don't trust the notification → check your bank app directly
- Confirm the sender name and amount match 100%
- If suspicious, file an 'Appeal'
Fake mobile apps
Fake 'Binance' apps sometimes appear on the app stores.
Identifying the real app
- The developer is shown exactly as 'Binance'
- Very high download count and rating
- If unsure, download from the link at the bottom of binance.com
How to reach support and get a fast answer
The same request gets resolved much faster when you send it organized. Know-how people often miss.
Hours & response speed
- Operates 24/7 (AI chatbot + human agents)
- An AI chatbot responds first → if unresolved, ask for a human agent
- Type "I want to talk to a human agent" or choose 'Live agent'
- Live chat is disabled when logged out — log in first
Send everything at once
So the agent doesn't ask for the same info repeatedly, include it all in your first message.
Items to include
- Email / UID
- Time it happened (specify the timezone)
- Coin type / network
- Order number or TxID
- Screenshot (attach if possible)
'Live Chat' vs 'Submit a Request'
- Live Chat — instant, for simple questions (5 min – 1 hour)
- Submit a Request — email reply, for complex issues (1–3 days)
- For evidence-heavy matters (frozen withdrawal, locked account), use Submit a Request
- For network errors and quick questions, use Live Chat
Official channels only
- Reach support only through binance.com after logging in
- Track email replies in 'Support → My Tickets' (check spam too)
- Never share your password, 2FA code, or seed with anyone
- For global outages, the official X account (@binance) is fastest
Frequently asked issues & fixes
My deposit doesn't show up in my balance
Cause · Wrong network used / missing memo (tag) / coin confusion.
Fix order
- Get the TxID from the sending side's withdrawal history
- Search the TxID on the coin's block explorer → confirm 'Success'
- Confirm the receiving address matches your Binance address
- Confirm the networks match (TRC20 vs ERC20, etc.)
- For XRP/XLM, a missing memo/tag may be recoverable via support
My withdrawal is blocked for 24 hours
Cause · Changing your password, 2FA, email, or phone number triggers an automatic 24h withdrawal restriction.
Fix
- Waiting 24 hours is the only option (it can't be lifted early)
- Check the remaining time on the withdrawal screen
- Going forward, change security info only when necessary
I lost my 2FA (Google OTP) code
Cause · You lost the backup key (lost phone/deleted app).
Fix
- If you have the 16-character backup key, enter it in Google Authenticator on a new phone to restore instantly
- Without it, use 'Lost 2FA?' on the login screen and complete identity re-verification (usually 3–7 days)
- After recovery, register new 2FA and store the backup key somewhere safe
Blocked by 'Risk Control' on login
Cause · A login attempt from an unusual IP/device/country.
Fix
- Click the 'Authorize this device' email sent to your account
- Pass email + SMS + 2FA verification again
- If using a VPN, turn it off and try from your usual network
'Service not available in your region'
Cause · Region/IP restriction, or a country setting that limits some features.
Fix
- Clear cache/cookies and reconnect
- Turn off any VPN
- Check your account's country-of-residence setting
- If it persists, contact support about the restricted feature