BingX Problems and How to Fix Them (2026): Deposits, Withdrawals, KYC

Something has gone wrong and you want it fixed, not a lecture. Almost every BingX problem is either a timing problem (it is working, it just has not finished) or a small input problem (wrong network, blurry document, frozen balance). Below are the six issues people actually hit, plus how to spot fake «support». The honest headline: in most cases nothing is lost, and this guide flags the exceptions.

Normal timelines: what is expected and when to worry

First, check whether you are actually outside normal — many «stuck» transfers are still inside their usual window.

What	Usually takes	Start investigating after
Crypto deposit	Minutes to ~30 min, by chain confirmations	1 hour, transfer already confirmed on-chain
Crypto withdrawal	Minutes to approve, then network time	A few hours with no TxID issued
Lock after a security change	A fixed short cooling-off period	Only once that period has passed
P2P order release	Minutes after the merchant confirms payment	The payment window expires — open a dispute
KYC verification	Minutes to a few hours	24 hours with no result and no reason given

Times vary with congestion and review volume, so treat the right column as a prompt to look rather than a promise. Note also that BingX is unavailable in the US, UK, Netherlands, Singapore, Canada, mainland China and Hong Kong.

Deposit not credited

Why this happens. A deposit needs the right network, the right address and enough confirmations. Four causes cover nearly all failures.

• Wrong network. You sent over one chain but generated a deposit address for another. The tokens exist — just not where the platform is looking.
• Not enough confirmations. Every chain needs a set number of blocks, and congestion stretches that out.
• Missing memo or tag. XRP, TON, ATOM and EOS route funds by memo; without it the deposit cannot be attributed automatically.
• Below the minimum. Amounts under the stated minimum for that asset and network are usually not credited.

What to do, in order:

1. Find the TxID in the wallet you sent from and open it in that network’s block explorer. No TxID means the transfer never left the sending side.
2. Check status and confirmations. Pending means wait; confirmed means the funds moved.
3. Compare the explorer’s network with the deposit page’s network. They must match exactly — the same ticker on a different chain is the most common failure of all.
4. Verify the receiving address character-for-character.
5. After an hour with everything matching, contact support in-app with the TxID, asset, network, amount, address and time. Without a TxID nothing can be traced.

The honest part: if you sent a coin over a network BingX does not support, recovery may be impossible. On a supported chain a misrouted deposit can sometimes be recovered manually, with no guarantee and no fast timeline. The real fix is prevention — send a small test amount on any new address or chain, as our deposit guide explains.

Withdrawal stuck or pending

Why this happens. A withdrawal passes platform approval and then the blockchain, and it can pause at either.

• Security hold. Changing your password, email, phone or 2FA device triggers a temporary withdrawal lock — deliberate, because it stops an attacker who just seized an account from emptying it.
• Network congestion. Once broadcast, the transaction belongs to the chain.
• Manual review. Large amounts, a new destination address or a first withdrawal after a long gap can route to a human — and limits follow your verification level.

What to do, in order:

1. Look for a TxID in the withdrawal record. If one exists the funds have left the platform, the explorer has your answer, and support cannot speed up a broadcast transaction.
2. No TxID? Check for a security lock. If you recently changed a credential, the cooling-off period has to run out — nobody can shorten it, support included.
3. Confirm your verification level covers the amount, and re-check the destination address and network.
4. Contact support with the withdrawal ID, asset, amount and timestamp if hours have passed with no TxID and no visible hold.

What does not help: resubmitting. A second request does not cancel or accelerate the first — it creates another withdrawal, so you may pay two network fees or send twice the amount. More in our withdrawal guide.

KYC rejected or stuck

Why this happens. Verification is largely automated image checking, so rejection is nearly always about the photo, not about you: glare from a flash, cropped edges, an expired document, a name mismatch between ID and account, or a selfie shot in poor lighting. KYC is mandatory for P2P, so this one blocks real activity.

What to do, in order:

1. Read the rejection reason in the verification section — it usually names the exact fault.
2. Reshoot the document in daylight, flat on a dark non-reflective surface, no flash, all four corners in frame, text sharp on your screen. No filters, no photo of a photocopy.
3. Check the expiry date — an ID expiring within weeks is often refused — and match the details exactly: full name, spelling, name order and date of birth as printed.
4. For the selfie: even front lighting, plain background, no hat, glasses or mask, following the prompts at a steady pace.
5. After two failures with the same document, switch to another accepted type — passport instead of national ID.

