Name the restriction before responding
Capture the exact login message and check email, including spam, for a case-support or verification request. Record the last successful login, last deposit or withdrawal, device and province. Do not infer the reason from timing alone.
If a responsible-gambling exclusion is active, do not attempt to bypass it. If the message is a security or KYC review, respond through the authenticated route named in the notice.
- Exact restriction wording
- Case or email reference
- Last known good account event
Submit the smallest complete document set
Match each requested fact with one readable document: identity, address or payment ownership. Show all required corners and relevant names while masking information the request does not need. Keep the upload receipt or message ID.
Do not send passwords, authentication codes or unrequested full card data. A complete, well-labelled response is safer and easier to audit than several partial uploads across chat and email.
- One file per requested fact
- Readable and current
- Submission receipt retained
Escalate around a single outcome
After the stated review window, reply to the same case with the document list, timestamps and the outcome requested: restore access, identify the missing item or release an eligible withdrawal. Ask for a written status rather than opening duplicate tickets.
If access returns, enable strong authentication and confirm the account profile before transacting. Do not create a second account to work around the original lock.
Questions players ask
Is an account lock the same as self-exclusion?
No. The displayed notice or support response should identify the actual state.
Should I send every document I have?
Send only the complete set requested through the authenticated channel.
Can a new account solve the lock?
No. A duplicate account can create another compliance problem.
Last reviewed: 9 August 2026