Exchanges

Bybit Froze Withdrawals: What to Do Before Contacting Support

Financial charts on a laptop screen, representing exchange withdrawal restrictions
In brief

If Bybit has frozen withdrawals, first distinguish a short security hold after a password or 2FA change from a request for withdrawal documents and a full AML / SoF review. Record the status, case number, and facts, collect evidence showing the source of funds, and avoid sending a generic "unfreeze it urgently" message. See exchange account unfreezing for the process of working with an exchange.

Two different withdrawal-hold scenarios

A security restriction lasting about a day. Bybit's help materials list actions after which withdrawals, internal transfers, and some other operations are temporarily unavailable: changing a password, email address, phone number, fund password, resetting Google Authenticator, changing Passkeys, and similar security steps. This is a security hold, not necessarily an AML case; it is often enough to wait for the restriction window to expire and avoid opening duplicate requests.

Additional verification for a specific withdrawal is a separate scenario. The exchange may request documents such as identity confirmation, proof that you control an address, or evidence of logging in to an external platform. Bybit's help center states that if documents are not provided within the allotted window, the withdrawal request may be rejected. For the broader context, see the top reasons exchange accounts are frozen.

Also check the withdrawal limits for your KYC level. If the amount exceeds the daily limit for your verification status, the issue may be the limit rather than an account freeze. Use the account dashboard and current help-center limit tables, not screenshots from year-old chats.

What the document package usually includes

For SoF / AML, the key issue is usually whether amounts and sources form a coherent chain: where the funds came from, which addresses or exchanges they passed through, evidence of income or asset sales, and the TxIDs of incoming transfers. If some documents are unavailable, explain the gap honestly and offer alternative evidence rather than attaching irrelevant files just in case.

Do not send a seed phrase, private keys, or full statements containing unnecessary personal data through an open chat. Use only official account channels. See Source of Funds for guidance on documenting the chain of funds. A similar KYC process on Bybit is covered in the Bybit $195K case.

If you are asked to prove control of a withdrawal address, the exchange may expect a small transfer or a screen recording showing you logging in to the external platform. Follow the instructions in your account exactly. Screenshots belonging to someone else and generic templates from Telegram will usually be rejected.

First steps while withdrawals are on hold

  1. Save a screenshot of the withdrawal status, the notification text, and the case number.
  2. Check whether you recently changed your 2FA or password. If so, first wait for the security window to expire.
  3. If additional withdrawal verification is required, open Funding history and follow Bybit's instructions rather than a link from search results.
  4. Prepare one document package for the specific request.
  5. Submit the complete package instead of sending fragments every three days.
  6. Never share a seed phrase or passwords.
  • Do not open a second account to try to withdraw at least some funds.
  • Do not route funds through friends; this makes the AML history harder to explain.
  • Do not use urgency or threats in correspondence.

If the funds have already moved to an external address and further transfers are likely, see emergency response. That is a different scenario.

When escalation may be appropriate

Escalation may be appropriate after you have submitted a complete initial package and received a clear rejection, or if there has been no reply for longer than the support team's usual response time. It is not a substitute for collecting the facts. An assessment can identify the next route: improving the package, escalating with the exchange, or using another service. The outcome is not guaranteed and depends on Bybit's policies and the quality of the evidence.

SituationRealistic next step
Recent 2FA or password changeWait for the security window to expire
Request for withdrawal documentsSubmit one complete package as instructed
Complete package followed by rejection or prolonged silenceEscalate and assess the available route
Guaranteed unfreezingNo — the outcome depends on policy and facts
Limitations

Risks and limitations

  • Unfreezing is not guaranteed; the outcome depends on exchange policy and the quality of the evidence.
  • Using urgency and threats in a support request usually makes communication less effective.
  • Sharing a seed phrase or passwords with third parties creates a risk of losing all assets.
  • Help-center limits and wording change; check the current text in your account.
Sources

Sources used

Next

Related resources

ServiceExchange account unfreezingBack to the blog
Next step

Need an assessment of your situation?

Briefly describe what happened — without seed phrases or private keys. We will outline possible routes and assess their feasibility.

Request a free assessment
Free initial assessment

Describe what happened

Answer a few questions so we can assess the situation and suggest the next steps.

Do not send seed phrases, private keys, passwords, or 2FA codes. They are not needed for an initial assessment.

Do not send seed phrases, private keys, passwords, or 2FA codes.