Dormant Account Reactivation Compliance
A player account dormant for a year or more comes back into an operating environment that's likely changed — risk models, sanctions lists, KYC document requirements and the player's own financial circumstances can all have shifted since the account was last active, but a reactivation flow that simply unlocks the old account treats it as though none of that happened. That's a genuine AML gap: current controls exist to catch current risk, and applying them for the first time only at onboarding, never again on an account that goes quiet and comes back, leaves a blind spot regulators specifically look for during license reviews.
STARTING PRICE
From €299
Standard tier · Multi-step workflow with AI extraction/decisioning and 2-3 integrations.
Get a quote →Saves roughly 4-6 hrs/week of manual dormant-account review, plus stronger evidence of continuous AML control coverage.
How the automation works
We define dormancy thresholds by account risk tier and trigger a proportionate re-check when a dormant account reactivates, rather than either a full re-onboarding for every returning player or no check at all. A low-risk, short-dormancy account might only need a lightweight sanctions and PEP rescreen; a long-dormant or higher-risk account triggers a fuller re-KYC, including confirming the identity document is still current and re-running AML risk scoring against present-day thresholds. The player experiences this as a short, proportionate step during reactivation rather than a full onboarding repeat, and every reactivation check and its outcome is logged as evidence the operator's controls apply continuously, not just once at sign-up.
Process flow
- 01
Dormant account attempts reactivation trigger
A player returns to an account that has crossed the defined dormancy threshold and attempts to log in, deposit or play.
- 02
Classify dormancy risk tier ai
The account's dormancy length and prior risk profile determine which reactivation check tier applies — a short dormancy on a low-risk account differs from a long dormancy or a previously flagged account.
- 03
Rescreen against current lists and rules integration
The account is rechecked against current sanctions and PEP lists and current AML risk thresholds, which may have changed materially since the account went dormant.
- 04
Confirm document and profile currency ai
Identity document expiry and key profile data are checked for currency, prompting re-verification where needed before full reactivation.
- 05
Route unresolved flags to compliance output
Any rescreen hit or unresolved verification gap routes to a compliance analyst for a decision before the account is fully reactivated — a stale profile is never waved through automatically.
- 06
Log reactivation check outcome output
The dormancy tier, checks run and outcome are logged, evidencing that controls were reapplied at reactivation rather than only at original onboarding.
Inputs
- Account activity and dormancy status
- Current sanctions and PEP list data
- Identity document expiry status
- Historical account risk profile
Outputs
- Dormancy risk tier classification
- Rescreen and re-verification results
- Compliance analyst decisions on flagged reactivations
- Reactivation compliance log
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- Treating reactivation as a simple unlock, with no recheck against current sanctions lists or AML thresholds, assumes nothing material changed while the account sat idle — for a long dormancy that assumption is often wrong, and it's exactly the gap license reviews look for.
- Applying full re-onboarding to every reactivating account regardless of dormancy length or original risk tier creates unnecessary friction for a player who was inactive for a few months on a low-risk account — the check needs to scale with actual dormancy and risk, not apply uniformly.
- Sanctions and PEP status can change while an account is dormant even if the player's own behavior hasn't — a rescreen against current lists is the control here, not a review of the player's historical play pattern, which tells you nothing about a new sanctions listing.
- A dormancy threshold set the same for every risk tier misses that a previously flagged or higher-risk account reactivating after even a short absence deserves more scrutiny than a long-dormant but always-clean low-risk account — tier the threshold by risk, not just elapsed time.
Frequently asked questions
Does every returning player have to go through full re-onboarding?
No — the check scales with dormancy length and the account's risk tier, so a low-risk account dormant a few months gets a lightweight rescreen, while a long-dormant or previously flagged account gets a fuller re-KYC check.
What specifically gets rechecked on reactivation?
Current sanctions and PEP list status, identity document currency, and current AML risk thresholds — all of which can have changed materially since the account went dormant, even if nothing about the player's history looks different.
Does a flag during reactivation block the player automatically?
No — any rescreen hit or unresolved verification gap goes to a compliance analyst for a decision before the account fully reactivates, rather than an automatic block or an automatic pass.
How is dormancy length defined?
It's configurable to the operator's own AML programme and risk tiering, since what counts as meaningful dormancy differs by player risk profile rather than being a single fixed period for every account.