QuinnBet fined £609,104 for AML and safer-gambling failures

What happened

The UK Gambling Commission has settled a compliance review into QuinnBet (Gibraltar) Limited’s remote gambling licence. The operator will pay £609,104, made up of a £193,118 disgorgement payment plus contributions towards the Commission’s investigation costs. The funds go to the UK government’s Consolidated Fund. The review covered the period from March 2023 to August 2025.

On social responsibility, the Commission found QuinnBet ran a manual process that let customers aged 18 to 24 spend over their deposit limits. One customer placed roughly 4,800 bets in a single day and 7,000 the following day without this being identified or flagged. A separate customer staked over £215,000 in one day, including multiple wagers above £5,000, and the pattern was not picked up until a report was produced the day after. The operator also failed to ensure that all customers meeting the relevant threshold underwent a light-touch financial vulnerability check.

On anti-money laundering (AML) controls, the Commission found insufficient checks on disproportionate spending. One customer had provided payslips showing monthly earnings of around £2,000 yet was able to deposit and lose £9,000 in four days. The Commission also found deposits accepted without established source of funds documentation, and delayed submission of suspicious activity reports (SARs).

Why it matters

The £215,000 single-day stake sitting unflagged until the next day’s report points to a detection lag, not just a missing rule. A threshold breach that only surfaces in a retrospective report has already let the harm happen before anyone acts on it. That gap between an event occurring and a control noticing it is the pattern worth watching here, and it recurs across the Commission’s case, from the 18 to 24 age group deposit issue to the 4,800 and 7,000 bet days.

The payslip example is the sharpest AML point in the file. A declared income of about £2,000 a month against a £9,000 loss in four days is not a subtle mismatch, it is the kind of gap a source of funds check exists to catch before the money moves, not after. Pairing that finding with delayed SAR submissions suggests the same underlying issue: information the operator held was not converted into a timely control action.

Practitioner angle

Gambling firms and other high-cash-flow, high-velocity sectors should treat this case as a prompt to check three things.

• Source of funds triggers: confirm your policy sets a clear deposit or loss threshold relative to declared income that forces a document check before further funds are accepted, not after a pattern review flags it.
• Same-day escalation, not next-day reporting: if a customer’s spend or bet frequency crosses a defined threshold intraday, the alert needs to reach a human who can act that day. A report generated the following morning is a record, not a control.
• Behavioral pattern detection thresholds: recalibrate monitoring for volume anomalies (bet counts running into the thousands in a day) as well as value anomalies, since the Commission’s findings show both slipped through.

The single most important step is to test whether your own intraday alerting can catch a stake or deposit spike before the next reporting cycle runs, because that is the exact gap this case turned on.