# NuxGame procurement pack

Review path: /review/nuxgame

Primary procurement model: White-label operating platform

This is an editable procurement record, not a readiness score, contract commitment, market permission or launch approval.

## Recorded position

| Field | Current position |
|---|---|
| Named product or module records | 9 |
| Product responsibility kinds | Casino platform · Sportsbook · Game aggregator · Front-end & apps · Affiliate system · Compliance |
| Recorded permission markets | Not confirmed |
| Recorded permission kinds | Not confirmed |
| Pricing transparency | Not recorded |
| Operational history | Incident history unavailable for a complete count |
| Included deployment records | 0 |
| Included current-live deployment records | 0 |
| Interpretation boundary | These are records included in this review. Counts, zero values and empty lists do not establish absence, package inclusion, the supplying entity, market availability or a current deployment. |

## Applicable procurement scopes

| Scope | Inclusion basis |
|---|---|
| Turnkey iGaming platform | Turnkey |
| Modular PAM / API platform | PAM / API |
| Sportsbook platform | Recorded sportsbook capability |
| Casino game aggregator | Game aggregator |
| White-label operating platform | White-label |

## Product and responsibility map

| ID | Product or decision subject | Kind | State | Recorded position | Responsibility | Boundary | Accept when |
|---|---|---|---|---|---|---|---|
| product:nuxgame:casino-platform | Crypto Casino · Casino platform | Casino platform | recorded | Crypto Casino is recorded for NuxGame as casino platform. The record establishes the named product-to-provider relationship only. | The casino product layer joining player sessions, lobby, games, account services and operational controls. | Title approval, market availability, wallet authority, content ownership or inclusion of adjacent modules. | An end-to-end casino session and responsibility map covering launch, play, interruption, settlement and recovery. |
| product:nuxgame:sportsbook | Sports Betting API · Sportsbook | Sportsbook | recorded | Sports Betting API is recorded for NuxGame as sportsbook. The record establishes the named product-to-provider relationship only. | The bet and market lifecycle assigned to the named sportsbook product, including its connected operating components. | Trading ownership, event volume, PAM inclusion, market permission, latency or operator-specific configuration. | Bet-state tests covering offer, acceptance, rejection, cash-out, cancellation, settlement, correction and resettlement. |
| product:nuxgame:game-aggregator | Casino API · Game aggregator | Game aggregator | recorded | Casino API is recorded for NuxGame as game aggregator. The record establishes the named product-to-provider relationship only. | The integration and routing layer between an operator platform and multiple game-content connections. | A current title count, commercial entitlement, certification, market availability or one uniform integration path. | A supplier-title-market route matrix with launch, rollback, round-state and reconciliation acceptance. |
| product:nuxgame:front-end-apps | Telegram Casino · Front-end & apps | Front-end & apps | recorded | Telegram Casino is recorded for NuxGame as front-end & apps. The record establishes the named product-to-provider relationship only. | The player-facing presentation, navigation and interaction layer for the named channel. | Backend system authority, device coverage, accessibility, security or parity between web and native clients. | A supported-browser and device matrix with accessibility, degraded-mode, session and release-rollback tests. |
| product:nuxgame:affiliate-system | Affiliate & Agent System · Affiliate system | Affiliate system | recorded | Affiliate & Agent System is recorded for NuxGame as affiliate system. The record establishes the named product-to-provider relationship only. | Partner attribution, account structure, commission logic and partner reporting. | Tracking accuracy, payment entitlement, traffic compliance or the treatment of reversals and closed accounts. | Attribution and commission reconciliation cases covering adjustments, reversals, disputes and partner closure. |

## Five priority questions and acceptance gates

