Deposits are easy. Withdrawals are where the compliance obligation bites, because a payout is the moment money leaves the regulated perimeter and goes somewhere the firm cannot see. Every AML regime treats that point as the one requiring most certainty about who is being paid and why they are entitled to the money.
So payouts get screened. Most clear automatically. The ones that stop have hit a rule, and the rules are more predictable than the silence suggests.
What actually triggers a hold
Transaction monitoring runs a defined set of checks against every withdrawal, and a match sends the request to a human queue rather than to the payment rail.
| Trigger | What it suggests | What usually clears it |
|---|---|---|
| Payout destination differs from the deposit method | Possible layering between channels | Routing back to the original method, or evidence the new account belongs to the same person |
| Deposit in, little or no trading, withdrawal out | The account is being used to move money, not to trade | An explanation, and often a return of funds to source rather than a payout |
| Amount crosses a verification threshold | The client's checks no longer match the sums involved | Upgrading to the next verification tier |
| Name mismatch on the receiving account | Third-party payment, prohibited almost everywhere | An account in the client's own name |
| Screening hit on a sanctions or PEP list | Possibly a false positive on a common name | Date of birth and identity confirmation to rule the match out |
| New device, new country, changed bank details | Possible account takeover | Step-up authentication and a support verification call |
Two of those deserve emphasis. Third-party payments are refused by essentially every regulated firm, which catches out clients trying to withdraw to a spouse's or a company account. And the deposit-then-withdraw pattern with no trading is one of the oldest laundering shapes there is, so it is monitored closely even when the amounts are small.
What the desk is doing while you wait
The reviewer pulls the client file and looks for consistency. Does the identity documentation cover the amount being paid out. Does the trading history explain the balance. Do the deposit and withdrawal routes belong to the same named person. Does anything in the account's history conflict with what the client stated at onboarding.
Where the answer is unclear, the next step is a source of funds request, which is a request for evidence of where the deposited money came from. The reviewer is not trying to be difficult. They are building a written record that would satisfy an inspector reconstructing the decision later, which is why they ask for documents rather than accepting an explanation over chat.
If the review escalates, it goes to the officer described in the MLRO role, and at that point the timeline stops being the firm's to control. Where a report has been filed, some regimes require the firm to wait for consent from the authorities before releasing funds, and tipping-off rules mean nobody may tell the client that this is what is happening. A support agent giving a vague answer is often following the law rather than avoiding you.
A hold is a pause, not a confiscation. Firms do not profit from holding client money, and every day a payout sits in a queue costs support time and goodwill. The delay exists because the alternative, releasing money the firm cannot account for, carries consequences that outweigh the inconvenience.
How a client shortens it
Most of the delay is document quality. The requests that get resolved on the first pass share a few characteristics.
Complete verification before requesting a payout rather than after. Withdraw to the same method you deposited from, in your own name, and expect profit above the deposited amount to leave by a different route because a card refund cannot exceed the original charge. Send documents as full uncropped files with the name, date and issuer visible, not screenshots. And when a source of funds request arrives, answer it with something that ties a named person to a dated amount: payslips, tax returns, business accounts, a property completion statement, or a bank statement showing the money arriving.
Anything less usually produces a second request, and the second request is where the real delay lives. The tiered structure behind these thresholds is set out in KYC verification levels, and it is worth knowing which tier you sit in before the balance grows past it.
What the firm should be doing
From the operator's side, payout friction is a retention problem with a compliance cause, and most of it is fixable without weakening a single control.
Verify at the right moment. Asking for documents at registration produces abandoned sign-ups, and asking at the first withdrawal produces angry clients. Asking when a client crosses a threshold, with the reason stated, works better than either. Publish the payout rules in plain language, including the same-method rule and the third-party prohibition, so nobody discovers them at the worst moment. Show a real status in the client portal rather than a spinning indicator: pending review, documents requested, approved, sent. And keep the review queue staffed on the days people withdraw, which for retail trading is weekends and month ends.
Rail choice matters too, because a hold and a slow settlement look identical to the client. Knowing which route settles in minutes and which takes days is the difference between explaining a delay and inventing one, which is what payout rails compared is about. Firms onboarding corporate clients face the same evidence problem one level up, through the KYB file.
"Nobody enjoys holding a client's payout. But a firm that releases money it cannot account for is not being generous, it is borrowing against its own licence."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Most holds come from a small set of triggers: method mismatch, no trading activity, threshold crossings, name mismatch, screening hits and device changes.
- Third-party payouts are refused almost everywhere. The receiving account must be in the client's own name.
- Source of funds requests are answered with documents linking a named person to a dated amount, sent whole rather than as screenshots.
- Firms cut complaints by verifying at threshold crossings, publishing payout rules plainly and showing a real status instead of a spinner.
Frequently Asked Questions
Why must a withdrawal go back to the deposit method?
Returning funds along the route they arrived on is a standard control against layering, where money enters through one channel and leaves through another to break the trail. It is also a card scheme requirement for refunding card deposits. Profit above the deposited amount usually leaves by a different method, because a card refund cannot exceed the original charge.
How long can a firm hold a withdrawal?
Routine document checks are usually a matter of days. A hold connected to a filed report can last as long as the applicable law requires, and in some regimes a firm must wait for consent from the authorities before moving the money at all. The firm cannot shorten that part and, under tipping-off rules, often cannot explain it either.
What documents release a source of funds hold fastest?
Documents that connect a named person to a dated amount. Payslips, an employer letter, tax returns, audited accounts for a business owner, a completion statement for a property sale, or a bank statement showing the funds arriving from the named source. Screenshots, cropped images and statements with the account holder's name removed usually cause a second request rather than a release.