# BetConstruct procurement pack

Review path: /review/betconstruct

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 | Player account management · Sportsbook · Game aggregator · CRM & engagement · Front-end & apps · Anti-fraud · Affiliate system · Live casino · Odds feed |
| Recorded permission markets | Denmark · Malta (MGA) · UK (UKGC) |
| Recorded permission kinds | B2B supplier approval · Operator licence |
| Pricing transparency | Not recorded |
| Operational history | Defined incident history |
| 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:betconstruct:player-account-management | SpringBME · Player account management | Player account management | recorded | SpringBME is recorded for BetConstruct as player account management. The record establishes the named product-to-provider relationship only. | Player-account identity, lifecycle, authentication, profile state and the account services assigned to the PAM. | Wallet authority, KYC coverage, bonus ownership, omnichannel continuity or inclusion of every adjacent service. | An account-state and data-authority model with registration, restriction, closure, recovery, audit and migration tests. |
| product:betconstruct:sportsbook | Spring Sportsbook · Sportsbook | Sportsbook | recorded | Spring Sportsbook is recorded for BetConstruct 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:betconstruct:game-aggregator | Casino Platform · Game aggregator | Game aggregator | recorded | Casino Platform is recorded for BetConstruct 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:betconstruct:crm-engagement | CRM & CRM AI · CRM & engagement | CRM & engagement | recorded | CRM & CRM AI is recorded for BetConstruct as crm & engagement. The record establishes the named product-to-provider relationship only. | Audience state, journey orchestration, messaging triggers, suppression and campaign measurement. | Consent, lawful contact, deliverability, bonus correctness or a complete customer record. | Journey tests covering consent, suppression, timezone, channel failure, re-entry and measurement reconciliation. |
| product:betconstruct:front-end-apps | SpringBuilder X · Front-end & apps | Front-end & apps | recorded | SpringBuilder X is recorded for BetConstruct 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. |

## Five priority questions and acceptance gates

### 1. TK-03 — Wallet and control authority

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: BetConstruct: Reporting & BI is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Which system is authoritative for identity, balances, bonus liability, limits, exclusions, transaction history and regulatory reporting?
- Request: System-of-record map; wallet sequences; control precedence; reconciliation output; access model; witnessed failure and replay tests.
- Accept when: One authority is named for every state, conflict resolution is deterministic, and debit, credit, rollback, limit and exclusion tests reconcile end to end.
- Stop when: Competing systems can independently alter player eligibility or financial state without a deterministic authority, audit trail and reconciliation path.
- Contract destination: Architecture, controls and reconciliation schedules

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

### 2. PAM-02 — Interface contract

- Procurement context: Modular PAM / API platform
- Current state: unknown
- Recorded position: BetConstruct: 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-06 — Peak resilience and economics

- Procurement context: Sportsbook platform
- Current state: unknown
- Recorded position: BetConstruct: no bounded deployment record is included in this review. This does not mean that the provider has no deployments.
- Question: Can the proposed service and price survive event peaks, feed disruption, settlement bursts and managed-trading escalation?
- Request: Peak-load profile; capacity and failover tests; incident history; recovery objectives; support model; complete price basis and event-volume scenarios.
- Accept when: Capacity, recovery, support and price are tested against buyer volumes and event shapes, with measurable service levels and remedies.
- Stop when: The service has no accepted peak-load boundary, recovery evidence or comparable commercial basis for the proposed event and bet volumes.
- Contract destination: Capacity, SLA, support and charges schedules

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

### 4. AGG-06 — Commercial chain

- Procurement context: Casino game aggregator
- Current state: unknown
- Recorded position: BetConstruct: commercial terms are not recorded for this profile. This does not imply a price level.
- Question: Are aggregator fees, studio charges, minimums, jackpots, promotional tools, certification, data and exit treatment comparable?
- Request: Per-studio and platform rate card; calculation basis; minimums; pass-throughs; excluded tools; content removal; data retention; direct-integration exit plan.
- Accept when: Every scenario reconciles invoice logic to wallet and game data, while content continuity, data access and transition rights survive termination.
- Stop when: A material studio charge, calculation basis, minimum, liability, content-removal consequence or exit restriction remains undefined.
- Contract destination: Content charges, settlement and exit schedules

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

### 5. WL-05 — Data and brand portability

- Procurement context: White-label operating platform
- Current state: partial
- Recorded position: BetConstruct: this decision requires buyer-controlled data and brand portability documents before award.
- Question: What can the buyer retain and migrate if it changes platform, licence route or service model?
- Request: Ownership matrix; export schema; player consents; domain and app rights; creative and configuration inventory; migration rehearsal; deletion certificates.
- Accept when: The buyer can lawfully transfer the agreed brand assets and complete player, balance, control, transaction and audit records within tested time bounds.
- Stop when: Termination strands the brand or makes material player, balance, control or transaction history unavailable, unusable or legally non-transferable.
- Contract destination: IP, data rights, migration and exit schedule

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