How aggregators like SoftSwiss and Slotegrator work

A content aggregator is a "delivery layer + marketplace" between studios (B2B game providers) and operators (online casinos/bookmakers). It solves three problems: distribution (one connection - hundreds of studios), compliance (certificates, market builds, RG), monetization (billing, reports, promo). Using SOFTSWISS Game Aggregator and Slotegrator as an example, let's look at how such platforms work from the inside.

1) What exactly does the aggregator give

Single integration for the operator. By connecting to the aggregator API/SDK, the operator gets a library of thousands of games from different studios.

Onboarding for studios. One contract and technical requirements → access to hundreds of operators; fewer integration points and certifications.

Directory and metadata. RTP versions, volatility, languages, geo-restrictions, age tags, images, demos.

Promo framework. Freespins, tournaments, missions, quests, network/local jackpots.

Billing and reports. Spin events → NetWin/GGR, commissions, royalties, true-up; uploads for BI.

SLA and monitoring. 24/7 observation, alerts, folbacks, uptime/latency reports.

2) Technical architecture (simplified)

Gateway/Router. Routing requests from operators to RGS studios; geo-balancing.

RGS integrations. Studio side: outcome generation (RNG), bonus logic, build version control.

Wallet Layer. Two patterns: debit/credit (bet/pay on the fly) and transfer (deposit in session). Idempotence is mandatory.

Auth & Session. Tokens, country, currency, RG flags, market restrictions.

Telemetry/Event Bus. 'spin _ start/finish', bonus triggers, jackpot contributions/payouts, errors.

Compliance Store. Certificates, list of permitted countries, market configs, certificates/warnings.

Analytics/Billing. Aggregation by games/markets/operators, calculation of commissions/royalties, invoicing.

DevOps. CDN assets, WAF, anti-tamper, canary calculations, versions/hashes of builds.

3) Onboarding studio (provider)

1. Treaty. IP, jurisdictions, payment models (rev-share/per-spin/hybrid), reporting and auditing.

2. Technical integration. API compatibility, wallet, log formats, repeatable builds, hash registry.

3. Catalogue. Game cards, RTP ruler, volatility, tags, images/videos, demos.

4. Compliance. Download laboratory certificates, mapping to countries and market builds (language, warnings, RTP profiles, limits).

5. QA. Tests of functionality, wallet, RG hooks, emergency scenarios.

6. Listing. Games fall into the catalog and are available to operators by geo/currency settings.

4) Operator onboarding

1. API/SDK. Authorization, session launch, wallet, iframe/web view.

2. Geo & RG. Country/currency restrictions, age tags, timeouts/limits, self-exclusion.

3. Promotional module. Setting up freespins, tournaments, missions; segmentation of players.

4. Reporting/invoices. NetWin/GGR uploads, commissions, royalties, FX; true-up monthly/quarterly.

5. SLAs/incidents. Alert channels, folbacks, technical work windows.

5) How does one spin (life cycle)

1. Session Init - checking geo/build version/market config.

2. Bet (debit) - the operator writes off the bet through the Wallet API.

3. Outcome on RGS - RNG → result, bonuses, jackpot contribution.

4. Credit - return of winnings to the operator; events are written in Event Bus.

5. Billing - the aggregator aggregates events into reports, counts commission/royalties (rev-share or per-spin).

6. Compliance Check - filtering "optional spins," compliance with certificates and market settings.

6) Promotional tools in the style of SOFTSWISS/Slotegrator

Freespins/bonus rounds. Batch issuance, accounting for'cash/free' spins, different charging rates.

Tournaments/leaderboards. Metrics (multiplier, winnings, series), anti-bot defense, real-time tables.

Missions/quests. Goals within one or more games, rewards, schedule.

Jackpots. Local/network/progressive, transparent contributions and odds of winning.

Showcase placements. "New items," "top," "recommended," banner sets, A/B cards.

7) Compliance and market builds

Certification. Storage of laboratory reports, linking to specific builds/hashes.

Localization. Languages/warnings/age icons/rate limits.

RTP profiles. Multiple certified versions - operator-level selection within a country.

RG hooks. Timeouts, limits, self-exclusion, RG event logs.

Logs. Unchangeable key events (bet, result, bonus, jackpot), UTC time, export for audit.

8) Commission models and "money waterfall"

Calculation base: more often NetWin (GGR − taxes/jackpots/permissible deductions), less often - GGR.

Models:

Rev-share. The share of the provider from NetWin after the aggregator commission.
Per-spin (turnover-fee). Microfy off the paid back or share of the bet.
Hybrid. Minimum per-spin + upside from NetWin; tiered grids by volume.

