The hold that looks arbitrary
A player who has passed identity verification can still see a withdrawal frozen when casino wildzy asks for source-of-funds evidence. The trigger is rarely the withdrawal amount alone; it is the relationship between deposits, play, and the account profile. For example, a £1,200 cashout after three months of £50 deposits may pass, while the same cashout after a sudden £3,000 deposit and a 20-minute session is flagged. The takeaway is that compliance teams assess patterns, not just balances.
Why the request lands after the win
Licensed operators must apply anti-money-laundering controls when transactions are large, unusual, or inconsistent with a customer’s known income. The cause is regulatory: a payment processor or licensing authority expects the operator to show that funds came from a legitimate source. A bank statement showing salary credits is strong evidence; a screenshot of a crypto wallet is not. When the document set does not connect the player’s identity to the funds, the review expands rather than closes.
What a clean source-of-funds file contains
The most efficient response is a short, indexed file that answers three questions: who the player is, where the money came from, and how it reached the casino account. Useful items include:
- Identity: a current passport or driving licence with a clear photo page and matching address.
- Income: two recent payslips or a tax document that shows regular earnings.
- Bank flow: a statement covering the deposit period, with salary credits and casino transfers visible.
- Ownership: evidence that the bank account or payment method belongs to the named player, not a relative or employer.
A common failure is sending a single payslip without the corresponding bank credit. Another is redacting the transaction dates, which makes the statement unusable for reconciliation.
Reducing friction before the next cashout
Players can avoid repeat holds by keeping payment methods in their own name, depositing from an account that receives their salary, and responding to document requests with dated, unredacted files. If a review is already open, ask the support team which specific transactions need explaining and provide a one-page cover note linking each document to those transactions. This turns a vague request into a closed checklist and gives the reviewer a defensible record.
Timeline, escalation, and what to keep
Most document reviews close within two to five business days once a complete file arrives; a mismatch can restart the clock. Keep a dated copy of everything sent and ask support to confirm the review is closed in writing. If the response stays vague, escalate through the operator’s formal complaints route and keep the ticket numbers. The record matters because the same source-of-funds questions can return at the next large withdrawal.