If the status sits on «under review» past a day with no reason given, raise it with support. Full walkthrough in our KYC verification guide.

Verification code not arriving

Why this happens. The code is generated instantly; delivery fails. Email codes land in spam or promotions. SMS codes are often filtered by the mobile carrier, which throttles automated international messages. Authenticator codes fail for a different reason: your phone’s clock has drifted, so the digits are calculated for the wrong moment.

What to do, in order:

1. Check spam and promotions, mark the message as not spam and add the sender to your contacts.
2. Wait two to three minutes before requesting again — rapid re-requests invalidate earlier codes and trigger rate limits.
3. For SMS: confirm the number on file is current, disable any spam-blocking app, and switch to email or an authenticator app if it keeps failing.
4. For an authenticator app: turn on automatic date and time, then use the app’s time-sync option — this fixes most «invalid code» errors.
5. Always use the newest code, since they expire quickly.

Lost the phone or authenticator entirely? That is an account-recovery case — see below.

Order did not execute

Why this happens. Usually the system working as designed, not a fault.

• The limit price was never reached. A limit buy fills only if the market trades at or below your price; close is not touched.
• Insufficient available balance. Funds committed to other open orders are frozen — your total can look fine while available is not.
• Wrong account. Spot and futures balances are separate.
• Order type mismatch. A market order guarantees execution, a limit order guarantees price.

What to do, in order:

1. Open the order list and check whether it is open, partially filled or cancelled.
2. Compare your limit price with the actual traded range on the chart.
3. Look at available versus frozen balance and cancel stale orders to free funds.
4. Confirm the asset is in the right account, transferring between spot and futures if not.
5. Decide what matters more — a market order if execution matters, a limit order if price does.

Spot trades cost 0.10% at the base tier, futures 0.02% maker / 0.05% taker, with a permanent discount of up to 20% when you sign up with a referral code — open an account with the fee discount.

Account access lost or suspicious activity

Why this happens. Lost phones, changed numbers, an authenticator reinstalled without its backup key — or a password reused from a breached site, or a phishing page that captured a login.

If you cannot log in:

1. Use the official password reset in the app or on the site — never a link from an email you did not request.
2. If 2FA is the blocker, follow the in-app recovery flow and expect identity checks; that friction stops somebody else doing this to you.
3. Reach support only through the app or official site — never a chat group, DM or number from search results.

If you suspect someone has been in your account, in this order:

1. Change the password to something unique and never reused.
2. Revoke all active sessions and devices, killing any attacker session.
3. Reset 2FA, storing the backup key offline, and delete or rotate every API key — especially any with withdrawal permission.
4. Enable the withdrawal address whitelist so funds can only leave to pre-approved addresses.
5. Set an anti-phishing code so genuine emails carry a phrase only you know.
6. Contact support with times and details of what you saw.

Steps 4 and 5 are worth doing today even if nothing is wrong — they cap the damage of any future compromise. Our security guide sets both up in minutes.

How to tell real support from a scammer

More money is lost to fake support than to any technical fault, and it happens precisely when you are stressed and looking for help. Real support:

• Is reached only through the help centre or live chat in the official app or website — you start the conversation.
• Never messages you first on Telegram, WhatsApp, X, Discord, Instagram or by phone.
• Never asks for your password, 2FA code, email or SMS code, API secret or seed phrase.
• Never asks you to move funds to a «safe wallet», and never charges a fee to unlock a withdrawal.
• Never asks for remote access or a screen-share of your login.

Anything pairing urgency with a request for credentials or a transfer is an attack, however official the badge or group name looks. Scammers also watch public complaint threads, so if you post about a stuck withdrawal anywhere public, treat every DM that follows as fraudulent.

If you trade P2P, run our P2P safety checklist before your next order: escrow discipline, verifying payment in your own banking app, and the exact phrases scammers use.

The short version

Check the TxID before assuming anything is lost, wait out security holds, reshoot documents in daylight, read available balance rather than total, and treat unsolicited «support» contact as fraud. Put the TxID or order ID, asset, network, amount and time into one message when you open a ticket. The rest is prevented by three habits: a test transaction on any new address, the withdrawal whitelist and anti-phishing code left on, and KYC finished before you need it.

New here? Crypto deposits are free, spot trading is 0.10%, and the up-to-20% referral discount is permanent from your first trade — register on BingX here. As always: crypto is volatile and high-risk, so only commit what you can afford to lose.