Understanding the problem
Next steps for unfinished access and recovery
An error can have an ordinary cause, but not every failure is a browser problem. The sections below distinguish verification, account status and the details needed to ask for help.
Recognise earlier requests when codes arrive late
Repeated code requests over a short period can produce messages arriving at different times. An older code may fail if you cannot identify the request it belongs to. Match the request time, recipient and current page instructions, and observe any waiting instruction given by the service.
Not receiving a message does not mean verification is complete. Check the connection, message filters and registered contact details. If you no longer have access to that number or email, use the service's account recovery process; entering a new identity does not establish ownership of an older account.
- Use one tab and one recent request when checking the problem.
- Keep the message time and error wording; do not record or email the actual code.
- If an unfamiliar person asks for a code, stop the request without sharing it.
Application status differs from incorrect credentials
Submission, initial verification and approval for use may be separate stages for an affiliate account. Changing a password cannot approve a pending application. Read application messages and requests for information, and establish the earlier application's status before applying again.
A restricted account also differs from an ordinary access error. Note any message about review, incomplete information or a temporary barrier. Quote the specific message when contacting that service; do not use another person's identity to bypass the restriction.
| Status | First action | Do not assume |
|---|---|---|
| Identity or password rejected | Check account type, identity and autofill | The account has been deleted |
| Verification incomplete | Match the latest request and recipient | More code requests will necessarily help |
| Application pending | Read the latest application message and requested information | Logging in completes approval |
| Restricted or under review | Follow the message and relevant support route | A new account can bypass the restriction |
A concise, safe description for help
Provide enough context to understand the problem: affiliate or player account, stage reached, error wording, date and time, device and checks already performed. Before attaching a screenshot, conceal names, numbers, balances, codes and other private information.
The relevant service assesses personal account status and recovery requests. Questions about unclear writing or contact on this website can be sent to [email protected]. Do not send passwords, one-time codes or complete transaction documents; this email does not provide access to an account.
- Account type and the stage where the problem occurred.
- Error wording and time, including the time zone.
- Browser, device and results of checks already made.
- The clarification or correction needed, in one sentence.