Endida
Home Solutions Sectors About Insights Speak to a Specialist

Safer gambling & responsible gaming softwareSpot harm early.
Act in proportion.
Prove it worked.

Endida brings every marker of harm into one real-time player profile, shared with AML and fraud: monitoring from account opening, deciding the proportionate response in under 100ms and keeping the evidenced audit trail your regulator expects.

Heads of Safer Gambling Player Protection leads RGOs and RG managers
Monitoring from account opening Automated action, human review Every interaction evidenced Multi-market · configured per licence
1 profile
Safer gambling first, with
AML and fraud context
Same day
Rules your team deploys,
no vendor change control
Every why
Each decision shows the rule,
version, inputs and outcome
<100ms
From marker to action at the
point of play, at peak volume

Every marker.
One response.

Continuous monitoring against each player's own behavioural baseline, acting the moment the pattern changes

The tools are in place.
The evidence often isn't.

Most operators already have limits, time-outs and self-exclusion. What regulators look at now is whether you spotted the harm in time, responded in proportion and can show it made a difference.

One player, five systems
Deposits, sessions, limit changes, contact history and source of funds all live in different systems. Analysts jump between them to piece one player together, and by the time they have, the moment to act has often passed.
Flat thresholds, noisy alerts
The same deposit means very different things for different players. Flat triggers flood the team with low-value alerts and still miss the player whose own pattern has changed.
Interactions you can't evidence
A message went out, a call was made. But what triggered it, why that response, and did the player's behaviour change? Inspectors will ask all three.
Strong indicators, slow action
Manual review queues and weekly batch reports leave days between the marker and the response. UK rules now expect timely, automated action where the indicators are strong.
Thresholds that keep moving
The vulnerability check threshold has dropped from £500 to £150, and financial risk assessments are arriving in stages. Each change should be a configuration decision, not another development ticket.
Protection versus friction
A single county court judgment shouldn't mean a blanket block. Weigh it alongside spend and behaviour and the response stays proportionate, such as an automated deposit limit while someone reviews the account. The player is protected, and the revenue isn't thrown away.
The business case · for the board
Keep good customers playing
Baseline-aware, proportionate responses replace blanket blocks, so recreational players aren't driven away by friction they didn't need.
Protect revenue that should stay
Scale without scaling the team
With the whole player on one screen, analysts stop assembling cases across five systems and spend their time on the conversations that matter.
More capacity, same headcount
Fewer vendors to run
Safer gambling, AML and fraud on one engine, one integration and one audit trail, with no per-event metering on-premise.
Lower cost to comply

Every marker of harm,
on one player profile.

Every player has their own behavioural baseline. No flat thresholds, no one-size-fits-all. Events from your platform, cashier and CRM are scored against that baseline continuously, from the first deposit. The markers below follow the UKGC indicators, the MGA Player Protection Directive and Gibraltar's draft Safer Gambling Code, and your team can tune every one of them.

