iGaming Glossary: Platform, Casino & Sportsbook Terms
Understand 38 terms used when comparing platform proposals, planning integrations and reviewing operator reports. These definitions connect delivery models, technology, game mathematics, financial workflows, player protection and acquisition to the scope or calculation a buyer needs to confirm.
Explore the guideAn iGaming glossary explains online casino and betting terminology. PAM manages player accounts; RGS technology serves games; RTP describes theoretical long-run return. Delivery labels and financial metrics need agreed scopes and calculations before suppliers can be compared fairly.
Delivery models, architecture and ownership
Turnkey platform. A supplier package that brings together the components needed for an agreed operating scope. It may combine platform software, integrations, configuration and support. Confirm the included products, retained operator responsibilities, third-party contracts and change process.
White-label platform. An existing supplier platform configured with an operator’s branding and supported options. Hosting, staffed services and commercial or licensing arrangements depend on the package. The label alone does not establish ownership, permission to operate or available customization.
Custom platform development. Commissioned software built around a defined product or workflow. It can cover the entire platform or selected components. Source-code rights, third-party dependencies, acceptance criteria and support responsibilities belong in the agreed delivery scope.
Modular architecture. A system organized into components with defined responsibilities and interfaces. A business can commission or replace selected modules while retaining others. How independently those modules can change depends on their actual data, deployment and integration boundaries.
Headless platform. An architecture that separates the player-facing experience from backend capabilities accessed through APIs. It supports different interfaces over shared services. It does not automatically make the backend replaceable or remove the need for integration and journey testing.
Software as a Service (SaaS). Software accessed as an ongoing service rather than operated entirely by the customer. In iGaming, check the hosting, release, configuration, data-export and support terms. A subscription does not itself transfer the supplier’s source code.
Multi-tenant platform. A shared application serving multiple tenants with defined separation of their data, settings and permissions. A tenant may represent an operator or another business boundary. Multiple brands and multiple tenants are related concepts, but their isolation requirements can differ.
Supplier terminology is illustrated by SOFTSWISS’s delivery-model comparison. AWS’s SaaS explanation provides the underlying service and tenancy context.
Core platform and integration technology
Player Account Management (PAM). The services and operator workflows that manage player identity, account status and permitted activity. Depending on the implementation, PAM connects verification, restrictions, wallets and support tools. Confirm which system owns each account record and decision.
Content Management System (CMS). Tools for managing pages, promotions, banners, languages and other presentation content. A CMS is distinct from the financial ledger or account-control system, even when staff access them through one back-office interface.
Remote Gaming Server (RGS). Server-side technology that runs or serves supported games, controls round state and exchanges transactions with the operator’s wallet or platform. An RGS and a game aggregator perform different functions, although a supplier may offer both.
Game aggregation. A distribution and integration layer connecting content from multiple game providers. It can normalize catalogue, launch, transaction and reporting interfaces. A single technical connection does not establish rights to every game, provider or intended market.
Application Programming Interface (API). A defined way for software systems to exchange requests, events and results. An iGaming API contract specifies more than endpoint names: authentication, transaction references, failure responses, retries and version behavior affect whether the connected journey works reliably.
Wallet ledger. The financial record of credits, debits, reservations and related adjustments behind player balances. It should connect each posting to its business event. The displayed balance is a view of that record, rather than a replacement for transaction history.
Seamless wallet. A provider-integration model in which game transactions use the operator’s wallet through agreed interfaces. This differs from moving funds into a separate provider wallet. Confirm balance authority, pending transactions, rollbacks and reconciliation behavior for the selected implementation.
See the primary product descriptions for PAM, RGS and aggregation, alongside AWS’s API explanation.
Game mathematics, outcomes and verification
Random Number Generator (RNG). A component that supplies random values used in outcome generation. The game’s logic maps those values to results. Assessing an RNG alone does not verify every payout, interface state or financial transaction in the complete game.
Return to Player (RTP). The theoretical proportion of stakes returned as prizes over the long run under a specified game model. Observed RTP measures an actual sample. Neither figure promises what an individual player will receive during a session.
Volatility. The variability of game returns around their expected behavior. Games with similar theoretical RTP can distribute prizes differently. A volatility label needs the underlying mathematics and measurement definition; it does not predict a particular sequence of wins or losses.
Provably fair. A verification design that lets a user check defined properties of outcome generation, often using commitments, disclosed inputs and a reproducible calculation. The mechanism’s exact guarantees depend on its implementation. Verification does not replace wider game testing or independent approval.
Jackpot. A prize feature with defined eligibility, funding and award rules. A progressive jackpot grows according to its contribution model; a network jackpot can span connected games or operators. Contributions, awards and interrupted play need traceable financial records.
The Gambling Commission distinguishes theoretical RTP, actual RTP and volatility. Its RNG guidance and Stake Engine’s verification implementation address different parts of outcome assurance.
Sportsbook activity and trading
Odds. The quoted price of a betting outcome, expressed through formats such as decimal, fractional or moneyline. Odds determine the applicable payout calculation and imply a probability, but the offered price is not a guarantee that the outcome will occur.
Handle. The total value of wagers counted within a defined scope and period. Specify whether the report includes only settled wagers and how it treats promotions, voids and corrections. Handle is wagering activity, rather than operator profit or customer deposits.
Sportsbook hold percentage. Gross gaming revenue divided by the relevant betting handle, expressed as a percentage. Confirm matching settlement periods and wager definitions. Some vendors use “hold” for a deposit-and-withdrawal metric, so the denominator must be stated before comparing reports.
Trading and risk management. The processes and tools for managing markets, prices, bet acceptance, limits, liabilities and settlement exceptions. Supplying those tools is a different scope from staffing a trading operation. The responsible people, permitted interventions and escalation process should be explicit.
Primary references include odds terminology, DraftKings’ sportsbook hold definition and an example of the alternative payments-layer use of hold.
Payments, settlement and revenue reporting
Cashier. The player-facing deposit and withdrawal experience plus its connected payment workflows. It can include method selection, payment initiation, status information and withdrawal requests. The cashier interface depends on processor events, account controls and the authoritative ledger.
Settlement. Completion of a financial obligation under the relevant workflow. Bet settlement applies an accepted result to a wager; payment settlement concerns funds moving through the payment chain. A processor confirmation, player credit and bank payout can represent different stages.
Reconciliation. Comparing records across the platform, payment providers and game or sportsbook systems to explain balances and movements. It identifies missing events, timing differences and mismatches. Corrections should retain their connection to the original transaction and approved review process.
Chargeback. A payment reversal raised through a card-payment dispute process. It differs from an ordinary merchant refund and can have its own statuses, evidence and fees. Platform handling needs to track the dispute alongside the original payment and ledger entries.
Gross Gaming Revenue (GGR). Wagering revenue calculated from the relevant stakes less player winnings for the defined activity. It is a gross operating measure, not net profit. The reporting specification must explain settled rounds, promotional wagers, cancellations and corrections.
Net Gaming Revenue (NGR). GGR after the deductions defined for the report or commercial agreement. Deductions can differ between suppliers and contracts. Record the exact formula, eligible costs, adjustment timing and negative-balance treatment before using NGR for comparisons or revenue-share calculations.
Adyen documents payment-lifecycle states and transaction-level reconciliation records. SOFTSWISS separately defines GGR and contract-dependent NGR deductions.
Identity, player protection and access controls
Know Your Customer (KYC). Processes for identifying customers, checking their identity and assessing relevant customer information. In a platform, the resulting statuses connect to permitted actions and review workflows. A verification-provider response is distinct from the operator’s final policy decision.
Anti-Money Laundering (AML). The wider policies, controls and review processes used to address money-laundering risk. KYC contributes information to that framework. Technology can support screening, monitoring, records and case routing; the required policy and decision responsibilities depend on the business and applicable requirements.
Geolocation. Establishing and checking a user’s physical location using supported device and network signals. It can inform access decisions and fraud review. The integration must distinguish a permitted location from an inconclusive check, unavailable service or suspected location manipulation.
Responsible gaming controls. Product and operational measures supporting player protection, such as configured limits, time controls, self-exclusion and restricted communications. A control needs consistent enforcement across connected journeys. Its required behavior and escalation ownership should follow the operator’s approved policies.
These boundaries are described in Sumsub’s KYC and AML explanation, GeoComply’s location-verification explanation and the Gambling Commission’s technical-standards framework.
Acquisition, retention and player economics
Customer Relationship Management (CRM). Systems and workflows for organizing player information, communication, segmentation and service activity. Marketing automation can use that information to trigger campaigns. Permissions, communication preferences and player restrictions need to remain effective when data moves between tools.
Affiliate attribution. Rules and tracking that assign eligible player events to a referring partner for reporting and commission calculations. Confirm qualifying events, attribution windows, duplicate handling and correction rules. A tracked click, an account registration and a payable acquisition are different events.
Customer Acquisition Cost (CAC). Acquisition spending divided by the number of newly acquired customers under an agreed definition. Match the spend, customer cohort and period. State whether acquisition means registration, a verified account, first deposit or another qualifying event before comparing channels.
Lifetime Value (LTV). The observed or estimated value of a customer relationship over a defined horizon. A revenue-based LTV and a contribution-based LTV answer different questions. Record the revenue basis, included costs, cohort and assumptions when comparing LTV with acquisition spending.
Retention. The extent to which an acquired player group returns and remains active over a defined interval. Specify the original cohort and qualifying return activity. Registration retention, depositing-player retention and wagering activity can produce different results from the same customer population.
See Affilka’s attribution and partner-management scope, Stripe’s acquisition-cost explanation, its lifetime-value discussion and a gaming-specific retention definition.
Turn the terminology into a clear platform brief.
Share your intended product, existing systems and supplier proposals. We can help define component responsibilities, integration boundaries and the evidence your team needs to review the delivery.
Let’s build