Bonuses
Configure incentives. Reward type, wagering terms, expiry and per player limits are set as rules the engine enforces.Length
Recorded in the back office
Audit: trace every platform event
Trace every platform event. Administrative actions, security events and system configuration changes in one stream.
Audit
- Length
- Sound needed
- No, it is silent screen capture
- Form to watch
- None
Audit
Trace every platform event. Administrative actions, security events and system configuration changes in one stream.
What to keep your eye on
- Player actions, staff actions and system actions share one stream and one clock.
- Every entry carries who did it, in what role, from where and on what device.
- A withdrawal appears as a sequence of separate events rather than a single outcome.
Readable without sound
The recording in words
What to watch for
- Player actions, staff actions and system actions share one stream and one clock.
- Every entry carries who did it, in what role, from where and on what device.
- A withdrawal appears as a sequence of separate events rather than a single outcome.
The audit trail is one list, in time order, covering administrative actions, security events and system configuration changes together. A withdrawal does not appear as a result. It appears as the sequence that produced it: requested, approved, processing, payout verified, sent. Each of those is its own row, with its own timestamp, so the gap between any two of them is measurable.
Every row names the actor and the role behind it, and separates a staff member from the player from a system process such as the payments integration. Alongside that sits the country and city, the network address and the browser and operating system. Filters narrow the stream by type or by actor. This is the record that regulator evidence packs are built from, which is why it is append only and why nothing on the platform writes to it selectively.
The still frame
The poster shows the Audit Trail screen: a time ordered list of withdrawal, deposit, login and authentication events, each row carrying a timestamp, an event type, the actor and role, the country and city, the network address and the browser and operating system.
Demo data
Every figure on screen belongs to a demonstration environment. Player counts, balances and jackpot totals are test values, not results from a trading casino.
The rest of the tour
Each module of the back office is recorded separately, so you can watch only the part you are being asked to judge.
Branding
Customise without code. Brand Studio builds the look from the brand's own colours and publishes it without a release.Length
Financials
Control wallets and transactions. Deposit activity, the currency everything settles in, and how a payment becomes a balance.Length
Games
Manage the catalogue. Studio visibility, lobby coverage and player facing collections, controlled from one screen.Length
Launch
Provision a casino. The recording follows a new brand from an empty environment to a working player lobby.Length
Onboarding
Verify identity at signup. The operator application runs through identity checks before a casino can be created.Length
Players
Manage the player lifecycle. Account state, compliance tier, verification status and the audit history of every check.Length
4:00 is the length of the whole tour, end to end.
Seen enough to ask a real question?
A walkthrough is a conversation about your brands, your markets and your payment rails, on the same back office you have just watched.