Player events
Registrations
Deposits & withdrawals
Bets & game play
Sessions & devices
Limit & tool changes
Reality check responses
Customer contact
Any schema
Spend & deposits
Spikes against the player's baseline
In-session and accelerated deposits
Multiple payment methods
Failed or shrinking deposits
Credit card funding
Time & speed of play
Session length and frequency
Night-time and early-hours play
Speed of play
Reality checks ignored
Withdrawals
Reversed withdrawals, where permitted
Changing withdrawal patterns
Redeposit straight after a withdrawal
Tools & controls
Repeated limit increases
Limits removed or "no limit" requests
Limit set far above usual spend
Frequent time-outs
Attempts to get round a control
Customer contact
Rising contact and complaints
Bonus requests
Concerns raised by your agents
Product & account
Product switching, e.g. sportsbook to slots
Return from dormancy
Return after self-exclusion
VIP status and incentives
Affordability & vulnerability
Financial vulnerability checks
Financial risk assessments
Age-related risk, e.g. 18 to 24
Vulnerability flags
One decisioning layer
Safer gambling decisioning
Live
Continuous monitoringWatching
Behavioural baselineLearned
Player risk scoringWithin norm
Affordability & vulnerabilityStanding by
Strong-indicator actionsArmed
Marketing & bonus suppressionStanding by
Case & interaction logStanding by
Effectiveness reportingStanding by
Event feedPlayer 48213 · illustrative
    A continuous loop, not a one-off check
    Monitor
    Continuously, from account opening, across every channel and brand
    Score
    See where behaviour starts to change against the player's own baseline
    Act
    The appropriate response: automated on strong indicators, human where judgement matters
    Evidence
    Trigger, rationale, outcome and the rule version behind it
    Evaluate
    Was it effective? Did the change last for weeks? Tune the markers that matter

    Your safer gambling specialists own the markers, thresholds and actions. They test changes against historical data, run them in shadow mode and deploy the same day. Every version is kept, so you can show exactly why a player was treated the way they were on any date, and if something does go wrong, you can show it was isolated rather than systemic.

    One signal. Your rules.
    Every decision explained.

    Most safer gambling tools only look at gambling behaviour. Because the same profile also carries AML and fraud data, your team sees the full picture on one screen and can tell what is actually behind a change in behaviour. Two players with the same risk score might need completely different help, one around time on site and another around spend, so the response matches whatever is driving the risk. Safer gambling comes first, and your team makes the call.

    Context, not just a threshold
    A sudden deposit spike looks very different when you can also see source of funds, payment methods, linked accounts and past play. You need all of that context to choose the right response. Public record checks miss things like defaults and arrears, so tracking behaviour against a player's own baseline helps fill the gap.
    Fewer wrong interventions
    AML clearance isn't harm clearance
    Gibraltar's draft code makes the point directly: a wealthy player using their own money may rule out money laundering, but not harmful play. Shared signals, separate judgements, one record.
    No blind spot between teams
    Self-exclusion that holds
    Network analysis links the devices, cards and identifiers behind accounts, so a self-excluded player returning under a new account is caught by the same engine that finds fraud rings and mules.
    Circumvention detected
    At registration
    Caught before the first deposit
    Devices, payment cards, dates of birth and networks link a "new" player to an existing exclusion, even when the name and email change.
    Across brands
    One exclusion, every brand
    Links are checked across all your brands and labels, alongside national self-exclusion registers, so an exclusion holds wherever the player tries to return.
    Same engine
    The one that finds fraud rings
    Circumvention is caught by the same network analysis that exposes multi-accounting and mule networks, while genuine new players clear without extra friction.

    You can say why.
    Every time.

    If nobody can explain how a risk score was reached, you can't defend it to a player, a regulator or your own board. Here, rules and machine learning work side by side, and every decision spells out the factors behind it.

    Why this firedPlayer 48213 · illustrative
    RuleSG-07 · version 14 · approved by your team
    InputsWithdrew, then redeposited within minutes · 02:14 · product switch to slots
    AgainstThis player's own baseline: weekend football, evenings, rarely after midnight
    ModelRisk rising since day 19 · top contributing factors shown
    ActionMessage shown · marketing paused · case opened for review
    ContestReviewer can uphold, adjust or reverse, with the reason recorded
    Version historyv14 live · v13 retired, reason logged · v12 retired
    See why it fired
    The rule, its version, the inputs and the model's top contributing factors sit on the case, in plain language your team can repeat to a player.
    Decisions you can explain
    Change it the same day
    Your specialists draft a rule, test it against history, run it in shadow mode and deploy it, with no vendor change control. The expertise stays with your team, not on a supplier's roadmap.
    Your judgement, configured
    Built to be challenged
    Automated actions on strong indicators come with manual review and a route to contest, and every version is kept so you can show what was in force on any date.
    Ready for an inspector

    The record
    an inspector asks for.

    Each case answers the three questions regulators now ask safer gambling teams: what triggered it, why that response, and did it work. Nobody has to rebuild the story from emails and spreadsheets, and whoever picks up the phone has already seen the whole profile.

    01
    Why this player?
    The markers that fired, the score, and the rule version in force at that moment.
    02
    Why this response?
    What was automated, what a person reviewed, and the rationale recorded for both.
    03
    Did it work?
    How the player behaves before and after, tracked against their baseline over weeks rather than days. It sits on the case file, so you can show whether your interventions are actually working.
    Case SG-20481
    Player 48213 · UK licence · Opened 02:14 by rule
    Strong indicator
    Trigger
    Withdrew, then redeposited within minutes, at night
    Rule SG-07 · version 14 · score 88 / 100
    Context
    AMLLow
    FraudNone
    Vulnerability checkClear
    Actions and outcome
    1. Day 21AutoEarlier nudge on record: message and limit prompt
    2. 02:14AutoSafer gambling message shown in session
    3. 02:14AutoMarketing and new bonus offers suppressed
    4. 09:05AnalystAutomated action reviewed and confirmed
    5. 09:20AnalystCall with player; weekly deposit limit set
    6. Day 30OutcomeDeposits back within norm; night-time play stopped
    7. Day 38AnalystFollow-up review: change held, case closed
    Customer contest available · none raised Rationale recorded Exportable for inspection

    Safer gambling rules,
    by market.

    These are four of the rulebooks we see most often, with more below. The detail differs, but the direction is the same: monitor from the start, respond in proportion to the risk and show that what you did worked.

    UKGC · Great Britain
    Customer interaction rules require monitoring from account opening across seven indicators. Strong indicators must trigger timely automated action, with manual review and a way for customers to contest decisions, and marketing and new bonuses must stop. Financial vulnerability checks apply at £150 net deposits in 30 days, and gross deposit limits apply from 30 September 2026.
    Automate the strong cases. Evidence all of them.
    SR Code 3.4.3 · SR Code 3.4.4 · RTS 12. Financial risk assessments: stage one at £5,000 in 24 hours, start date TBC
    MGA · Malta
    The Player Protection Directive requires documented markers of harm, at minimum: deposit and wager amounts and frequency, multiple payment methods, reversed withdrawals, complaints and bonus requests, and use of responsible gaming tools. Policies must define when staff intervene, impose limits or exclude.
    Documented criteria, defined triggers.
    Directive 2 of 2018 · Art. 17 and 17A. Interaction records kept for at least two years
    Spillemyndigheden · Denmark
    Operators must already understand each player's playing patterns, keep written procedures and retain behaviour data and risk assessments for five years, with ROFUS checked at every login. Bill L 37 proposes a duty of care from 1 July 2027: monitor behaviour, act immediately on signs of problem gambling and evaluate the measures.
    Monitor, act immediately, evaluate.
    Online casino order BEK 682/2025 §§22, 25 · Bill L 37 (proposed). Lands alongside EU AMLR in July 2027
    GGC · Gibraltar
    The Gambling Act 2025 is now in force, while the 2012 codes stay in place until new ones take over. The draft Safer Gambling Code calls for a Head of Safer Gambling, ten markers of harm, real-time monitoring of late-night play, closer checks on credit card funding and regular reviews of your thresholds and alerts.
    Monitoring, not just tools.
    Draft Safer Gambling Code v1.0.2026, consultation closed October 2026
    Also configured forOne engine, one control set, configured per licence. National self-exclusion registers can connect by API.
    Isle of ManGSC NetherlandsKSA · CRUKS SwedenSpelinspektionen · Spelpaus GermanyGGL · OASIS IrelandGRAI OntarioAGCO · iGaming Ontario South AfricaProvincial licensing boards Your marketAsk us →
    Where we would focus first
    1Join the signals
    Feed deposits, sessions, tool changes and contact into one profile, across every brand.
    2Define strong indicators
    Write them down, set the thresholds and automate the response.
    3Evidence every interaction
    Trigger, rationale and outcome on the case, with the rule version behind it.
    4Measure what works
    Track whether interventions change behaviour, and tune the markers that do.
    Not sure where you stand? Our safer gambling gap analysis maps your monitoring, interactions and evidence against what your regulators expect, and ends in a prioritised plan. It is complimentary for qualifying operators and platforms.See how the gap analysis works →

    Alongside your platform,
    not instead of it.

    Limits, reality checks and blocks stay in your platform, where your players play. Endida adds the layer that decides when to use them and records why. If you already use a safer gambling scoring tool, keep it: its score simply becomes one more input. It all sits within our wider iGaming financial crime and compliance offering.

    Endida delivers
    Detection, decisioning and evidence
    Markers of harm, risk scoring, automated actions, case management and reporting. National self-exclusion schemes like GAMSTOP, ROFUS and CRUKS connect by API alongside your public record provider, keeping vulnerability checks in the same flow, with credit reference data ready for financial risk assessments when they go live. Deploy in public cloud, private cloud or on-premise, with local hosting for data residency and no per-event charges on-premise.
    Your player platform and cashier
    Where controls are enforced
    Deposit limits, reality checks, time-outs and blocks act at the point of play. Decisions arrive by API in under 100 milliseconds.
    Your CRM and marketing
    Where suppression takes effect
    Suppression signals for self-exclusion, time-outs and strong indicators flow to the systems that send offers, so marketing and bonuses stop when they should.
    Your safer gambling team
    Who owns the judgement
    Your specialists set the rules and have the conversations. If you need more analyst capacity or RGO advisory support, we can provide it, while the appointment and the accountability stay with you.

    Let's talk.

    We aim to be fast to value. Start by seeing it work on safer gambling scenarios, check it fits your stack with a proof of concept, then prove the outcome on your own data with a proof of value.

    A working demo
    One hour
    Live software on your screen, not slides. We walk through markers of harm, risk scoring, automated actions, case management and the audit trail using safer gambling scenarios.
    Request a demo →
    Proof of concept
    Fast to value
    A quick technical check against your stack: platform and cashier data flowing in by API, your markers configured and decisions returning to the point of play. Your engineers get their questions answered before you commit to anything bigger.
    Scope a proof of concept →
    Proof of value
    Six to eight weeks
    One use case, run on your live and historical data alongside your existing controls. We measure earlier detection, alert quality and the evidence each case produces.
    Plan a proof of value →
    Safer gambling gap analysis
    Online or on-site
    A structured review of where your monitoring, interaction and evidence fall short of what your regulators expect. See how the gap analysis works →
    Ask about a gap analysis →
    Contact us
    Tell us what you need and we will come back to you.
    Interested in
    Licences held
    Indicative pricingOn request
    Platform licence only
    You arrange the hosting, in your own cloud or on-premise.
    Licence and hosting
    Deployed and run by us on hyperscaler, dedicated IaaS or bare metal in the jurisdiction you need.
    Common questions

    Safer gambling software,
    answered.

    Does this replace our platform's responsible gambling tools?
    No. Deposit limits, reality checks, time-outs and blocks stay in your player platform and cashier, where they act at the point of play. Endida adds the layer that monitors markers of harm, decides when a control or an interaction is needed, and records why. Decisions reach your platform by API in under 100 milliseconds, and suppression signals reach your CRM so marketing and bonuses stop when they should.
    We already use a safer gambling scoring tool. Do we have to replace it?
    No. An existing risk score can be sent by API and read as one more input, alongside AML, fraud, linked-account and self-exclusion signals and vulnerability data. Your rules decide what happens next, and each decision records which inputs drove it. Some teams keep their scoring tool and add the wider context; others consolidate once they have compared the two side by side.
    Who sets the markers of harm and the thresholds?
    Your safer gambling team, in configuration. A rule or threshold is drafted, tested against your historical data, run in shadow mode with no player impact, then deployed the same day without a development release or a vendor change control. Every version is retained, so you can reconstruct the configuration in force on any date.
    How do automated actions fit with human judgement?
    Both are needed. UK rules expect strong indicators of harm to trigger timely automated action, with a manual review of how that automation worked for each player and a way for the player to contest it. Strong indicators can act in real time, for example a safer gambling message in session and suppression of marketing and new bonuses. A case then opens for your team to review and follow up.
    How are financial vulnerability checks and risk assessments handled?
    Public record data from your data provider connects by API, so checks run in the same flow as the rest of the profile. In the UK, a financial vulnerability check applies when net deposits exceed £150 in a rolling 30 days, unless a check or assessment was done in the previous 12 months, and the rationale for the action taken is recorded. Responses stay proportionate: a single lower-risk county court judgment is weighed alongside spend and behaviour rather than triggering a blanket block, and an automated deposit limit can hold while a person reviews. When the staged financial risk assessments start, the credit reference data they rely on connects the same way, and their thresholds are a configuration change, not a project.
    Why combine safer gambling with AML and fraud?
    Because the context changes the right response. A deposit spike reads differently when you can see source of funds, payment instruments, linked accounts and fraud signals on the same profile. The judgements stay separate: as Gibraltar's draft code points out, ruling out money laundering does not rule out harmful play. One profile and one audit trail means no blind spot between teams.
    We hold licences in several markets. Does that work?
    Yes. Rulesets, markers and thresholds configure to each regime, including UKGC customer interaction and financial vulnerability requirements, the MGA Player Protection Directive, the Danish rules and proposed duty of care, and Gibraltar's draft Safer Gambling Code, as well as other regimes such as the Isle of Man, the Netherlands, Sweden, Germany, Ireland and Ontario. You run one control set, configured per licence, rather than a separate stack for each.
    What does a proportionate response look like?
    It follows what is driving the score. A pattern driven by time on site points to a time-out or session reminders; one driven by spend points to a deposit limit. Where a player keeps raising and lowering their limits, a longer cooling-off before increases take effect can help them stick to the limit they chose. And a limit set well above someone's normal spending is treated as a marker in its own right, because it offers no real protection. Your rules decide the response, and your platform applies it.
    Can you provide our RGO or Head of Safer Gambling?
    We provide operational capability, not the appointment. That can mean analyst capacity for monitoring and interactions, and advisory support for your RGO or Head of Safer Gambling. The regulatory appointment and the accountability stay with the operator, with the contractual arrangements and oversight set up accordingly.
    What about brand-new players?
    Every player has their own behavioural baseline from the first deposit. For a new player it starts with little history, so in the early weeks it is read alongside how similar players typically behave, as well as the markers of harm and your rules. It sharpens with every session.
    How do we show a regulator that it is working?
    By measuring outcomes, not activity. An interaction only counts if it changed something, so each case tracks behaviour against the player's baseline before and after, over weeks rather than days, and records whether any limit set was meaningful relative to their usual spend. Every case carries the trigger, the actions, the rationale and the outcome, with the rule version behind each decision. Reporting shows interaction volumes and outcomes over time, and what you learn feeds back into the markers and rules. That supports the UK expectation to evaluate your approach and benchmark interaction volumes, and the periodic review of markers and thresholds in Gibraltar's draft code.
    What are markers of harm?
    Markers of harm are signals in a customer's account and behaviour that suggest they may be experiencing, or at risk of, gambling harm. In Great Britain, the UKGC customer interaction rules (SR Code 3.4.3) group them into customer spend, patterns of spend, time spent gambling, gambling behaviour indicators, customer-led contact, use of gambling management tools and account indicators. Malta's Player Protection Directive and Gibraltar's draft Safer Gambling Code set out their own markers, and each operator documents the markers and thresholds it uses.
    What is a financial vulnerability check?
    In Great Britain, a financial vulnerability check looks at publicly available information, such as county court judgments and insolvency records, to identify customers who may be financially vulnerable. It applies when a customer's net deposits exceed £150 in a rolling 30 days, unless a check or assessment has been done in the previous 12 months (SR Code 3.4.4). It is separate from the staged financial risk assessments, which use credit reference data.