Short answer
Before sending a verification document, confirm the requested check, the exact evidence needed and the submission route through the operator's official site or app. Ask which fields must remain visible and whether any alteration is expressly permitted. Prepare only the accepted evidence, submit it once through the confirmed route and keep a receipt that does not reproduce the document's sensitive contents.
This guide helps you decide how to share evidence. It does not certify a platform's security or supply a universal list of documents every player must provide.
Establish what the document must prove
An identity image, an address record and a payment-ownership document answer different questions. Start with the request itself: which check is unresolved, which account or transaction does it concern, and why is this particular evidence requested?
For the broader reasons behind checks, read identity checks before a lottery withdrawal. The useful next step here is turning a general instruction such as “send proof” into an agreed document specification. Do not send a collection of unrelated financial or identity records hoping that one will satisfy an unclear request.
If your name or address differs from the account record, explain the discrepancy through verified support and ask how to correct it. Do not edit a document to make it match.
Confirm the route independently
Open the operator from an address or app you already use. Locate its verification instructions or contact support there to confirm the request. An unexpected email's display name, logo or upload button is insufficient evidence of the recipient's identity.
LottoPark's terms, effective 22 September 2026, instruct users of its lottery and casino domains to supply documents through the secure method specified by support and to keep identity and payment evidence out of public or player chat. That is an operator instruction, not a verified test of its upload system.
If support directs you to a third-party verification service, ask it to confirm the provider and destination through the established official channel. A different domain may have a legitimate role, but you should resolve its identity before sending evidence. Do not bypass access controls or create another player account to reach a blocked upload area.
Agree the document and visible fields
Ask for a usable specification before taking photographs or exporting statements:
| Detail to confirm | Why it matters |
|---|---|
| Accepted document type | A document proving address may not establish payment ownership |
| Required side or pages | A front image, both sides and a complete statement are different requests |
| Relevant date or validity period | The operator may need current evidence for the stated check |
| Fields and edges that must be visible | Cropping can remove evidence needed to assess the document |
| Accepted file format and size | A technically rejected upload may never reach review |
| Any expressly permitted redaction | You need acceptance before concealing or altering information |
An example shows why instructions matter. Jackpocket's US support article on identity verification says that when its automatic check cannot verify a customer, it may request the front of a current driver's licence with all information visible and directs the customer to its secure document process. This is the named product's US help example. It does not establish acceptable documents for another operator or market.
Obtain permission before redacting
Do not assume that obscuring a document number, transaction description, balance, photograph or machine-readable area will be accepted. Likewise, an operator's permission to conceal one field on one document does not authorise changes to everything else.
Ask which fields, if any, may be hidden on the specific evidence requested. Keep the written answer with the submission reference. Follow only explicit operator instructions for the accepted document; if they conflict with the upload instructions, resolve the conflict before submission.
If the requested disclosure concerns you, ask why it is needed and whether an accepted alternative can establish the same fact. That question preserves the choice between providing appropriate evidence and seeking clarification. Inventing an edited replacement can create another verification problem.
Prepare and submit a readable copy
Use a device you control and review the file before uploading. Check that the selected file is the correct document, the required content is readable and no unrelated pages or other person's records are included. Follow the confirmed image and file requirements. Preserve factual content; do not change dates, names, amounts or other evidence.
Avoid unnecessary copies in messages, shared folders and public screenshots. Do not put identity numbers or full financial details in filenames or the support-message subject. Do not send a password, banking sign-in secret, card security code or one-time authentication code as verification evidence.
If the confirmed route is unavailable, ask for an approved alternative. Do not replace it with an unverified email address or a publicly accessible file link simply because that is easier.
Ask what happens after receipt
Submission and acceptance are different events. Keep the date, request reference, channel, general document type and acknowledgement; your private timeline does not need another full copy of every sensitive field. Ask whether the upload was received, whether it is readable and whether anything specific remains unresolved before resending it.
LottoMart's UK-facing privacy policy describes identity-verification and due-diligence providers among recipients of relevant information. For your own service, ask who handles the file, the purpose and the applicable retention category. When account use ends, raise those privacy questions separately from the operational instructions in cancellation versus account closure.
If you accidentally sent evidence to the wrong recipient or posted it publicly, stop sending further material, preserve a minimal incident record and contact the legitimate provider through its verified route. Ask about removal and the appropriate response to the exposed information. Follow the account security checklist if account access may also be affected. Do not publish the document again to illustrate a complaint.