Back to Blog Listing

The £150 affordability trigger is a data-integration problem

The £150 affordability trigger is a data-integration problem
Jakub Pietroszek Jul 4, 2026 4 min read

Written by: Jakub Pietroszek, Partnership Manager, Digital Colliers

The £150 threshold sounds small until you do the math against your actual player base. Net deposits, rolling 30 days, per customer, across every payment method you accept. If your compliance team is three people and you've got six figures of monthly actives, you're not doing this by hand. You're doing it in software, or you're missing it.

The math nobody wants to run

UK affordability checks trigger at £150 net deposits per rolling 30 days. That's the number from the Gambling Commission, and it's been the reference point since the RCI guidance came into force in August 2022 and was expanded again in 2024.

Here's what that looks like operationally. Every deposit event needs to be net of withdrawals in the window. The window is rolling, not calendar, so a player who deposits £40 on the 3rd, £60 on the 12th, £30 on the 20th, and £25 on the 29th crosses the line on the 29th and you owe them an interaction. If your data warehouse refreshes overnight and your ops team eyeballs a dashboard the next morning, you're already late.

Multiply that by every active player, every payment rail, every currency conversion, every chargeback reversal, and you can see why roughly one in four UK-licensed operators fails to achieve a satisfactory AML rating on first assessment. It's not that they don't care. It's that the pipes don't connect.

Why manual review breaks down

Compliance teams at mid-size operators tend to look similar: a head of compliance, two or three analysts, maybe a KYC specialist, plus outsourced review capacity for surges. Kindred Group publicly reported a £14M compliance-team cost in 2023, and Kindred is a large operator with global scope. If that's the top of the market, a mid-tier UK-only book is not out-hiring the problem.

Manual review breaks down in three specific places:

  • Reconciliation lag. Deposits sit in the PSP system. Withdrawals sit in the wallet. Chargebacks sit in a third feed. Getting them to agree on "net" in real time is where the wheels come off.
  • Trigger detection. A rolling 30-day window means the trigger can fire on any day, for any player. You can't batch this once a week.
  • Evidence trail. When the Commission asks why you did or didn't interact with a player, "our analyst reviewed it" is not the answer they want. They want the rule, the data, the timestamp, and the action.

The penalty side of that equation is not small. Serious AML breaches in UK iGaming can reach up to 15% of gross gaming yield. That's the number a CFO cares about.

The data joins that actually matter

If you're going to automate the £150 trigger properly, you're joining at least four sources in near-real-time:

  1. Deposits from each PSP, normalised to GBP, timestamped to the second.
  2. Withdrawals, including pending and reversed, from the wallet.
  3. Player identity from KYC, so you're aggregating across accounts where the same person has multiple.
  4. Historical interaction records, so you know what's already been sent and when.

The hard part isn't any single join. It's making them all agree on "who this player is" and "what net deposits mean right now." Operators who ship this cleanly tend to have a customer data layer that treats the player, not the account, as the primary key.

What a passing operator actually looks like

The pattern I keep seeing at operators who sail through assessment isn't exotic tooling. It's boring plumbing done well.

They've got an event stream where every deposit and withdrawal lands within seconds. They've got a rules engine that watches the stream and fires when a player crosses £150 net in the window. The interaction gets queued, assigned, and timestamped automatically. The evidence is captured as a byproduct of the workflow, not reconstructed later.

And critically, the rule is versioned. When the threshold changes, or when the Commission clarifies a definition, they change one config value and the whole system moves. Operators still running SQL by hand for the monthly audit are the ones getting left behind, and they're the ones showing up in the one-in-four figure.

The £150 number is not the hard part. The pipes underneath it are.

Related Posts