# Altenar procurement pack

Review path: /review/altenar

Primary procurement model: Sportsbook 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 | 6 |
| Product responsibility kinds | Sportsbook · Trading & risk · Player account management · Managed services · Omni-channel |
| Recorded permission markets | Alberta · Denmark · Malta (MGA) · UK (UKGC) |
| Recorded permission kinds | B2B supplier approval |
| Pricing transparency | Not recorded |
| Operational history | Incident history unavailable for a complete count |
| Included deployment records | 1 |
| 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 |
| White-label operating platform | White-label |

## Product and responsibility map

| ID | Product or decision subject | Kind | State | Recorded position | Responsibility | Boundary | Accept when |
|---|---|---|---|---|---|---|---|
| product:altenar:sportsbook | Sportsbook Module · Sportsbook | Sportsbook | recorded | Sportsbook Module is recorded for Altenar 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:altenar:trading-risk | Trading & Risk · Trading & risk | Trading & risk | recorded | Trading & Risk is recorded for Altenar as trading & risk. The record establishes the named product-to-provider relationship only. | Price, limit, exposure, suspension and trader-decision controls assigned to the named module or service. | Feed independence, profitability, automatic liability protection, staffing level or market coverage. | Price-and-exposure scenarios covering limits, overrides, suspension, escalation, audit history and loss controls. |
| product:altenar:player-account-management | Integrated PAM · Player account management | Player account management | recorded | Integrated PAM is recorded for Altenar 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:altenar:managed-services | White-label Sportsbook · Managed services | Managed services | recorded | White-label Sportsbook is recorded for Altenar as managed services. The record establishes the named product-to-provider relationship only. | A defined operational function performed by people on behalf of the buyer or platform operation. | Transferred accountability, continuous coverage, decision authority, performance level or inclusion in base fees. | A service RACI with hours, decision rights, queues, handover, quality controls, audit trail and exit assistance. |
| product:altenar:omni-channel | Retail Solution · Omni-channel | Omni-channel | recorded | Retail Solution is recorded for Altenar as omni-channel. The record establishes the named product-to-provider relationship only. | State continuity and controlled interaction between named retail and digital channels. | A shared wallet, shared identity, regulatory approval, retail hardware scope or failure isolation. | Cross-channel identity, balance, loyalty, transaction, outage-isolation and reconciliation scenarios. |

## Five priority questions and acceptance gates

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

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: Altenar: 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: Altenar: 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: Altenar: 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. WL-04 — Control operations

- Procurement context: White-label operating platform
- Current state: unknown
- Recorded position: Altenar: Anti-fraud is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Can AML, fraud, responsible-gambling, payments, safer-gambling and reporting teams operate one coherent control framework?
- Request: Control ownership; thresholds; case workflow; data access; decision timing; reporting calendar; audit logs; breach and regulator-notification procedure.
- Accept when: Controls are tested on the proposed brand and products, material cases remain visible, and escalation and reporting duties are contractually allocated.
- Stop when: A regulated control is delegated without buyer visibility, auditable decisions, response commitments or a lawful responsibility allocation.
- Contract destination: AML, safer-gambling, payments and reporting schedules

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

### 5. TK-04 — Launch product set

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: Altenar: Live casino is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Are the exact casino, live, sportsbook, bonus, CRM, fraud and reporting modules production-ready for this configuration?
- Request: Versioned module inventory; environment and market availability; configuration register; certification delta; acceptance scripts and results.
- Accept when: Every required module and substitute integration passes the buyer's exact market, version, data-flow and control tests in the proposed environment.
- Stop when: A launch-critical module is roadmap, demo-only, tied to another product version, or dependent on an integration with no accepted owner and test result.
- Contract destination: Product scope and acceptance schedule

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