What is still missing from your verification?

Get the missing detail into writing

Save the complete request, including its date and any attachment instructions. If support asks only for more documents, ask which document, what period and what information it must show. You cannot correct an unknown requirement by sending a larger pile of files.

For a rejected statement, check whether every requested page is present, whether the requested period is covered and whether the account holder is visible. A transaction date on a statement can differ from the document's issue date. Ask which date the reviewer needs.

If a name or address has changed, describe the change and ask what linking evidence the reviewer accepts. If a joint account or different payment holder is involved, explain that fact before uploading. Avoid editing a financial document to make it appear to match.

Keep the original file and the acknowledgement. A new upload filename, date and support reference let you distinguish a new submission from the first file still awaiting review.

A UK example: Sky Vegas distinguishes ID from address proof

Sky Vegas directs verification uploads through My Account, Account Settings and Document Uploader, with secure Live Chat as an alternative. Its ID and address requirements differ, so the same PDF or screenshot can have a different result depending on the requested check.

Source of funds answers a different question

An identity check establishes whose account it is. A source-of-funds request asks where the money used to play came from. Sky Vegas's explanation asks users to identify that source and support it with suitable records, such as evidence of earnings or a bank statement showing incoming funds.

Read the actual request before choosing a file. If it asks about a particular income payment, a photo ID alone cannot explain it. Ask which period and transaction the reviewer needs, then supply the requested supporting record through the secure channel.

When a requested record is unavailable, tell the reviewer why and ask which alternative can answer the same question. Keep that answer with the request instead of guessing that a different file will be accepted.

Repeated uploads can hide the unanswered question

In a UK Lottomart discussion, a player reported a £3,400 cashout followed by repeated requests for statements and payslips. The player also described an account freeze after disclosing gambling harm. The public discussion did not confirm a payout or establish the operator's reason for the restriction.

That case leaves two questions to record separately: what remained in the financial review, and what happened to the withdrawal during the account restriction. It gives no basis for promising that one more upload will release the funds.

If your account is restricted, ask how the existing withdrawal is being handled and which outstanding review applies to it. Keep that answer separate from any access-to-play request. You do not need to frame the payment question as a request to resume gambling.

Send a follow-up the reviewer can answer

My withdrawal remains pending after my document submission. Your latest request asks for this file and period. I uploaded it on this date and have the acknowledgement. Please confirm whether that submission has been reviewed and identify the exact missing or rejected detail. If a different document is required, please state its type, period and secure upload route.

If support repeats the same request, reply with the existing upload reference and ask whether the previous file was rejected or has not yet been reviewed. Add each answer to the ledger. A specific format rejection belongs in the rejected verification document guide; a general dispute needs the complaint evidence file.