Waterfall (typical): Bets → Winnings (= GGR) → Taxes/jackpots/bonus cost/PSP → NetWin → Aggregator commission → Provider share → Brand royalties (if any).

9) Pros and cons for the sides

Studio (provider)

Wide distribution "one port," fewer integrations and certifications.

Promo/tournaments/jackpots out of the box.

− Aggregator Commission, competition in the general catalog.

− Less control over storefront priorities.

Operator

One integration - hundreds of studios and ready-made market builds.

Unified billing and reporting, assistance with compliance.

− Dependence on the SLA of the aggregator and its roadmap.

− Part of the margin goes to the commission; not everything can be customized for your own UX.

10) Differences in approaches (generalized)

Catalog scale and geo-coverage. Number of studios, depth of localizations, presence of demo/modes.

Promo set. Native tournaments/missions, flexible metrics, ready-made campaign templates.

Analytics and reporting. Dashboards in real time, API for BI, depth of cuts (game/market/operator).

Compliance hub. Convenience of market builds, certificate validators, RG configs.

Cost of ownership. Commission structure, lot discounts, feature-fees for placements.

SLA/support. Reaction time, incident channels, public transparency of statuses.

(Specific figures and terms vary by contract; always compare on your traffic profile and target markets.)

11) Safety and reliability

Failover/Geo-redundancy. Duplication of regions, retro wallet, idempotent operations.

Anti-tamper. Obfuscation of the client, protection against substitutions, validation of the build by hash.

DDoS/WAF/CDN. Perimeter and asset delivery protection.

Observability. p95/p99 latency, error-rate, RTP/bonus frequency deviations.

Replay. Spin playback by seed/nonce for fast phonesics.

12) Reporting and invoicing

Event layer. 'game _ id, build_hash, stake, win, currency, spin_type, ts_utc, operator_id'.

Summary reports. NetWin/GGR by games/markets/operators, commissions/royalties, FX courses.

True-up. Quarterly exception reconciliations (free/test), FX, late-posting.

DWH/BI. API/uploads for cohort and portfolio analytics.

13) Risks and how to hedge them

Single point of failure. Use 2-3 aggregators + direct integrations with key operators.

Version chaos. Register of builds/hashes, auto-check of market configs.

Regulatory changes. Requirements matrix by country, quick updates of warnings/icons.

Reporting disputes. Clear scheme "optional spins," deduplication, audit rights, SLA responses.

Opaque "feature-fees." Count ROI of placements, record KPIs/responsibilities of parties.

14) Checklists

Studio → aggregator

RGS and wallet compatibility, idempotency.
Logs/UTC/replay, repeatable builds, hashes.
RTP ruler and market builds are documented.
Certificates/reports downloaded; game metadata is complete.
Promotional package (tournament/missions/freespins) for release.

Operator → aggregator

Geo-mapping: which games have which countries/currencies/RTP.
RG settings, age icons, limits.
Wallet API is integrated and tested for fault tolerance.
Quality dashboards (latency/error), alerts, SLA.
Reporting/invoicing, true-up and FX policy.

15) 30-60-90: Launch Roadmap

0-30 days

Inventory of catalog/certificates, RTP line finale and market builds.

Preparation of metadata/assets, technical "smoke" RGS/wallet.

Promo plan: freespins/tournament for release, banner kit.

31-60 days

Integration with 1-2 aggregators, pilot listings with priority operators.

Enabling dashboards (DAU/NetWin/bonus-freq), RTP alerts/frequencies.

LQAs/locales, window checks and age-labels.

61-90 days

Expansion of coverage (more aggregators/operators), joint campaigns.

Set up quarterly true-up, FX/exception reconciliations.

In parallel - 3-5 direct integrations with key brands.

16) Short FAQ

Does the aggregator change RTP/odds? No, it isn't. It distributes certified provider profiles and monitors market build compliance.

Is it possible without an aggregator? Yes, but more expensive and longer: more integrations, certifications, reporting and support.

Why is one game different by country? Market requirements: language/warnings/limits/allowed RTP versions.

Who pays for jackpots/tournaments? By contract: contributions usually up to NetWin; prize money - in separate estimates.

Level aggregators SOFTSWISS and Slotegrator are the circulatory system of iGaming: they scale distribution, standardize compliance and simplify money. For the studio, this is the path to hundreds of operators and ready-made promotional tools; for the operator - a single entry point into the world of content with standardized SLA and reporting. Success comes to those who are disciplined in the market builds, transparent in the logs and know how to work with the showcase and the aggregator promo kit.