15 delivery areas and 121 individual implementation items. This record explains the workflows already built, why they matter and the evidence available for review.
121Implementation items recorded below
15Connected delivery areas
185,135Assertions in the 8 October MariaDB run
This is a feature/workflow record, not a count of independent products or a certification statement. Test results are the existing dated local run.
01 / Player foundationIMPLEMENTED FOUNDATION
Player accounts, authentication and privacy
An operator needs one accountable view of the customer across play, account servicing and responsible gambling.
How it works
A customer signs in, the API establishes their identity and permissions, and account views read the same platform records used by betting and games.
What has been delivered
Registration and login endpoints, bearer-token sessions and account profile surfaces.
Player two-factor enrolment, one-time codes, recovery paths and brand-level authentication policy.
Account summary, betting history, transaction history and player activity statements.
Profile and verification workflows with recorded identity decisions.
Player data export for access requests and an anonymisation workflow with explicit refusal conditions.
Retention of financial and exclusion records alongside destruction of defined identity fields.
Registration checks against retained erased-identity hashes to support exclusion controls.
02 / Financial coreIMPLEMENTED FOUNDATION
Wallet, ledger and movement controls
A balance is useful only when every movement can be explained and retries or concurrent actions cannot create a second spend.
How it works
A funded action goes through the wallet service, records its transaction and updates the account projection. Reconciliation provides a separate check of the resulting position.
What has been delivered
Cash and bonus balance handling behind the central wallet service.
Credit, debit and transaction history with references to the action that moved the balance.
Insufficient-funds refusals and bounded movement/balance arithmetic.
Bonus credit, bonus-to-cash conversion and reversal handling.
Ledger reconciliation command and supporting integrity tests.
Withdrawal workflow, approval controls and policy checks.
Concurrency and retry probes for a controlled play-credit deployment.
Seamless-wallet integration support for third-party game transactions.
03 / Sports productIMPLEMENTED FOUNDATION
Sportsbook and customer betting journeys
Operators need coverage that a customer can navigate and betting behaviour that remains consistent when prices change.
How it works
The customer moves from a sport to a league, coupon and event, builds their selections, reviews the current quote and submits to the platform’s betting controls.
What has been delivered
Sport, league, competition, coupon and full-event browsing surfaces.
Pre-match and in-play views over the configured market data.
Market and selection structures with prices and line information.
Betslip, stake calculation and multiple-selection betting flows.
Correlation-adjusted same-game pricing, with naive and adjusted quotes available for comparison.
System-bet combination expansion in the front-end engine, including traditional structures from Trixie through Lucky 63.
Server-side price-change re-offers instead of silently accepting a different quoted price.
Open and settled bet history and cash-out quote/acceptance workflows.
04 / Trading foundationIMPLEMENTED FOUNDATION
Odds, pricing, risk and settlement
A sportsbook needs to control aggregate exposure and establish how a result was obtained, alongside offering attractive customer prices.
How it works
Provider prices are stored and selected by a configured strategy. Betting checks the permitted exposure; settlement records the result and credits through the wallet.
What has been delivered
Multi-provider odds interfaces and provider-specific adapters.
Stored bookmaker prices that can be repriced without another feed fetch.
Best-price and prioritised-bookmaker pricing strategies.
Feed freshness and credit/quota-aware synchronisation controls.
Trading configuration, maximum-payout and stake-risk controls.
Selection liability reporting and scheduled liability sweep/suspension logic.
Cash-out repricing and race-related test coverage.
Official-result settlement integration and documented result provenance.
A separately controlled synthetic demo fallback that must remain disabled for a regulated real-event deployment.
05 / Game estateIMPLEMENTED FOUNDATION
In-house games and game mathematics
Owning the game implementation allows the team to show its rules, mathematics and evidence directly, while taking responsibility for independent evaluation.
How it works
The game accepts a funded action, applies the engine rules, resolves the outcome, records the round and settles its wallet movement. Published rules and return information must match that engine.
What has been delivered
House-banked and instant-play implementations spanning card, table, number and arcade-style games.
Game controller entry points for blackjack, baccarat, roulette, craps, Sic Bo, poker variants, bingo and keno.
Dice, limbo, mines, plinko, wheel, coin flip, hi-lo, scratch, crash and tower-style game implementations.
Sport-themed games including penalty shootout, snooker and cricket, plus virtual racing capability.
Slot mathematics and configurable variants, including a five-reel entry point.
Advertised-return checks against the engine’s mathematics and constants.
Game rules and return disclosures delivered with the game catalogue.
Seed commitment/reveal and round-verification mechanisms, with determinism and statistical test coverage.
06 / Game operationsIMPLEMENTED FOUNDATION
Multiplayer, tournaments, jackpots and recovery
A complete product must deal with shared rounds, pooled value and interrupted play, as well as the happy path of a single game.
How it works
A round or competition records participation and funded state. It either resolves normally or follows the defined recovery/abandonment policy without silently losing track of value.
What has been delivered
Chinchón game and player-versus-player table implementations.
Multiplayer state, close, outcome and rake-related test coverage.
Shared crash-round implementation and shared-round integrity checks.
Tournament and sit-and-go management, participation and prize workflows.
Prize-versus-entry validation and tournament publication checks.
Jackpot configuration and ticker/catalogue presentation.
Active funded-round listing with resume or settlement paths.
Abandoned-round resolution and named recovery mechanisms for different game shapes.
07 / Player protectionIMPLEMENTED FOUNDATION
Safer-gambling and jurisdiction controls
A responsible-play control needs to apply at the server decision point, even if a client ignores the screen that describes it.
How it works
The player sets a limit or exclusion. Subsequent account and funded actions consult the stored policy, and any permitted relaxation follows its configured cooling-off process.
What has been delivered
Financial limits and cooling-off for relaxations.
Reality-check sessions, acknowledgement and account-facing controls.
Self-exclusion and time-out account workflows.
Server-side slot cycle control and per-action game-cycle checks.
Jurisdiction-configured stake and age-related rules.
Withdrawal cancellation refusal within the withdrawal workflow.
Interrupted-round and game-disclosure requirements tied into the readiness evidence.
A compliance readiness command that separates checked controls, stubs and manual external obligations.
08 / Risk & providersIMPLEMENTED FOUNDATION
AML, identity, location and payments integration
Customer verification, national exclusion and real financial movement depend on contracted external systems as well as internal workflows.
How it works
Account and transaction activity feed risk decisions. Provider interfaces return verifiable decisions; exceptions are recorded and handled by an accountable operator role.
What has been delivered
AML monitoring rules invoked around financial activity and through the scheduled monitor.
AML case workflows, restricted withdrawals, named decisions and access checks.
Identity-verification provider interfaces, configuration and decision records.
National self-exclusion provider abstraction and GAMSTOP integration configuration.
Geolocation provider abstraction and explicit fail-open/fail-closed configuration.
Payment gateway abstraction, payment results, settlement and withdrawal services.
Provider credential handling, instrument-policy checks and tenant-specific payment configuration.
Linked-account/fraud review described in the operator product evidence.
09 / Customer growthIMPLEMENTED FOUNDATION
Segmentation, campaign automation and assisted proposals
An operator needs to target the right audience while applying consent and exclusion controls at the point of communication.
How it works
Staff define a segment, preview the eligible audience, review the campaign and dispatch through the platform’s consent and exclusion handling.
What has been delivered
Rule-based segmentation with all/any/none combinations.
A recorded catalogue of 14 segmentation rule types.
Fail-safe handling of unrecognised segmentation rules.
Audience previews and campaign automation workflows.
Consent and self-exclusion filtering described in the campaign implementation evidence.
An optional AI assistant that returns a readable, editable segment proposal.
Human actions remain separate from an assistant proposal: the assistant does not save a segment or send a campaign.
Audience counts are resolved by platform rules rather than invented by the assistant.
10 / Retention & commercial toolsIMPLEMENTED FOUNDATION
Promotions, bonuses, affiliates and loyalty
Reward rules and commercial incentives need to reconcile with the wallet and eligibility policy, rather than becoming a parallel account system.
How it works
A qualifying action is evaluated against the configured conditions. A reward is granted through the account model, and any wagering, commission or tier outcome follows its own defined rules.
What has been delivered
Promotion engine, condition evaluation and offer targeting.
Bonus grants, redemption and wagering allocation workflows.
Game contribution handling for bonus wagering.
Reward-granting and referral services.
Affiliate attribution and NGR-based commissioning described in the product records.
Loyalty/VIP services and segment-related tier progression.
Gamification events and leaderboard ranking services.
Administrative surfaces for bonuses, referrals, tournaments and rewards.
11 / Operator controlIMPLEMENTED FOUNDATION
Multi-brand administration and staff security
A platform that serves several brands must give an operator useful autonomy without allowing access to a sibling brand’s records.
How it works
Each request resolves its tenant and staff identity. The API applies tenant ownership and role/capability checks before reading or changing operator data.
What has been delivered
Tenant resolution, tenant settings and brand-scoped account/content records.
Tenant provisioning service for starter product content.
Cross-tenant ownership and isolation tests.
Distinct platform and brand staff access models.
Owner, manager, trader, support and read-only roles described in the product records.
Brand-level player/staff two-factor policies and mandatory platform-staff authentication policy.
Scoped brand settings, staff management and administrative audit.
Shared-credential restrictions and capability hardening tests.
12 / Business operationsIMPLEMENTED FOUNDATION
Reporting, audit and platform billing
An operator and its supplier need to explain player activity, financial outcomes, staff decisions and the commercial relationship.
How it works
Reports read the underlying account and betting records. Staff actions carry identity into the audit trail; platform billing produces invoices from the configured plan and period.
What has been delivered
Operator return and player activity-statement services.
Breakdown reporting and bet-search services.
CSV exports and scoped operational views.
Named-actor audit service, filtering and write-coverage tests.
Staff identity and tenancy checks around administrative audit.
Platform billing-plan assignment and invoice generation.
GGR-based billing calculation and due-invoice processing.
MRR reporting support in the platform billing service.
13 / Product deliveryIMPLEMENTED FOUNDATION
API, widgets, skins and custom interfaces
Customers should be able to choose their product experience without moving the financial and game decisions into the presentation layer.
How it works
The browser or application calls the same API. Widgets and custom screens render the response; the platform controls the decision and records its outcome.
What has been delivered
Versioned API and repository OpenAPI specification.
Recorded inventory of 335 operations across 292 documented API paths.
43 front-end widget files in the recorded inventory.
Ten visual skin presets and four interface locale directories.
WordPress/Elementor delivery route and static customer delivery route.
Seven distinct operator-brand demonstrations.
A custom sportsbook front end using the public API without the shared widget engine.
Shared brand plumbing and asset synchronisation tooling.
Partner API keys, scopes and idempotency support.
14 / Application scopeIMPLEMENTED FOUNDATION
Player, operator and sales application codebases
Different users need different mobile surfaces while the account and financial rules remain consistent across devices.
How it works
The applications use a shared typed API client. Credentials use secure device storage; screens render platform responses and do not decide whether a funded action is permitted.
What has been delivered
Player application source for sign-in, coupon/betslip, casino, account history and safer-gambling views.
Operator application source for dashboard, player review, withdrawal queue and audit views.
Sales application source for a portable product presentation.
Shared API client and money-formatting code in an npm workspace.
Secure-store credential handling described in the mobile architecture.
Separate environment configuration and build profiles per application.
A documented release-verification path and common server-controlled decision boundary.
15 / Engineering evidenceIMPLEMENTED FOUNDATION
Verification, integrity hardening and deployment tooling
A platform needs repeatable ways to find errors in financial, game and access behaviour and to establish what was actually deployed.
How it works
The local suite evaluates the implementation; specialised probes exercise a controlled deployment; the readiness command identifies obligations that code cannot satisfy.
What has been delivered
Recorded backend verification: 2,503 passing tests and 185,135 assertions on isolated MariaDB 11.8.2, 8 October 2026.
76 passing tests against the shipped front-end engine in that local evaluation.
Static-analysis configuration and documented PHPStan verification procedure.
Separate slow game/RNG simulations and production-database parity configuration.
Wallet, game outcome, retry, concurrency and abandoned-round integrity tests.
Cross-tenant, staff capability, two-factor and administrative audit test coverage.
Smoke, abuse, adversarial and concurrency probe tools for controlled evaluation.
Health services, operational alerting and webhook dispatch services.
Bunny static deployment, shared asset synchronisation and documented API deployment procedures.
Review the full record
Bring the questions the summary cannot answer.
A deeper review should trace representative account and funded actions through the API, inspect failure and retry behaviour, and establish the exact build and configuration for the proposed customer. The team can demonstrate the operator surfaces in a supervised session.
The foundation is built. Be part of what comes next.
Explore the working engine, meet the team and discuss the investment that advances independent testing and first customer deployments. Bring your questions; we’ll show you the product behind the proposition.