Enhanced due diligence thresholds are among the most consequential settings an iGaming operator controls, yet many platforms still rely on defaults inherited from early licensing applications rather than data drawn from actual player behaviour. Incidents reviewed across multiple regulated markets in 2024 and early 2025 show a consistent pattern: thresholds set too high miss genuine risk, while thresholds set too low create compliance backlogs that paradoxically weaken overall AML effectiveness.
Why Default Thresholds Become Liabilities Over Time
When an operator first applies for a licence, its EDD trigger points are often theoretical, based on guidance documents and peer benchmarks rather than real transactional data. That is unavoidable at launch. The problem arises when those same figures remain unchanged through years of product growth, new payment method adoption and shifting player demographics. Regulators in Malta, the United Kingdom and several Dutch-licensed markets have cited this drift in enforcement actions, noting that operators could not demonstrate a documented rationale for the thresholds in place at the time of an incident.
In one documented case from a mid-sized European operator, a single-transaction EDD trigger was set at a fixed euro amount that had made sense in 2021 but represented a far lower percentile of the active player base by 2024. The result was a monthly EDD queue running into the thousands, staffed by a compliance team sized for a fraction of that volume. Reviews became superficial, turnaround times ballooned and a cluster of genuinely suspicious accounts moved through the system with minimal scrutiny. The regulator's subsequent investigation focused not on the threshold itself but on the operator's failure to resource and review it proportionately.
Common Threshold Calibration Failures
- Static monetary triggers: Fixed deposit or withdrawal amounts that are never adjusted for inflation, product mix changes or evolving player value profiles.
- Single-variable rules: Thresholds built solely on transaction size, ignoring velocity, frequency, source-of-funds indicators or account tenure.
- Identical limits across risk tiers: Applying the same EDD point to a newly registered anonymous player and a verified, long-standing VIP creates proportionality problems in both directions.
- No documented review cadence: Thresholds that have no scheduled review date cannot be defended before a regulator as risk-based, regardless of how reasonable they once were.
What Operational Incidents Actually Reveal
Reviewing post-incident regulatory correspondence from operators across regulated European and Caribbean jurisdictions, several patterns emerge that are rarely discussed in public guidance.
First, the gap between trigger and review completion is as important as the trigger itself. An EDD trigger that fires at a sensible threshold but sits unreviewed for 14 days while a player continues to deposit is operationally equivalent to having no threshold at all. Regulators examine both the calibration and the workflow connected to it.
Second, crypto payment channels have repeatedly surfaced as a blind spot. Operators who defined their EDD thresholds in fiat equivalents sometimes found that rapid crypto price movements temporarily pushed transactions below trigger points, creating windows of reduced scrutiny. Incident reviews recommend either dynamic fiat-equivalent calculation at the moment of transaction or separate, lower nominal thresholds for crypto deposits.
Third, source-of-funds requests issued at EDD stage routinely suffer from poor timing logic. Asking for documentation after a player has already withdrawn eliminates most of the risk-mitigation value of the process. Threshold design must account for the practical point at which information can still be acted upon.
A Proportionate, Defensible Calibration Framework
Operators who have navigated regulatory scrutiny successfully share several structural practices worth adopting.
- Conduct a threshold review at least every six months, tie it to a documented risk assessment and record the rationale for any figure that is retained or changed.
- Build multi-variable triggers that combine deposit amount, velocity over 30 days, payment method risk rating and account age rather than relying on a single monetary figure.
- Segment EDD thresholds by player risk tier so that a newly registered player faces a tighter trigger than an established, source-of-wealth verified account.
- Model your compliance team's realistic review capacity and set thresholds that the team can actually process within regulatory turnaround expectations.
- For crypto channels, apply fiat conversion at the moment the transaction is assessed, not at deposit time, to account for price volatility.
The Operator's Practical Takeaway
EDD thresholds are living compliance instruments, not configuration entries to be set and forgotten. Regulators assess whether an operator can articulate why a given threshold exists, how it was derived and when it was last tested against actual transactional data. Operators who treat threshold calibration as an ongoing operational discipline, rather than a licensing formality, consistently demonstrate stronger outcomes both in regulatory reviews and in the quality of risk signals their compliance teams actually act upon.
At OnlineShine, our MLRO and compliance operations teams work with operators to audit existing EDD configurations, model threshold adjustments against live transaction data and build the documented review cadence that regulators expect to see. Calibration is not a one-time project; it is a continuous operational responsibility.
