Skip to main content

Player account management, the core every other system reads

Profile, two-factor login, phone verification, document upload, session history and connected accounts on one record. The wallet and the compliance layer both read it before they act.

A player record showing account status, compliance tier, verification and two-factor state, above the tabs where identity documents are reviewed step by step.

What a player does without contacting support

Every action here writes to the same audit trail as a staff action, so self-service never means an unrecorded change.

  • Profile and two-factor login

    Details, password and two-factor authentication, changed by the player rather than by an agent on their behalf.

  • Phone and document verification

    Phone verification and document upload run from the account area, with the current state visible at every step.

  • Session history

    A player can see their own sessions, which is usually the fastest answer to a question about unfamiliar activity.

  • Connected accounts

    The accounts a player has linked, listed in one place and removable without a support ticket.

The tier decides what an account may do

Every player sits at a tier from T0 to T4. The tier decides how much they can deposit, whether they can withdraw, and which checks must clear before either changes. The wallet consults it before it moves any money.

  • Thresholds are configured per brand

    A market with strict affordability expectations does not inherit the settings of one without.

  • Decided in the account core, in real time

    Eligibility is answered by the platform rather than through a support ticket.

  • Every decision keeps its reason

    The operation, the amount, the outcome, the tier and the policy behind it are all recorded.

The decisions tab of a player record, filtered by operation and outcome, showing a deposit decision with its amount, its result, the compliance tier and the policy that allowed it.

Player safety states live in the account, not in a marketing tool

Because they are states on the account itself, every other part of the platform has to respect them.

Account states

  • Account freeze

    A frozen account cannot quietly take a deposit.

  • Account suspension

  • Account ban

  • Self-exclusion

    A self-excluded player cannot be brought back by a campaign.

Limits and checks

  • Deposit limits

  • Session limits

  • Tiered checks before money moves

  • Reviewed payouts, decided by a person

    Paying out is the irreversible action in a casino, so it is deliberately not automatic.

Read our responsible gambling position

Everything else on the platform reads this record

The wallet reads it before money moves

Deposit and withdrawal eligibility is answered by the account's compliance standing, not by a separate rulebook kept somewhere else.

A portrait crop of the audit trail table showing the time, event and participants columns for a run of recorded events.

The audit trail records every change

A self-service change writes the same kind of event as a staff action, with the actor, the role, the location and the device attached.

The player screen updates as it happens

Balance changes, bonus progress and verification outcomes reach the player without a refresh, which removes the most common reason anyone writes in at all.

Screenshots are captures of the demo tenants MaxBet and LuckyOni. Every figure on screen is demo data.

Questions about the account core

Every player sits at a tier from T0 to T4, and the tier decides what they are allowed to do: how much they can deposit, whether they can withdraw, and which checks must clear before either changes.

Thresholds are configured per brand, so a market with strict affordability expectations does not inherit the settings of one without. The decision happens in the account core in real time rather than through a support ticket, and the wallet consults the tier before it moves any money.

Account freeze, suspension, ban and self-exclusion, built into the account core rather than added as a marketing setting. Because they are states on the account itself, every other part of the platform has to respect them: a self-excluded player cannot be reactivated by a campaign, and a frozen account cannot quietly take a deposit.

Deposit and session limits sit alongside them, as do the tiered checks that run before money moves. The controls are ordinary. Where they live is the part that decides whether they hold.

What this page covers in the feature matrix

Each capability below is a row in the platform index, where its tier sits beside the method and the date behind it. Read the full feature matrix.

Player self-service

Profile, two factor login, phone verification, document upload, session history and connected accounts, all handled by the player without contacting support.

Real-time player updates

Deposits, bonuses and account events appear on the player's screen the moment they happen, with no refresh and no support ticket.

Book a platform demo and open a real player record

Thirty minutes in the running back office, working the kind of record your own operation would work.

We reply within one working day.