Disputes

Dispute records: what the desk looks for, in the public logs

The desk's filter 3 is dispute record. The desk looks for a public dispute log or a regulator-published complaint tally. The page below walks through what the desk looks for, what the desk finds, and what the desk writes about.

Play now Compare options

Disputes

Dispute records: what the desk looks for, in the public logs, and what the desk writes about

The desk's filter 3 is dispute record. The desk looks for a public dispute log or a regulator-published complaint tally. A platform with no disputes is suspicious; a platform with a resolved dispute ledger is more interesting. The page below walks through what the desk looks for, what the desk finds, and what the desk writes about.

What the desk looks for

The desk looks for three things in a public dispute log: a volume of disputes that is not suspiciously low, a resolution rate that is published, and a regulator-published complaint tally that matches the platform's own numbers. The desk reads the log, not the marketing copy.

What the desk found on the mrbahis platform

The platform publishes a dispute log on its help page. The desk read the log for the previous 12 months. The log shows 41 disputes, 38 resolved inside the published window, 3 escalated to the regulator and resolved. The desk treats the regulator escalation as a positive signal.

What the desk found on the other platforms

One platform has a public log with a low volume. The low volume is not, on its own, a red flag: a small platform has fewer disputes: but the desk treats the absence of a published resolution rate as a transparency issue. The desk writes about the absence on the platform's review page.

What the desk is honest about

A dispute log is a record of past events, not a guarantee of future behaviour. The desk treats a platform's dispute log as one signal among five, not as the only signal. The five-filter checklist is on the reviews page.

What the limit is

The desk's reading of a dispute log is qualitative, not quantitative. The desk records what the platform publishes and writes about the patterns the desk sees. A reader who needs a quantitative analysis should consult a regulator or a professional investigator.

Ready to compare options?

The desk keeps the same five filters on every review.

Get Started Compare Options

Reader follow-up

A reader's dispute-records follow-up, in plain language

The reader treats a platform's dispute log as a record of past events, not a guarantee of future behaviour. The log is one signal among five, not the only signal. The five-filter checklist is on the reviews page.

The reader does not assume a low volume of disputes is a positive signal. A small platform has fewer disputes; a large platform has more. The reader compares the volume to the platform's size, not in absolute terms.

The reader does not assume a high volume of disputes is a negative signal. A high volume can mean a transparent platform that publishes its disputes, or a problematic platform that generates them. The reader reads the resolution rate, not the volume alone.

The reader does not assume a regulator-published complaint tally is a complete picture. The tally is the count of complaints that were escalated to the regulator. A platform that resolves disputes before the regulator does not appear in the tally.

The reader treats a regulator escalation as a positive signal. A platform that uses the regulator, not against it, is a platform that is comfortable with external oversight. The desk treats regulator escalations as a positive signal in the filter 3 grading.

The reader does not pay for a dispute-records "service". A service that promises to resolve a dispute for a fee is a marketing channel, not a regulator. The reader uses the platform's dispute process and the regulator's complaint process, not a third-party service.

The reader reads the desk's update notes. The desk publishes an update note when the dispute data changes. The reader reads the notes at the start of every month. The reader does not assume a previous filter 3 result is still current.

Desk follow-up

A reader's dispute-records follow-up, in three steps

The reader treats a platform's dispute log as a record of past events, not a guarantee of future behaviour. The log is one signal among five, not the only signal.

The reader treats a regulator escalation as a positive signal. A platform that uses the regulator, not against it, is a platform that is comfortable with external oversight.

Reader glossary

A dispute-records glossary, in plain language

Dispute: a disagreement between the reader and the platform.

Dispute log: a public record of disputes published on the platform help page.

Resolution rate: the percentage of disputes resolved inside the published window.

Regulator escalation: a dispute escalated to the public authority.

Volume: the count of disputes in the log; compare to the platform size, not in absolute terms.

Window: the time period within which the platform commits to resolve a dispute.

Filter: one of the desk five working checklist items; filter 3 is dispute record.

Transparency: the openness of the platform records.

Reader playbook

A reader's dispute-records playbook, in plain language

The first dispute log the reader reads is the platform's own log. The log is on the platform's help page. The reader reads the log for the previous 12 months. The reader notes the volume, the resolution rate, and any regulator escalations.

The middle dispute logs the reader reads are the regulator's logs. The regulator's logs are the public record. The reader reads the regulator's logs for the same 12 months. The reader compares the platform's log to the regulator's log.

The last dispute log the reader reads is the desk's review. The desk's review is on the reviews page. The reader reads the desk's filter 3 grading. The reader combines the three sources.

The reader does not pay for a dispute-records "service". A service that promises a dispute resolution is a marketing channel, not a regulator. The reader uses the platform's dispute process and the regulator's complaint process, not a third-party service.

Where to read more

A reader who wants to read more about the safety desk's reviews can read the reviews page. The reviews page covers the five filters, in order. The reader combines the dispute-records page with the filter 3 (dispute record) data.

A reader who wants to read more about the platform's dispute process can read the customer-care page. The customer-care page covers the in-app chat, the email, the phone, and the regulator.

Reader FAQ

A reader's dispute-records FAQ

What is a dispute? A dispute is a disagreement between the reader and the platform. A dispute can be about a stuck withdrawal, a KYC re-submission, or a bonus term.

Where is the platform's dispute log? The log is published on the platform's help page. The reader reads the log, not the marketing copy.

What is a resolution rate? A resolution rate is the percentage of disputes resolved inside the published window. A high resolution rate is a positive signal.

What is a regulator escalation? A regulator escalation is a dispute that is escalated to the public authority. The desk treats regulator escalations as a positive signal.

What is a low volume of disputes? A low volume of disputes is not, on its own, a positive signal. A small platform has fewer disputes; a large platform has more. The reader compares the volume to the platform's size.

What is a high volume of disputes? A high volume of disputes is not, on its own, a negative signal. A high volume can mean a transparent platform that publishes its disputes.

What is the published window? The published window is the time the platform commits to resolve a dispute. A pattern of overruns is a defect; a single overrun is a variance.

What is the difference between filter 3 and the customer-care page? Filter 3 is the desk's working checklist item for dispute record. The customer-care page is the platform's support playbook. The reader combines the two.