### 1. TK-01 — Permission chain

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: NuxGame: no active credential relationship is recorded for this profile. This is not a finding that permission is absent; confirm the exact entity, product and market route before award.
- Question: Can the exact supplier entity, product and operating arrangement support every proposed market and vertical?
- Request: Current authority records; entity and product map; operator dependencies; term dates; approval and change-control plan.
- Accept when: Each launch entity, product and market maps to a current permission or to a buyer-owned approval action with an accountable owner and stop condition.
- Stop when: Any launch-critical entity, product or permission route remains assumed, belongs to an unconnected group company, or cannot be completed before the corresponding launch gate.
- Contract destination: Regulatory responsibility and conditions schedule

| Owner | Supplier response | Exception | Sign-off |
|---|---|---|---|
|  |  |  |  |

### 2. PAM-02 — Interface contract

- Procurement context: Modular PAM / API platform
- Current state: unknown
- Recorded position: NuxGame: Headless API is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Can the PAM operate as a modular service across the required synchronous APIs, events, exports and administrative workflows?
- Request: Versioned specifications; event catalogue; idempotency and ordering rules; error model; limits; sandbox parity; deprecation policy; sample logs.
- Accept when: Buyer tests cover success, duplicate, late, out-of-order, timeout, partial-failure and version-change paths with deterministic recovery.
- Stop when: A critical state transition depends on a private manual process, undocumented interface, non-replayable event or change policy the buyer cannot test.
- Contract destination: API, event and lifecycle schedule

| Owner | Supplier response | Exception | Sign-off |
|---|---|---|---|
|  |  |  |  |

### 3. SB-04 — Feed and event integrity

- Procurement context: Sportsbook platform
- Current state: unknown
- Recorded position: NuxGame: incident history unavailable for a complete count. This does not establish poor reliability.
- Question: How are event identity, feed conflict, latency, suspension, correction and abandonment controlled across suppliers?
- Request: Feed inventory; event mapping; freshness thresholds; conflict precedence; monitoring; suspension tests; correction workflow and audit output.
- Accept when: The system detects stale or conflicting data, suspends deterministically, records overrides and reconciles every correction to bets and balances.
- Stop when: A feed failure or event-identity conflict can continue accepting bets without a bounded automated or supervised control.
- Contract destination: Data feeds, integrity and monitoring schedule

| Owner | Supplier response | Exception | Sign-off |
|---|---|---|---|
|  |  |  |  |

### 4. AGG-04 — Financial reconciliation

- Procurement context: Casino game aggregator
- Current state: unknown
- Recorded position: NuxGame: Reporting & BI is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Do the operator, aggregator and studio agree on rounds, stakes, wins, jackpots, bonuses, refunds, adjustments and settlement periods?
- Request: Transaction-level export; daily control totals; jackpot and bonus liability; unmatched-item ageing; correction entries; invoice-to-ledger reconciliation.
- Accept when: Independent buyer totals reconcile all three layers and every variance retains source transaction, reason, owner, action and closure evidence.
- Stop when: The buyer cannot independently reconstruct GGR and liabilities or resolve a variance below provider-level aggregate reports.
- Contract destination: Financial records, settlement and invoice schedule

| Owner | Supplier response | Exception | Sign-off |
|---|---|---|---|
|  |  |  |  |

### 5. WL-03 — Market and brand perimeter

- Procurement context: White-label operating platform
- Current state: unknown
- Recorded position: NuxGame: no bounded deployment record is included in this review. This does not mean that the provider has no deployments.
- Question: Are domain, app, brand, product, language, payment, marketing and geographic boundaries approved and technically enforced?
- Request: Brand-market matrix; domain and app inventory; product eligibility; geo rules; payment routes; marketing approvals; release and change controls.
- Accept when: Only approved combinations can be configured or exposed, and every change requires the correct supplier, buyer and regulatory approvals.
- Stop when: A brand can accept players, payments or gameplay outside its approved entity, market, product or distribution boundary.
- Contract destination: Brand, territory, product and distribution schedule

| Owner | Supplier response | Exception | Sign-off |
|---|---|---|---|
|  |  |  |  |