The back office both sides work in.
Operators and providers sign in to the same back office, each with their own view. Requests, rules and records move between them as threads with reference numbers, and every thread sits next to the figures it is about.
Dashboard. Rounds, bets, wins, RTP and players for any period, provider, brand or game.
A dispute pinned to three hours. The operator questions part of an invoice, the provider answers with evidence, and the platform team is brought in, all in one thread.
A contract rule waiting for approval. The provider proposes how promo rounds count and the monthly spin-value limit. The operator approves or rejects it before it reaches an invoice.
Compliance at a glance. Certificates expiring in 30 or 90 days, expired ones and RTP deviations, with a list of what needs attention.
A big win, verified by the studio. The operator asks before releasing a withdrawal. The provider answers on the round itself, with the reel result attached.
A campaign rate change, decided in place. Free spins sent, played and pending, and a rate change from the provider waiting for the operator's decision.
Certified against actual RTP. Every game's actual RTP next to its certified one, with deviations and re-certification flags.
The provider's side. The studio sees its games' performance with every operator, and each settlement status, in the same back office.
Settle invoices without the email chain.
Every settlement period moves from pending to reviewed to settled. When a provider's invoice and the ledger disagree, open a dispute scoped to the period, a game, a day or a single hour.
- Drill down from period to game, day and hour
- Comments, a transaction ledger and CSV export
- Ask the platform team to investigate from inside the thread
- Settled periods are locked
Operator and provider, with platform staff on request.
Certificates and markets, always current.
Providers keep certificates and declared markets per game in one registry, linked to their own document storage. Operators see validity and expiry, and send tracked requests for documents or confirmations.
- A compliance dashboard with certificates expiring in 30 or 90 days
- Jurisdictions declared per game and cross-linked to certificates
- Every game save records whether re-certification is needed
- An audited export of the RTP compliance view
Operator legal asks, provider answers.
Questions arrive with the round attached.
Ask a provider to investigate a round or verify a big win straight from the round or the Big Wins report. The provider sees the transactions behind it, so nobody re-types IDs into a ticket.
- Started from a round row or a big win
- Provider sees the round's transactions
- Replaces a separate service desk on each side
Operator raises, provider answers.
Agree the rules before the invoice, not after.
Free-spin and promo rounds count on the invoice the way both sides agreed: excluded, at full value, or partial with a discount the provider absorbs. Revenue-share rates keep their version history, and period overrides cover one-off discounts.
- Propose, approve, or reject with a required comment
- Monthly spin-value limits on the default rule
- Rates per operator, provider and brand, with history
Either side proposes the default. The other decides.
Free-spin campaigns with the rate agreed up front.
Operators send free spins to a player list on a schedule, cancel with withdrawal, and report on what was played. The rate for a campaign is requested and decided in the back office, so it is settled before the spins go out.
- Scheduled sending, retries and withdrawal
- Played-spins report and grant inventory
- Either side requests a rate, the other decides
Operator runs campaigns. Both sides agree the rate.
One set of numbers, read by everyone.
Dashboards, game history and monitoring read the same ledger that reconciliation uses. Operators see their players, games and providers. Providers see how their games perform across every operator.
- Player, game and round drill-down with replay and CSV export
- Big Wins report with a verification request on each row
- Big-win and RTP-deviation monitors with email and Slack alerts
- Provider overview: GGR, effective rate and amount due
Operator and provider, each in their own scope.
Built for teams who answer to auditors.
Access control is part of the product, not an afterthought.
Roles and groups
Predefined and custom groups. An admin can grant only what they hold. Providers manage their own staff.
Brand restriction
Limit a user to the brands they look after. Operators never see each other's data.
Two-factor sign-in
MFA, re-authentication before sensitive actions, and sessions that end on their own.
Audit log
Who did what and when, with an audited CSV export.
One login, several studios
A provider user can work across the studios they belong to without switching accounts.
A notification centre
A bell, waiting counts beside every menu entry, and one reference number per request.
Where the line goes next.
Planned work, in no fixed order. Customers move items up this list.
Jackpot settlement
Jackpot statements between operator and provider, with jackpot share shown separately in RTP.
Market rules that act
Declared jurisdictions checked automatically against where a game is available, not only as a report.
Material-change notices
Providers announce changes to a game or its certification, and every operator using it is notified.
Cashback and volume rebates
Rebate agreements kept and applied in the back office next to the contract rules.
Player protection and geo views
Market presence, geo restrictions and a player protection overview.
More alert channels
Microsoft Teams and on-call tools alongside email and Slack.
Your request
Tell us what your team needs from the operator–provider relationship. We read every suggestion.
See what it costs for your volume.
Leave your email and we send you a private link to our pricing calculator.