Перейти до основного вмісту

Responsible gaming

UCRM enforces RG features at two layers: (1) inbound webhooks from the casino platform mirror state into CRM, (2) CRM-side enforcement never messages a self-excluded player regardless of platform support — the capability_mock pattern.

Feature catalogue​

self_exclusion          - permanent or time-bound block
cooldown_period         - cooling-off after triggering event
deposit_limit_daily     - cap per-day deposit
deposit_limit_weekly
deposit_limit_monthly
loss_limit_daily        - cap per-day net losses
loss_limit_weekly
loss_limit_monthly
session_limit_minutes   - max session duration
reality_check           - periodic in-session reminder
session_cooldown        - mandatory pause between sessions
affordability_check     - KYC-bound spend cap (UK style)

Tenant config picks which features are enabled (license defaults give you a starting point); adapter declares which it supports on the platform side.

State storage​

players.responsible_gaming_state (JSONB) — heterogeneous limits + self-exclusion details:

{
  "self_excluded": {
    "until": null,                    // permanent
    "set_at": "2026-05-08T...",
    "reason": "responsible_gaming_request",
    "actor_kind": "admin"
  },
  "limits": {
    "deposit_limit_daily": { "amount_subunit": 10000, "currency": "EUR", "set_at": "..." },
    "session_limit_minutes": { "value": 60, "set_at": "..." }
  },
  "session": { "started_at": null, "minutes_used_today": 0 }
}

Plus mirror columns for fast lookup: players.rg_self_excluded (bool) + players.rg_self_excluded_until (timestamp or null).

Capability_mock — CRM-side enforcement​

The campaign-enqueue path filters self-excluded players directly in SQL:

WHERE deleted_at IS NULL
  AND (rg_self_excluded = false OR rg_self_excluded_until < now())
  AND ...

This filter applies regardless of whether the adapter supports self-exclusion. A self-excluded player is never messaged from CRM — even if the platform doesn't enforce on its side, even if the operator forgets to wire the webhook.

Same pattern for journey send_message + manual admin sends.

Platform webhook events​

POST /v1/adapters/:slug/webhooks/bonus-events (or future dedicated /rg-events endpoint) accepts:

  • self_exclusion.requested — player initiated self-exclusion on the platform
  • self_exclusion.set / self_exclusion.lifted / self_exclusion.expired
  • deposit_limit.set / deposit_limit.reached / deposit_limit.reset
  • session_limit.warning / session_limit.exceeded
  • reality_check.triggered / reality_check.acknowledged
  • cooldown.entered

State-sync mutates responsible_gaming_state JSONB + the mirror columns where applicable.

License-driven defaults​

Operator picks license → UCRM auto-suggests RG features:

  • Nevis — self_exclusion only
  • Curaçao — + deposit_limit_daily + deposit_limit_monthly
  • MGA — full RG suite (limits + reality checks)
  • UK GamCom — MGA + affordability_check + session_cooldown
  • CZ — MGA + session_cooldown (5-min mandatory pause after session)

These are recommendations. Operator can override anything per tenant — UCRM doesn't enforce regulatory compliance (your compliance team's job).