Account HelpLogin and verification guidance
Help when you need it
Contact SCR99 Support
Use the official member support channel and prepare the right information so your question can be reviewed efficiently.
A good support request is short, specific and free of secrets that should never leave your device. The aim is to help the team identify the account event without exposing a password, code or full payment credential.
Transaction HelpPrepare the reference details
Offer QuestionsCheck campaign conditions
Play SupportResponsible gaming assistance
Prepare your request
Get the Right Help Faster
For privacy and security, account-specific questions should be raised through the support channel shown after official member login. Avoid sending passwords, one-time codes or full financial details through public messages. Anyone asking for those items is not following a safe process.
A clear description, transaction reference, date, time and relevant screenshot can help support understand an issue. Remove unrelated personal information before sharing an image. Crop the screen so the useful part is visible and the rest is not.
Duplicate messages rarely speed a case up. If you already have a reference number, reply in that thread rather than opening a second copy of the same question. Add new facts, not the same paragraph again.
This page explains how to prepare. The live channel itself sits behind official access because that is where identity and account history can be reviewed more safely.
Account Access
Explain whether the issue involves login, password recovery, verification or account settings. Use the recovery steps shown on the official member page first. A second account created in a hurry can make the original problem harder to repair.
Support should never ask for your existing password or one-time security code. If a message asks for those, stop and return to the official access page. Reset through the published flow instead of sending secrets by chat.
Transactions
Provide the transaction type, date, amount, payment channel and reference number. Processing times can depend on verification and payment provider checks. A pending item is not always a failed item, so include the status shown in history.
Do not submit the same request repeatedly while an active case is being reviewed. If new information appears, add it to the existing case. Repeated new tickets can slow matching rather than speed it up.
Promotions and Games
For promotion questions, include the offer name and the term that needs clarification. For a game issue, include the title, provider and round reference where available. “The bonus is wrong” is harder to review than a named campaign and a quoted sentence.
Screenshots should show the relevant error or history without exposing private login information. If the screen includes a password field or a one-time code, do not send that image.
Responsible Gaming Requests
You can contact support to ask about limits, cooling-off options or self-exclusion where those tools are available. You do not need a long explanation to start that request. A short statement that you want account controls is enough.
If the situation feels urgent, use local professional services for financial or mental health help as well. Platform tools can restrict an account. They are not a replacement for medical or counselling support.
What to Leave Out
Leave out passwords, PINs, full card numbers, one-time codes and copies of identity documents unless the official flow specifically asks for a verification file through a secure upload. Email and public chat are the wrong places for those items.
Leave out unrelated complaints in the same ticket. One topic per case is easier to assign. A payment question mixed with a game question mixed with a VIP question often has to be split before anyone can answer.
After You Send a Request
Keep the case reference, the time you sent it and any follow-up questions. If support asks for extra detail, reply with that detail only. A long restatement of the original message is usually less useful than the missing reference number.
When the case is closed, save the outcome. If the same issue returns later, the earlier reference can shorten the next review.
Write the case once
A Short Template for SCR99 Support Messages
You can adapt this structure to almost any account, payment, offer or game question. Short sentences are easier to route than a long story.
Start with the topic and the time
Say whether the case is about login, a transaction, an offer, a game round or a responsible gaming request. Then give the date and time, including the time zone if you know it. That already removes a lot of guesswork.
Add the identifiers, not the secrets
Include username or account ID if shown, transaction reference, offer name, game title, provider and round ID. Do not include the password you use to open the account or any one-time code from email or SMS.
Describe what you expected and what you saw
Two short lines are enough. For example, you expected a listed status to change after a deposit, and the history still shows pending. Attach a cropped screenshot of that status if it helps.
Create a clear request
Before Contacting Support
A prepared message can reduce unnecessary back and forth and protects your account details.
-
1
Choose the Topic
Identify account, payment, offer, game or responsible gaming support before you write.
-
2
Gather Details
Prepare dates, references and a short description of what you expected and what you saw.
-
3
Protect Your Data
Remove passwords, codes, full financial credentials and unrelated personal details.
-
4
Track the Case
Keep the support reference until it is resolved and reply in the same thread when you can.
Questions and answers
Support FAQs
Security reminders and guidance for common support requests.
Where should I ask an account-specific question?
Use the official support route available through the SCR99 member access area. Public pages can explain how to prepare, but they cannot see your account history.
Should I send my password to support?
No. Never share passwords or one-time security codes with anyone. Official recovery tools do not need your existing password sent by chat or email.
What should I include for a transaction question?
Include the type, date, amount, payment channel and reference number without exposing full financial credentials. Add the status shown in history if it is visible.
How can I explain a game issue?
Provide the game title, provider, time and round reference together with a relevant screenshot when available. Crop out login fields and codes.
How many times should I send the same request?
Once is enough until you have new information. Reply in the existing case with the extra detail rather than opening duplicate tickets.
Can support help with responsible gaming limits?
Yes. Ask through the official channel about available limit, cooling-off or exclusion options. You can keep the request short.
What if someone contacts me first claiming to be support?
Do not reply with account secrets. Return to official member access and use the channel shown there. Unsolicited password requests are a warning sign.
Official assistance
Access Member Support Securely
Log in through the official page to find the current support channel.