Account verification literacy · English
Record the purpose and channel of a withdrawal ID request
A verification record for linking each requested document to age, identity, fraud or source-of-funds purpose while checking timing, secure upload and complaint options.

Verification timing and purpose both matter
An account can need age, identity, anti-fraud or financial information at different points. A document request should be tied to a stated purpose and sent through a verified channel. Record what could have been requested earlier, what new event prompted the current request and which document fields are actually necessary.
The UK Gambling Commission explains age and identity checks, says information should be requested promptly where it could have been sought earlier and notes that later legal obligations can still create additional checks. Tie every document request to the source title, access date and jurisdiction on the verification-purpose register before adding a an identity request connected with a withdrawal conclusion. start with the source's narrowest supported statement.
Copy the stated purpose
Age, identity, self-exclusion screening, fraud review and source-of-funds checks are not interchangeable. Ask the business to identify the reason for each requested item. Do not infer wrongdoing simply because enhanced verification occurs. Tie every document request to request, stated purpose, legal or terms basis and date while examining an identity request connected with a withdrawal. Log purpose, timing, secure channel and receipt across the verification-purpose register. Attribute the copy the stated purpose observation to UK Gambling Commission age and ID verification guide, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For request, stated purpose, legal or terms basis and date, separate public guidance from private account facts. Send one verified evidence set and wait for its stated review; preserve both timestamped versions whenever the verification-purpose register still shows a conflict.
Build the timing line
The account-opening date, first deposit, play, withdrawal request and verification message show when the need arose. Place each event in chronological order with the original timestamp. A delayed request does not by itself prove the business lacked a later legal reason. Tie every document request to account opening, deposit, withdrawal and request time while examining an identity request connected with a withdrawal. Log purpose, timing, secure channel and receipt across the verification-purpose register. Attribute the build the timing line observation to UK Gambling Commission age and ID verification guide, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For account opening, deposit, withdrawal and request time, leave unanswered fields visibly open. Send one verified evidence set and wait for its stated review; preserve both timestamped versions whenever the verification-purpose register still shows a conflict.
Verify the upload destination
Identity files can be valuable to impersonators and should not travel through a link copied from an unsolicited message. Reach the account or support route independently and confirm the hostname. HTTPS alone does not prove that a lookalike site belongs to the business. Tie every document request to hostname, account route, support confirmation and upload method while examining an identity request connected with a withdrawal. Log purpose, timing, secure channel and receipt across the verification-purpose register. Attribute the verify the upload destination observation to UK Gambling Commission age and ID verification guide, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For hostname, account route, support confirmation and upload method, start with the source's narrowest supported statement. Send one verified evidence set and wait for its stated review; preserve both timestamped versions whenever the verification-purpose register still shows a conflict.
Minimise document exposure
Different purposes can require different fields, dates or document types. Ask whether redaction is permitted and send only through the confirmed mechanism. Do not obscure information the verified process legitimately requires without first asking. Tie every document request to document type, required field, permitted redaction and retention while examining an identity request connected with a withdrawal. Log purpose, timing, secure channel and receipt across the verification-purpose register. Attribute the minimise document exposure observation to UK Gambling Commission age and ID verification guide, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For document type, required field, permitted redaction and retention, separate public guidance from private account facts. Send one verified evidence set and wait for its stated review; preserve both timestamped versions whenever the verification-purpose register still shows a conflict.
Record status without repeated uploads
Processing can be pending, rejected, incomplete or accepted, each with a reason and next step. Save acknowledgements and wait for the stated review window before resubmitting. Multiple copies sent through different channels increase exposure and confusion. Tie every document request to upload time, receipt, status, reason and next review while examining an identity request connected with a withdrawal. Log purpose, timing, secure channel and receipt across the verification-purpose register. Attribute the record status without repeated uploads observation to UK Gambling Commission age and ID verification guide, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For upload time, receipt, status, reason and next review, leave unanswered fields visibly open. Send one verified evidence set and wait for its stated review; preserve both timestamped versions whenever the verification-purpose register still shows a conflict.
Escalate the exact disagreement
A complaint should identify whether the dispute concerns timing, relevance, security, delay or account terms. Attach the narrow evidence set and the resolution requested. The regulator provides guidance but does not adjudicate ordinary transaction complaints directly. Tie every document request to complaint issue, evidence, requested resolution and case reference while examining an identity request connected with a withdrawal. Log purpose, timing, secure channel and receipt across the verification-purpose register. Attribute the escalate the exact disagreement observation to UK Gambling Commission age and ID verification guide, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For complaint issue, evidence, requested resolution and case reference, start with the source's narrowest supported statement. Send one verified evidence set and wait for its stated review; preserve both timestamped versions whenever the verification-purpose register still shows a conflict.
Assemble the verification-purpose register as six working rows
1) Copy the stated purpose — request, stated purpose, legal or terms basis and date; 2) Build the timing line — account opening, deposit, withdrawal and request time; 3) Verify the upload destination — hostname, account route, support confirmation and upload method; 4) Minimise document exposure — document type, required field, permitted redaction and retention; 5) Record status without repeated uploads — upload time, receipt, status, reason and next review; 6) Escalate the exact disagreement — complaint issue, evidence, requested resolution and case reference.
Use the Commission guide for Great Britain context
The consumer guide describes why businesses verify identity and finances, examples of documents and expectations around when requests are made. Open UK Gambling Commission age and ID verification guide over HTTPS and date that an identity request connected with a withdrawal source on the verification-purpose register.
It does not prescribe one universal document set, promise a processing time or decide an individual withdrawal. Send one verified evidence set and wait for its stated review. The site's source-checked guides explain related terms.
Send the minimum verified evidence once
A complete register should show purpose, timing, channel, receipt and outcome for every item without scattering identity copies across messages. Keep the verification-purpose register in date order and keep secrets outside it.
Identity verification should not become a reason for more play. An 18+ customer can pause completely while a withdrawal is reviewed, protect essentials and seek help if delay triggers borrowing or chasing. Use the responsible-play centre when stronger separation or confidential support is needed.
Source: UK Gambling Commission age and ID verification guide ↗
