Player accounts & wallet
Registration, account history, cash and bonus balances, ledger reconciliation, withdrawal workflows and seamless-wallet integration.
Evidence reference
WalletTest.php; SeamlessWalletTest.php; LedgerAuditCommandTest.php
02 / Capability catalogue
A practical inventory of what exists, where live integration is still required, and what independent approval must establish.
24 capabilities
Registration, account history, cash and bonus balances, ledger reconciliation, withdrawal workflows and seamless-wallet integration.
WalletTest.php; SeamlessWalletTest.php; LedgerAuditCommandTest.php
Pre-match and in-play surfaces, multiple-bet structures, price re-offers, cash-out and correlation-adjusted same-game pricing. Official settlement and commercial feed rights remain deployment gates.
docs/marketing-spec/03-feature-sportsbook.md
Multi-provider adapters, stored bookmaker prices, configurable pricing strategies, exposure reporting and liability sweeps.
backend/app/Services/Odds/; backend/app/Services/Betting/
30 game controllers, game rules, published return figures and seed-based round verification. Internal game-maths tests are evidence for independent testing, not a test-house approval.
AdvertisedRtpTest.php; GameEngineCertificationTest.php
Resume or resolve funded rounds, with abandonment handling for supported game types.
backend/app/Console/Commands/ComplianceReadinessCommand.php
Seamless-wallet architecture supports a third-party content route. Supplier contracts, content rights, integration acceptance and applicable approvals are still required.
SeamlessWalletTest.php
Financial limits, cooling-off, reality checks, account exclusions and server-side game controls. Market-specific configuration must be reviewed before launch.
docs/RTS-MAP.md
Monitoring rules, case handling, withdrawal restrictions and named decisions. The operator must own its policies, thresholds and regulatory responsibilities.
backend/app/Services/Compliance/Aml/
Provider interfaces and drivers exist. Live identity verification and GAMSTOP configuration and acceptance remain outstanding.
backend/config/compliance.php; compliance:readiness
Payment and geolocation interfaces exist. Demo payments are simulated; real-money deployment needs contracted providers and verified configuration.
compliance:readiness
Tenant resolution, scoped player and brand data, configurable features, per-brand policy and platform administration. Sports odds and some trading exposure are deliberately shared.
TenantIsolationTest.php; TenantOwnershipTest.php
Player management, withdrawals, games, promotions, audit, reporting and platform operations. Staff access is evaluated through a guided session.
AdminCapabilityHardeningTest.php; AdminWriteAuditCoverageTest.php
Segmentation, campaigns, promotions, affiliate workflows and loyalty features. Suppression and permissions must be evaluated with the operator configuration.
docs/marketing-spec/05-feature-crm.md
Regulatory and management-information reporting, flexible breakdowns, bet search and CSV exports. Reports require operator review for the actual jurisdiction and regulatory submissions.
backend/app/Services/Reporting/
Affiliate attribution and commission workflows, with NGR-based calculation described in the product evidence. Commercial rates and contractual settlement are operator-specific.
backend/app/Services/Affiliates/AffiliateService.php
Loyalty and gamification services support retention mechanics and configurable player progression. Customer rules, disclosures and exclusions remain part of acceptance.
backend/app/Services/Loyalty/; backend/app/Services/Gamification/
Data-driven promotion and bonus workflows alongside CRM segmentation. Terms, eligibility and wagering conditions require a defined operator configuration.
backend/app/Services/Promotions/
Brand-bound integration access, scopes, rate limiting, revocation and idempotency support for external clients. Review money-moving access and key ownership before deployment.
backend/app/Services/Partner/; docs/marketing-spec/09-feature-developer.md
A virtual racing engine provides demonstration capability. It is distinct from a contracted live racing feed and remains within the applicable game testing scope.
backend/app/Services/Virtual/VirtualRacingEngine.php
Tournament, pooled jackpot and shared-game workflows exist alongside the player wallet. Availability and approval depend on the customer launch scope.
docs/marketing-spec/04-feature-casino.md
An optional assistant can draft segmentation proposals. A configured model service and validation are required; generated proposals do not replace operator review or control enforcement.
backend/app/Services/Ai/SegmentAssistant.php
335 documented API operations, an OpenAPI specification, 43 front-end widgets, ten skin presets and four interface locales in the recorded inventory.
docs/openapi.json; sites/ledgerfield/stats.json
Player, operator and sales app code against the same API. Build, signing, device acceptance and distribution status must be confirmed for each customer release.
mobile/README.md
Game/RNG testing, licensing decisions, an ISO 27001 programme and a SOC 2 examination are separate workstreams. No certificate or assurance report is claimed.
docs/RTS-MAP.md; ISO; AICPA
Game implementation scope
30 game controller entry points in the current repository, excluding the shared active-round recovery controller. A controller is an implementation boundary, not necessarily a unique commercial title. The demo lobby may contain several titles using an engine.
Availability varies by demo and configuration. These in-house implementations require the applicable independent maths, RNG, fairness and integration testing before an authorised real-money release.
Read the status correctly
Code and supporting repository evidence exist. Customer configuration, independent assessment and operational acceptance may still be required.
A contract or adapter is present, but the commercial provider connection has not been established and accepted for launch.
A regulator, test house, certification body or independent auditor must determine the outcome. Code cannot grant that status.
Help take the engine to market
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.