Separate the event from the conclusion
Start with a factual chronology: what was requested, when, what the account displayed and what the operator replied. “The request remains pending after this date” is an observable statement. The reason for that delay may still be unknown.
Preserve the relevant material
- The exact domain and account case reference.
- The terms relevant to the issue, with their date or saved version.
- Request and response timestamps with the time zone.
- Payment amount, asset and network where relevant.
- A public transaction identifier if one exists.
- Copies of support responses.
Keep identity documents, passwords and wallet secrets out of public submissions. Redact personal information before sharing screenshots beyond an authenticated complaint channel.
Use the appropriate route
Follow the operator’s published complaints procedure first where appropriate, keeping the case reference. An applicable regulator or dispute body may have its own remit and eligibility requirements. Verify that route using the relevant official source; a regulator in one jurisdiction is not automatically responsible for every website.
Assess public complaint patterns carefully
A raw number of complaints is difficult to interpret without context such as activity level, dates, issue types and outcomes. Equally, the absence of visible complaints is not proof that a business has no problems. Reviews should distinguish an allegation, an operator response and a documented resolution.
What Casinodur can handle
Our contact form accepts evidence that a published statement needs correction. Casinodur is not a regulator, dispute-resolution body or fund-recovery service. Sending us a report does not open an official operator complaint or guarantee recovery.
For related research methods, read licence checking and critical review reading.