Classify the problem
Choose one primary category and state the disputed outcome precisely. Attach account and transaction references without exposing login credentials, full card details or identity document numbers.
This page is a decision worksheet built around a specific search task. It separates observable records, first-party wording and unresolved claims so the conclusion can be checked again after a material change.
Build a dated chronology
List the original event, each support contact, documents supplied, responses received and promised deadlines. Keep original files and send redacted copies through the verified channel.
Quote the applicable rule
Save the terms, promotion or game rule that applied when the event occurred. Explain how the observed decision matches or conflicts with that wording instead of relying on a later review.
Request a specific remedy
Ask for payment trace, corrected balance, written KYC decision, reopened account or final complaint response. A bounded request gives support and an external reviewer something testable.
Choose the right escalation
Verify the operator’s regulator and complaint process, then check whether ACMA, a bank, ReportCyber or another body has jurisdiction over the actual issue. Reporting does not guarantee recovery.
Review volume is not complaint proof
Public ratings can reveal themes, but only a documented account-level chronology can support a particular payment or policy conclusion.
Questions this page resolves
Should I post documents in a public review?
No. Keep sensitive evidence in the verified complaint channel and publish only redacted facts if needed.
Can ACMA resolve a payment dispute?
Check its current remit; legal compliance reporting and recovery of an individual balance are different processes.
What is a final response?
It is the operator’s documented position after its internal complaint steps, useful for any permitted external escalation.