# Delasport procurement pack

Review path: /review/delasport

Primary procurement model: Modular PAM / API 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 | 8 |
| Product responsibility kinds | Player account management · Casino platform · Sportsbook · Managed services · Affiliate system · Bonus & loyalty · Engagement tool · Other |
| Recorded permission markets | Alberta · Denmark · Malta (MGA) · Ontario · UK (UKGC) |
| Recorded permission kinds | B2B supplier approval |
| 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 | SaaS / PAM category · 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:delasport:player-account-management | Orbit · Player account management | Player account management | recorded | Orbit is recorded for Delasport 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:delasport:casino-platform | DelaCasino · Casino platform | Casino platform | recorded | DelaCasino is recorded for Delasport 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:delasport:sportsbook | DelaSports · Sportsbook | Sportsbook | recorded | DelaSports is recorded for Delasport 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:delasport:managed-services | Managed Services · Managed services | Managed services | recorded | Managed Services is recorded for Delasport 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:delasport:affiliate-system | Agent System · Affiliate system | Affiliate system | recorded | Agent System is recorded for Delasport 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-03 — Wallet and control authority

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: Delasport: 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: Delasport: 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: Delasport: 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-06 — Commercial chain

- Procurement context: Casino game aggregator
- Current state: unknown
- Recorded position: Delasport: 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-03 — Market and brand perimeter

- Procurement context: White-label operating platform
- Current state: unknown
- Recorded position: Delasport: 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 |
|---|---|---|---|
|  |  |  |  |