Skip to content
iGamingX
Contact

Back office

In production

One console for every team.

159 console pages for finance, compliance, CRM, VIP, games and support, with two-⁠factor sign-⁠in required by default for sensitive roles, a hash-⁠chained audit log and a second sign-⁠off on sensitive flows such as withdrawals, refunds and adjustments, each with its own rule or threshold.

Talk to sales
The overview of the iGamingX console, with today's GGR, stakes, deposits and first deposits, and the queues waiting for the team, on sample data.

What it does

  • Every team, one place

    Overview, players, payments, compliance, promotions, marketing, games, the player site, settings and platform tools, in Spanish and English.

  • Two people where it matters

    A second person signs off sensitive flows, each with its own rule or threshold: withdrawals, refunds, adjustments, chargebacks, earned money, KYC, AML, self-⁠exclusion lifts, bet corrections, RTP, CRM publishing and legal texts.

  • A chained audit log

    Staff and system actions are written to an audit log chained with SHA-⁠256 and checked every hour, with an alert if the chain ever breaks.

  • Staff sign-in

    Two-⁠factor sign-⁠in with an authenticator app is required by default for administrators, finance, compliance and affiliate managers. By default, sessions last 12 hours and close after 60 idle minutes.

  • In pilot

    Roles and permissions

    Eight roles guard every page. A matrix of 50 permissions in 15 categories records each decision and is enforced per operator once it is switched on.

  • Platform tools

    Job queues you can pause and retry, an error log across API, console and player site, and a readiness page with the status of backups.

By the numbers

  • Console pages

    159

  • Console languages

    2

    Spanish, English

  • Staff roles

    8

Details

Built to be checked

Each page is guarded by role, and a page outside the access list answers 404. Personal data is revealed on request and every reveal is logged, and the activity of every API key can be read in the console.

Approvals that hold

The person who approves a withdrawal never sends it, and the database refuses the same person on both sides. API keys never approve. An approval is tied to the exact version the reviewer saw, so a change after the review needs a new one.

What is not there yet

Single sign-on for staff, with SAML or OIDC, is not available yet, and the AI usage page is still to come.

Related modules

Contact

Tell us what you are building.

Markets, brands, verticals. We show you the platform with your case in mind.

Talk to sales