Owns product decisions, vendor relationships and the operating model. Orchestrates the business; it is not an extra transaction hop between the wallet and a game.

The account holder starts onboarding, funding and play journeys. Each action remains subject to access, balance and player-protection controls.

Connects campaigns and traffic sources with registrations and first-time depositors. Cohort-level spend and conversion support CAC analysis.

Tracks partner referrals and agreed CPA or revenue-share terms. Attribution and contract definitions determine which activity qualifies for partner reporting.

Creates the account, collects required details and records acquisition context. Verification and activation follow the market-specific onboarding policy.

Age, identity, location and screening checks determine permitted account actions. Their timing and depth depend on the market and applicable policy; further review may be needed.

Maintains account state, permissions, product access and links to financial and protection controls. The platform can integrate separate wallet, payments and content services.

Records confirmed credits, debits and reserved balances. Duplicate callbacks must not produce duplicate postings; game-round transactions are distinct from external movement of funds.

Offers eligible payment methods and displays deposit or withdrawal status. A submitted payment request does not itself mean funds are available in the player wallet.

Selects a payment channel using method, currency, market and provider availability. Routing rules and controlled retries help manage acceptance, cost and duplicate-payment risk.

Processes the payment through its supported network and returns verified status updates. Authorisation, capture, payout and settlement are distinct stages whose availability varies by method.

External banking, card or local-payment infrastructure executes the relevant funds movement. These rails are outside the player ledger and report results through the payment integration.

Matches internal transaction records against processor reports and settled amounts, including fees, refunds and exceptions. Reconciliation is separate from immediate game-round settlement.

Presents games enabled for the brand, market and player. Catalogue availability and game discovery are separate from transaction processing and round outcomes.

Launches the selected game with a scoped session and required account checks. The content connection can use an aggregator or a direct provider integration.

Normalises access to multiple game providers through one integration. It reduces integration work but does not replace the provider’s game logic or the operator’s player ledger.

Operates or supplies the game service and round outcomes for connected slots, live or other content. A studio can also be the provider; it need not be another runtime hop.

Applies validated bet, win or rollback transactions to the wallet using unique round and transaction identifiers. A settled game round is not the same as a PSP payout settlement.

Handles bet placement, tickets and settlement of sports markets. It shares account and wallet services but has a separate odds, trading and exposure-management workflow.

Supplies market pricing, sports data and trading controls. Sportsbook exposure risk concerns accepted bets and liabilities; it is distinct from responsible-gambling risk.

Publishes time-stamped account, payment and gaming events with stable identifiers. This data pipeline supports reporting and decisions; it does not carry or transfer player funds.

Stores deduplicated history with consistent player, currency and timestamp definitions. Data quality and complete observation windows determine which analyses and forecasts are meaningful.

Turns validated history into business metrics. GGR is based on stakes and winnings; NGR depends on the operator’s deduction policy. Deposits alone are neither revenue nor LTV.

Groups players by observed lifecycle and product behaviour. Consent, exclusion status and protection rules are checked before a segment is activated for commercial communication.

Orchestrates event-based messaging and measures responses. Opt-outs, consent and responsible-gambling suppressions take precedence over engagement or reactivation campaigns.

Applies offer eligibility, wagering rules and bonus-balance transitions. Bonus cost needs explicit accounting and protection restrictions apply before new offers are granted.

Builds model-ready activity and transaction series from historical events. Missing data, short histories and currency changes are explicit input-quality issues, not zero activity by default.

Estimates future activity and transaction-series ranges from player history. Commercial value needs a separate economics layer and validation. A behaviour forecast is not a clinical or validated RG risk score.

Combines forecast uncertainty, business rules and contact eligibility to propose an action. The operator can review outcomes; protected or excluded accounts are suppressed from commercial activation.

Monitors changes in play, spend and contact history against an approved protection policy. Signals can initiate immediate safeguards and specialist review; they are not a diagnosis.

A specialist assesses context, records interactions and evaluates whether safeguards work. Human oversight complements automatic protection; urgent safeguards need not wait for a manual review.

Enforces applicable deposit, time and loss limits, cooling-off and self-exclusion. Status changes reach account access and campaign systems so protection is enforced across the operation.