MyStake Complaints and Dispute Resolution
MyStake complaints should be used after the normal support route when an account, payment, verification, bonus or game issue remains unresolved. A complaint is not the first step for a simple question or missing information.
The complaint process should start with the issue class: payment, verification, bonus, game access, account controls or another unresolved support case. Clear classification helps customer service review the case without mixing several problems into one message.
Prepare evidence before sending the complaint. Include dates, status, screenshots and specific IDs where available, but do not send passwords, card security codes, recovery links or unrelated private information.
Support Review Before Complaints
Support should be contacted before the issue becomes a complaint. Use the normal support routes first, then escalate only if the answer does not resolve the case.
A complaint should explain what happened, which support route was used, what response was received and what point remains unresolved. This makes the escalation easier to review.
Do not turn every follow-up into a new complaint. Keep the same issue history together so the customer service team can see the previous status and response.
Complaint Details and Evidence
Complaint evidence should be factual and specific. The best starting point is the issue type, account email, date, status, screenshot and any transaction or request ID shown in the account.
Keep the complaint focused on one unresolved issue. If payment, verification and bonus matters are all involved, separate them inside the same complaint instead of writing one general statement.
| Complaint Type | Include | Avoid |
|---|---|---|
| Payment complaint | Transaction ID, amount, method, date and status | Claims of guaranteed refund or instant payout. |
| Withdrawal complaint | Request date, amount, method and payout status | Submitting another payout without checking status. |
| Verification complaint | Request type, current status and visible message | Passwords, card security codes or bypass requests. |
| Bonus dispute | Promotion name, code if relevant and bonus status | Claims that support must add a bonus. |
| Game issue | Game name, time, device, category and screenshot | Claims that a result was guaranteed. |
| Account-control issue | Account-control request and support history | Requests to bypass restrictions or self-exclusion. |
Payment, Verification and Bonus Complaints
Payment complaints should be tied to the payment route and visible status. Use payment methods for method context, deposit status for funding issues and withdrawal status for payout issues.
Verification complaints should include the visible request type, current status and the support response already received. Use verification steps before escalating a KYC or payment-method review issue.
Bonus complaints should include the promotion name, bonus status, code if relevant and the term or account result being disputed. Use bonus terms before claiming that an offer was applied incorrectly.
Responsible Gambling and Account Controls
Responsible gambling and account-control complaints should be handled seriously and without promotional language. If the issue involves limits, self-exclusion or control tools, do not mix it with bonus or deposit requests.
Do not use complaints to bypass restrictions, create a duplicate account or continue play after account controls are active. The complaint should focus on the unresolved account-control request.
For safer play and account-control context, use responsible gambling. That route should remain separate from promotion and payment escalation.
Dispute Resolution After Customer Service
Dispute Resolution belongs after customer service review when the support route has not resolved the issue. It should not replace the first support contact.
Use a factual structure: what happened, when it happened, which support route was used, what evidence is attached and what outcome still needs review.
Do not invent a UK regulator, ADR body or legal route if the official process does not show one. For policy context, use dispute resolution, but keep the complaint grounded in the customer service route.
Complaint Follow-Up and Privacy Checks
Complaint follow-up should keep the same case history together. Use dates, support route, response summary and current unresolved point instead of resending the same message without context.
Privacy matters during complaints. A clear complaint does not require passwords, card security codes, recovery links or unrelated private documents.
| Follow-Up Status | Next Step | Privacy Check |
|---|---|---|
| No support reply yet | Wait for the support route to respond before escalating | Keep the original support message and timestamp. |
| Reply does not solve issue | Explain which point remains unresolved | Attach only relevant screenshots or IDs. |
| Payment still pending | Provide transaction ID, amount, method and status | Do not send card security codes. |
| Verification still rejected | Provide request type and rejection message | Use secure account route for requested files. |
| Bonus still disputed | Provide promotion name and account bonus status | Do not claim guaranteed approval. |
| Account-control issue continues | Escalate the account-control request calmly | Do not ask to bypass active restrictions. |
FAQ
When Should I File A Complaint?
File a complaint after the normal support route has not resolved the issue. First contact support, save the response and then explain what remains unresolved.
What Evidence Should I Include?
Include account email, issue type, date, current status, screenshot and specific IDs where available. For payments, include transaction ID, amount and method if shown.
Can I Complain About Payments?
Yes. Payment complaints should include deposit or withdrawal status, method, amount, date and transaction ID if available. Do not claim a guaranteed refund or instant payout.
Can I Complain About Verification?
Yes. Include the verification request type, visible status, rejection message if any and previous support response. Do not ask support to bypass verification.
Can I Complain About Bonuses?
Yes. Include the promotion name, bonus status, code if relevant and the rule or account result being disputed. Support review does not guarantee that a bonus will be added.
Is This A UK Regulator Complaint?
No. This British English page is a customer-service and dispute-resolution guide. It does not create a UK regulator, UKGC or ADR route unless the official process shows one.
Who Handles Dispute Resolution?
Dispute resolution follows the customer service process shown on the site. Use the support route first, then escalate the unresolved case with evidence and previous support details.