Operations overview

The 91club24.com admin console is organised around four pillars: live sports and markets, the roll hierarchy (staff and clients), money and commission, and casino products with global settings. What follows is a concise reference for what each area covers, without leaving this page.

Sports & in-play

Live matches stream odds and market state in real time. Operators can follow match odds, bookmaker-style lines, session markets (fancy), and fall-of-wicket style specials as they are exposed on the match view. Completed events move into historical results so exposure and profit can be reconciled after the event.

In-play controls respect suspension, ball-running, and market status so that only valid bets are accepted. Finished-game views summarise outcomes for the same event IDs so reporting stays consistent across the stack.

Rolls & clients

The platform uses a clear chain: Sub Admin, Master, Super Master, Agent, and Client. Each roll has a reference code, limits, and permissions that flow down the tree. Client masters sit at the end of the chain and are where end-user exposure and balances are tracked.

  • Hierarchy and roll type drive who can see which events and ledgers.
  • Limits and coins are scoped per roll so risk stays bounded.
  • Changes to roles propagate through the same APIs as login and betting.

Cash, chips & commission

Cash and chip movements are recorded as credits and debits along the hierarchy. Commission may be calculated on a bet-by-bet or percentage basis depending on product rules, with separate treatment for match, session, and casino segments where relevant.

Len/den (give/receive) style views help operators reconcile what each party owes or is owed. All of this ties back to the same ledger tables that power statements and user balances, so the numbers you see in one screen should align with the same user’s history elsewhere.

Casino & settings

Casino-style products sit alongside sports: they may include turbo slots, in-out games, or card-style products depending on what is enabled. Product-level settings control visibility, limits, and integration with the same wallet and roll model as sports.

Global game settings and profile-level controls let administrators tune behaviour without changing code. Keeping these settings consistent with the rest of the stack avoids mismatches between what users see in the app and what the admin tools expect.