Glossary
Quick reference for terms used across the Betting Backoffice. Linked from the first use in each page.
Account and brand
| Term | Meaning |
| White Label (WL) | One of your operator brands. If your company runs several brands, each is a separate WL. The WL picker at the top of every Betting BO page sets which brand's data you see. Most pages — bets, callbacks, freebets, insurance, content, SPA config — are scoped to the selected WL. Match/Markets are platform-wide but the bets shown on a match are still scoped to your WL. |
| Integration manager | Your dedicated contact at DATA.BET who set up your account and is your first stop for access, configuration, and integration questions. |
Players and bets
| Term | Meaning |
| Player ID | The player's identifier on the DATA.BET side. |
| Platform Player ID | The player's identifier on your platform. Use whichever your CRM or support tool gives you. |
Single (S) bet | One stake on one outcome. |
Express / Accumulator (E<n>) | One stake on n outcomes; all must win for the bet to pay out. E3 = 3-leg express. |
| System bet | One stake split across all n-leg combinations of m selections; pays out on each combo that wins. |
| Bet Builder | A bet composed of multiple legs on the same match, priced as a single combined odd. Filtered in the Bets list with the Bet builder filter. |
| Outright | A long-term bet on the overall result of a tournament (e.g. season winner), settled when the tournament ends rather than at a single match. |
Bet status (row badge on the Bets list)
The single-letter badge at the start of each Bets-list row shows the bet's current status. The canonical values from the BetStatus enum are:
| Status | Meaning |
INIT | Bet has just been initialised |
CREATED | Bet has been created but not yet placed |
PLACED | Funds successfully held on the player's balance; processing begins |
PLACE_ERROR | Funds couldn't be held (limit/balance issue on your platform) |
ACCEPTED | Bet validated and accepted |
DECLINED | Bet rejected by the betting service — terminal |
FORCE_DECLINE | Manually declined by an operator/trader |
ARBITRAGE_ACCEPTED / ARBITRAGE_DECLINED | Arbitrage-mode acceptance/decline (Risk Management) |
SETTLED | Bet has been settled (paid out or written off) |
UNSETTLED | Bet has been un-settled (settlement rolled back) |
ROLLED_BACK | Bet has been rolled back after acceptance |
REFUNDED_MANUALLY | Operator-issued manual refund |
Badge letters are short forms of these names — confirmed examples: A = ACCEPTED, D = DECLINED, P = PLACE_ERROR, F = FORCE_DECLINE. For the full state machine see the Bet lifecycle.
Bet result status (Odd status)
When the event has resulted, the bet's outcome is one of: NOT_RESULTED, WIN, LOSS, HALF_WIN, HALF_LOSS, REFUNDED, CANCELLED, REFUNDED_MANUALLY (from BetOddStatus).
Risk and money
| Term | Meaning |
| Risk | The operator's potential net result if the bet wins, expressed as a signed number. Negative = the operator owes the player on a win (typical case). Positive = the operator profits even if the bet wins (rare, occurs with bonus mechanics). The sign convention is the same on the Bets list, the Match page header, and the Markets panel. |
| Stake / Bet | The amount the player wagered. |
| Odd | The decimal price the player accepted when placing the bet. |
| O.Amo / O.Risk | Outright Amount and Risk — stakes and operator risk from outright (long-term) bets on the match. |
| T.Amo / T.Risk | Tournament-level stake and operator risk — bets placed at the tournament level rather than on this specific match. |
| Bet Max Stake | The largest stake that will be accepted on a single bet for this match (cap, not actual). |
| Bet Max Risk | The largest risk DATA.BET will accept on a single bet for this match (cap). |
| Possible Risk | The worst-case net result across all current bets if outcomes fall the wrong way. |
| MaxR | Match-level risk cap (the limit shown in the Matches list). |
Matches
| Term | Meaning |
| Match status | The lifecycle state of a match. Values (from the MatchStatus enum): NOT_STARTED, LIVE, SUSPENDED, ENDED, CLOSED, CANCELLED, ABANDONED, DELAYED, UNKNOWN. The single-letter badge in the Matches list is the first letter of the status — L = Live, S = Suspended, E = Ended, A = Abandoned, etc. |
| Market status | The state of an individual market (from the MarketStatus enum): ACTIVE, SUSPENDED, DEACTIVATED, RESULTED, CANCELLED. Shown in the markets panel as a badge: A = Active, S = Suspended, D = Deactivated, R = Resulted, C = Cancelled. |
| TOP-flagged | A match marked via the Top checkbox on the Match page (in this Betting BO) or by a trader inside the Trading BO. Both sources feed the same flag. Originally intended to drive BETTING_TOP_SPORT_EVENTS / BETTING_POPULAR_SPORT_EVENTS banner providers, but those providers aren't currently wired through to the SPA — to actually pin a match for players, use Manual rankers instead. |
| Defective | A match flagged as having data-quality issues (mis-scored, mis-priced, or otherwise out of sync with reality). Used as a filter on the Matches list. The flag is set by trading operations — coordinate with your trading team before changing it. |
| Linked sport | A relationship that lets the BETTING_LINKED_SPORT banner provider pull events tagged with a given sport. The link itself is configured at the platform level — ask your integration manager. |
Callbacks
| Term | Meaning |
| Callback | An HTTP request DATA.BET sends to your platform when a bet event happens (placement, acceptance, decline, settlement, cash-out). Your platform's response is logged in the Callback history. |
| Group ID | The identifier shared by all callback requests for one bet. For bet callbacks this equals the Bet ID; you can paste a Bet ID straight into the Group ids filter on the Callback history. |
| Request ID | The identifier of a single HTTP attempt inside a Group. |
| Destination | The path on your platform that received the callback, e.g. /bet/place. The set of destinations is part of your callback integration contract — your integration manager has the canonical list. |
Content
| Term | Meaning |
| Page type | The display style of a sportsbook page: mix (combined sports + esports), esport (esports-only), or classic (sports-only). Banner zones target one page type at a time. |
| Banner zone | A slot on the sportsbook that displays banner content. Created in the Banners manager; zone name follows {pageType}-{location}-{platform}-{index}. Only the combinations listed in the Banners manager section are actually delivered to the SPA. |
| Provider type | The source of content for a banner slot. Currently supported in production: CMS_BANNER_ID (a single banner) and CMS_BANNER_LIST (a slider of banners). |
| Provider config | One filled-in instance of a provider type inside a zone. A slider zone usually has several provider configs — one per banner in the rotation. |
| Featured tournaments zone | A separate concept from a banner zone — it drives the tournament widget in the sportsbook's navigation sidebar, not banners. Names follow the {pageType}-{location}-{platform} format (e.g. mix-left-web) with no index. |
| MaxCount | Maximum number of banners a zone can display. Set when the zone is created and the only field you can edit afterwards. |
| Interval | For carousel/slider zones, the rotation speed between slides, in milliseconds (e.g. 5000 = 5 s). |
| Fixed flag (WL scope) | A platform-side toggle that must be enabled at your WL for Manual rankers to take effect. Without it, pins you configure in Manual rankers are stored but not surfaced to players. Ask your integration manager to enable it. |
| Marked test account | A player account on your sportsbook tagged internally by your integration manager so that bets placed from it are captured as pinned hot bundles. The tagging step is what makes a bundle appear; an untagged account's bets are ignored. |
| Context (hot bundles) | The page-scope identifier under which a hot bundle is surfaced — e.g. home, esports, a specific tournament scope. Determined automatically from the sportsbook page the original bet was placed on. |
| Personal ranking (Categorizer config) | A toggle in Categorizer config that reserves the top 3 sport-rail slots for a logged-in player's own most-bet-on sports (based on their last 100 bets). Distinct from "personalized ranking" — that's a separate match-ordering signal driven by a neural-network model. |
| Personalized ranking | The default match-ordering signal used by the sportsbook to rank events for each player. Powered by a neural-network model; it's also what generates the auto-populated hot bundles. Manual rankers is the operator override on top of it. |
| Algorithm (Suggestions) | The strategy used by the Suggestions page to derive stake chips. Options: MANUAL (you set the amounts), STATISTIC (aggregate-based defaults), SMART (personalized per player — recommended). |