An identity-check request is not permission to send documents to any person who asks. Before uploading anything, return independently to the official app or domain, sign in through the normal route, confirm that the same request appears inside the account, and read the current instructions and privacy notice. Do not send an identity document, password, PIN, one-time code or full payment credential through this News site, a public contact form, social media or an unsolicited message.
First confirm that the request is genuine
Treat a verification link received by email, SMS, messaging app or social media as unverified until you confirm it independently. Do not use the link in the message as your only route back to the account.
Use this sequence:
- Open the official product yourself. Use the app you already installed from its verified listing or type the known official domain rather than following a shortened or unfamiliar link.
- Sign in through the normal account route. Check whether the same verification request, status or notice appears after you sign in.
- Inspect the destination before choosing a file. Check the domain, app identity and secure connection. A padlock alone does not prove that a site belongs to the operator.
- Read the current request. Note which field is requested, why it is requested, the permitted file type and any stated size or image-quality rule. Requirements can differ by account and product.
- Use official account support when the message and account disagree. Return to the support entry shown inside the relevant product. Do not reply to the unverified sender with a document or secret.
Lotwin's public website cannot inspect an app account or accept verification documents. Current account requirements and any upload destination must be confirmed inside the relevant product or its official account-support route. This guide does not assert that every Lotwin package presents the same verification screen, asks for the same document or completes a check within a fixed time.
For a broader domain and operator check, use the casino legitimacy guide.
Check whether the request explains its purpose
The Nigeria Data Protection Commission's 2025 implementation directive describes principles including transparency, purpose limitation, data minimisation, storage limitation and appropriate security. It also says software processing personal data should make its privacy information available and describe the categories and purposes of processing.
For a user, that supports a practical check: before uploading, look for a clear explanation of what is requested, why it is needed, who handles it, how to ask a privacy question and where the applicable privacy information can be read. The directive does not mean that the NDPC has reviewed or approved a particular casino verification flow.
If the request is vague, asks for more information than the displayed purpose appears to require, or moves the conversation to a personal messaging account, pause and verify the route through official account support.
Prepare the file without exposing unrelated information
Follow the exact current upload instructions. Do not assume that a passport, National Identification Number, bank statement, payment card or proof of address is universally required; this page does not provide a standard document list.
Before choosing a file:
- make sure it belongs to the correct account holder and is the document actually requested;
- check that the image is readable and shows only what the instruction requires;
- remove unrelated files from the upload folder or photo-selection view where practical;
- close notifications and other apps before taking a screenshot;
- never include a password, PIN, CVV, one-time code or complete payment credential;
- do not alter, fabricate or submit another person's document.
Do not automatically cover or crop fields. Mask unrelated information only when the current upload instruction explicitly permits it. An unauthorised alteration can make a valid document unusable or create a misleading record.
Upload through one controlled session
Use a private device that you control and a trusted connection. Avoid a shared computer, public file-transfer service or public Wi-Fi for an identity-document upload. Update the app, browser and device security before handling sensitive files when an update is available from the official source.
During the upload:
- Confirm the official destination again.
- Select only the intended file.
- Read the preview before submitting.
- Submit once and wait for the displayed result.
- Record the date, local time, status and any case or reference number.
Do not keep retrying through different links when a status is unclear. Repeated attempts can create several records and increase exposure. Save the displayed status, then use the official account-support route to ask whether the original submission was received.
Keep a safe evidence record
A useful private record contains the request date, the official route used, the type of item requested, the displayed status, a reference number and any support case number. It does not need to contain another copy of every sensitive field.
Store any local document copy securely and delete unnecessary temporary exports, downloads or screenshots from shared folders and cloud links. Do not post a verification screenshot publicly to prove that a request exists. If support needs to identify the case, begin with the reference number and provide additional information only through the verified secure route.
The Payments and Verification hub explains the boundary between general education and account-specific support. Lotwin's Website Privacy Policy describes this public site's data handling; it should not be assumed to replace privacy information shown inside a separate app account flow.
When verification appears during a pending withdrawal
If a verification request appears while a withdrawal is pending, preserve both records separately: the exact withdrawal status and reference, plus the verification request and its status. Do not make another deposit, repeat the withdrawal or send a document to an unsolicited helper in an attempt to release the first request.
Use the pending-withdrawal checklist for Nigeria to distinguish the operator stage from a bank or wallet stage. Neither page can predict approval, payment or completion time.
Stop immediately if a message asks for secrets
A request for a password, PIN, CVV, one-time code, complete card details, remote screen access or payment to an individual is a stop signal. Do not continue the conversation or install software from the sender. Return to the official product, secure the relevant email and payment accounts if needed, and report the impersonation through a verified channel.
Verification should reduce account and payment risk, not create a new exposure. Confirm the route, disclose only what the current legitimate instruction requires, keep a minimal record and pause whenever the request and official account do not match.
Responsible play
Account verification does not make gambling profitable or remove its financial risk. Do not deposit or chase a result while an account or payment status is unclear. Set a spending limit before play, stop when gambling affects essential expenses, and use the Responsible Play page for support and safer-play guidance.