Complaints and Dispute Handling | Maticslot

This page is part of Maticslot’s wallet-based crypto casino model. See Maticslot: Wallet-Based Crypto Casino.

This page describes complaint and dispute handling as a process category. It outlines common dispute types, typical lifecycle stages, and evidence categories that may be relevant. It does not imply that a complaint will be accepted, escalated, or resolved in a particular way.

What can be treated as a dispute (common categories)

Gameplay disputes: session interruptions, displayed outcomes, or game state confusion.
Payments disputes: deposit/withdrawal status, method mismatch, or network selection errors.
Promotions disputes: bonus state, eligibility, or conversion conditions.
Account access disputes: locked sessions or identity mismatch states.

Typical dispute lifecycle (conceptual)

Open: the user submits a complaint with a description and references.
Review: the platform reviews available records and checks for rule alignment.
Response: a response is produced, which may include requests for additional information.
Close: the dispute is marked closed in the ticket system, sometimes with an internal note.

This is a typical workflow pattern. It does not represent a assurances of how any specific case will proceed.

Evidence users commonly provide (categories)

Approximate timestamps and time zones.
Game/provider identifiers where displayed.
Order or ticket identifiers where provided.
On-chain transaction hashes for crypto transfers, where relevant.
Screenshots of UI states or error messages.

Providing evidence categories can reduce ambiguity, but it does not imply a particular decision.

Record and timeline concepts

Platforms commonly rely on records such as event logs, payment records, provider session identifiers, and message history. The existence of records does not imply that all disputes can be fully reconstructed or that records are complete.

Boundaries and third parties

Some disputes involve third-party systems (for example, payment processors, blockchain networks, or game providers). Responsibility and available data may differ depending on which system generated the relevant event. See operator vs platform boundary for interpretation framing.