# Pariplay procurement pack

Review path: /review/pariplay

Primary procurement model: Casino game aggregator

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 | 1 |
| Product responsibility kinds | Game content |
| Recorded permission markets | Alberta · Denmark · Malta (MGA) · Michigan · New Jersey · Ontario · Pennsylvania · UK (UKGC) · West Virginia |
| Recorded permission kinds | B2B supplier approval · Product / transaction 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 |
|---|---|
| Casino game aggregator | Game aggregator category · Game aggregator |

## Product and responsibility map

| ID | Product or decision subject | Kind | State | Recorded position | Responsibility | Boundary | Accept when |
|---|---|---|---|---|---|---|---|
| product:pariplay:game-content | Wizard Games · Game content | Game content | recorded | Wizard Games is recorded for Pariplay as game content. The record establishes the named product-to-provider relationship only. | The named portfolio or content-production relationship recorded for the provider. | Catalogue size, title ownership, certification, operator entitlement or availability in a specific jurisdiction. | A versioned title manifest carrying supplier, game ID, market, certification, RTP configuration and release state. |
| decision:pariplay:agg-01 | Permission route | Permission route | recorded | Pariplay: active recorded permission relationships cover Alberta, Denmark, Malta (MGA), Michigan, New Jersey, Ontario, Pennsylvania, UK (UKGC), West Virginia under B2B supplier approval, Product / transaction approval. They do not transfer permission to the buyer or prove the proposed launch configuration. | Can each proposed supplier, studio, game and aggregator role be used by the operator entity in the target market? | This row is a procurement starting point, not proof that the proposed operating configuration is accepted. | Every enabled game version traces through the aggregator and studio entities to the required current permissions and operator release approval. |
| decision:pariplay:agg-05 | Operational history | Operational history | unknown | Pariplay: incident history unavailable for a complete count. This does not establish poor reliability. | Can one studio, game, region or protocol fail without disabling unrelated content or corrupting wallet state? | This row is a procurement starting point, not proof that the proposed operating configuration is accepted. | Failures are detected and isolated at the smallest safe scope, player and financial states remain consistent, and recovery is observable and rehearsed. |

## Five priority questions and acceptance gates

### 1. AGG-02 — Wallet protocol

- Procurement context: Casino game aggregator
- Current state: unknown
- Recorded position: Pariplay: PAM / core platform is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Is ledger authority, debit, credit, rollback, replay and open-round handling deterministic across every studio adapter?
- Request: Protocol versions; studio exception matrix; idempotency retention; sequence diagrams; open-round rules; failure, retry and rollback results.
- Accept when: Each adapter passes duplicate, timeout, late-result, rollback, resettlement and failover tests without an unmatched balance or round.
- Stop when: Any material studio path relies on unbounded retries, non-idempotent posting, silent balance correction or irrecoverable open rounds.
- Contract destination: Wallet, round-state and protocol schedule

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

### 2. AGG-03 — Release inventory

- Procurement context: Casino game aggregator
- Current state: unknown
- Recorded position: Pariplay: Live casino is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Can the buyer identify exactly which game binary, math, certificate, metadata, configuration and jurisdiction rule is live?
- Request: Immutable game/version IDs; certificates; RTP and configuration variants; release manifests; change notifications; disable and rollback workflow.
- Accept when: The live inventory reconciles to approved versions, changes are buyer-gated, and a single game or version can be disabled and rolled back safely.
- Stop when: The aggregator cannot produce a version-level live inventory or can change regulated game configuration without an accepted buyer release control.
- Contract destination: Game inventory, release and change schedule

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

### 3. AGG-04 — Financial reconciliation

- Procurement context: Casino game aggregator
- Current state: unknown
- Recorded position: Pariplay: 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 |
|---|---|---|---|
|  |  |  |  |

### 4. AGG-05 — Failure containment

- Procurement context: Casino game aggregator
- Current state: unknown
- Recorded position: Pariplay: incident history unavailable for a complete count. This does not establish poor reliability.
- Question: Can one studio, game, region or protocol fail without disabling unrelated content or corrupting wallet state?
- Request: Dependency topology; component health; isolation controls; circuit breakers; queue limits; studio-level incident history; recovery and replay tests.
- Accept when: Failures are detected and isolated at the smallest safe scope, player and financial states remain consistent, and recovery is observable and rehearsed.
- Stop when: A single dependency can create platform-wide content failure or financial uncertainty without a tested isolation and recovery path.
- Contract destination: Resilience, incident and recovery schedule

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

### 5. AGG-06 — Commercial chain

- Procurement context: Casino game aggregator
- Current state: unknown
- Recorded position: Pariplay: 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 |
|---|---|---|---|
|  |  |  |  |