The withdrawal sits at "processing" for eleven hours. The balance is there, the address is correct, the network is right, and nothing on the screen explains anything. Meanwhile the position you wanted to fund has moved. This is one of the more common frustrations in crypto funded trading, and the causes are a short list rather than a mystery.
The automated checks that fire before a human sees anything
Every regulated exchange screens outbound transactions against chain analytics. The destination address is scored on its exposure to sanctioned entities, darknet markets, mixers, known theft proceeds and high risk services, usually by hop distance. An address one hop from a mixer scores badly even if you have never touched a mixer, because the risk model does not care how the exposure got there. A bad score routes the transaction to manual review, which is the hold you are looking at.
The second automated layer is the travel rule. Transfers above the applicable threshold between hosted providers must carry originator and beneficiary information. If the receiving provider does not support the messaging protocol your exchange uses, or the beneficiary details you entered do not match what the counterparty expects, the transfer stalls while the data is reconciled. Sending to an unhosted wallet triggers a different requirement, often a declaration of ownership or a signed message proving control of the address.
The third is sanctions screening on names and jurisdictions, which is unforgiving by design. A name matching a listed individual produces a hold until it is cleared as a false positive, and firms tune these systems to over-match rather than under-match because the penalty for missing a real hit is not commercial.
Account-level triggers you set off yourself
Several holds are the account's own security features working. Changing the password, adding a device, changing the two factor method or adding a new withdrawal address commonly starts a cooldown of twenty four hours or more on withdrawals. The cooldown exists precisely so a stolen session cannot be converted into an outbound transfer before the real owner notices, and no support agent will override it, because the request to override it is exactly what an attacker would send.
Sudden pattern change is the other trigger. An account that deposits monthly and withdraws quarterly, then attempts to move the entire balance to a new address minutes after a login from an unusual location, will be stopped. That is the system doing its job.
A hold on a withdrawal to a new address is the single most common case, and it is also the one you can eliminate in advance. Whitelist the addresses you use during a calm week, let the cooldown expire, and the transfer you actually care about later goes straight through.
Source of funds, and why the questions feel intrusive
When a hold escalates, the exchange asks where the money came from. Bank statements, exchange records, an employment or business trail, tax documents. This feels disproportionate to a trader moving their own money, and it is not personal: under AML law the firm has to be able to evidence the origin of funds it processes, which is the same requirement a broker applies through its own source of funds checks.
The requests that resolve fastest are the ones answered completely on the first attempt with documents that reconcile. Partial answers, screenshots with the balance cropped out, or explanations that do not match the on chain history extend the review rather than shortening it. Arguing with the agent achieves nothing, because the agent cannot release a case the compliance queue owns.
Network conditions get blamed for holds they did not cause
Not every stalled transfer is a compliance hold. A withdrawal that shows as sent but has no confirmations is a network problem: fee too low for current conditions, or congestion on the chain. A withdrawal that never leaves the exchange's own queue is an internal one. The distinction is visible in seconds, because a transaction hash means the exchange has broadcast it and the delay is on chain, while no hash means it never left the building.
Exchanges also suspend withdrawals for a specific asset or network during wallet maintenance, chain upgrades or after a suspected incident. These are announced on status pages and affect every user rather than your account alone. Checking that before opening a ticket saves a day, and it also tells you which question to ask if you do.
What this means for traders funding accounts
Treat the withdrawal path as part of the plan rather than an afterthought. Whitelist addresses before you need them. Keep the funding route and the payout route the same, since brokers and exchanges both dislike money that arrives one way and leaves another. Keep your own records of where funds originated, because the request will come at the least convenient moment and the answer is much easier when the documents already exist. Traders who split holdings between an exchange account and self custody should also understand what custody actually changes about who can pause a transfer at all.
For firms on the receiving side, the lesson is the same in reverse. Withdrawal review is unavoidable, but silence is not. A client who can see that a payout is in compliance review, with a stated document request and a timestamp, opens far fewer angry tickets than one staring at a blank status. SINGUARD builds payout queues in the client portal for that reason: the hold is a legal requirement, the confusion is a product decision. The same principle drives how AML holds on withdrawals should be communicated at a broker.
A held withdrawal is a delay, not a loss. What turns it into a real problem is a trader who assumed funds were instantly available and sized a position accordingly.
"Nobody at the exchange enjoys holding your withdrawal. It costs them a support ticket and it costs them goodwill. They do it because the alternative is explaining to a regulator why they did not."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Most holds are automated: chain analytics scoring of the destination address, travel rule data mismatches, or a sanctions screening match.
- Password changes, new devices and newly added withdrawal addresses start cooldowns that support staff will not and should not override.
- Source of funds requests resolve fastest when answered completely on the first attempt with documents that reconcile with the account history.
- Whitelisting addresses in advance and keeping deposit and withdrawal routes identical prevents most avoidable holds.
Frequently Asked Questions
How long does a crypto withdrawal hold usually last?
It depends on why it fired. A new address cooldown is a fixed period, often twenty four to forty eight hours. A compliance review depends on the queue and on how quickly you supply documents, and can run considerably longer if the first response is incomplete.
Why was my withdrawal flagged when I have done nothing wrong?
Screening looks at the destination address's exposure to high risk sources, not at your intentions. An address that has received funds from a flagged service, even indirectly, can score badly. Systems are tuned to over-flag because missing a genuine hit carries regulatory consequences.
Can an exchange keep my crypto permanently?
A regulated provider holds funds pending review and releases them once the checks are satisfied, unless a legal order or a sanctions match requires otherwise. That is very different from an unlicensed platform with no supervisor to complain to, which is one reason where you hold funds matters.
About the Author
Roman Onta is an Executive Director at SINGUARD. He builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals side by side with his brother Alex Onta, and he helped on the design of eTrader, the division Alex built and leads. His ground is worldwide payment processing, AML compliance and the corporate structures brokers are built on, work the two of them carry together, shaped by executive roles in the UAE and international corporates. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.