# EveryMatrix procurement pack

Review path: /review/everymatrix

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 · Payments · Game aggregator · Sportsbook · Affiliate system · Live casino · Lottery |
| Recorded permission markets | Denmark · Malta (MGA) · Michigan · New Jersey · Pennsylvania · UK (UKGC) · West Virginia |
| Recorded permission kinds | B2B supplier approval · Product / transaction approval |
| Pricing transparency | Not recorded |
| Operational history | Defined incident history |
| Included deployment records | 3 |
| 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 |

## Product and responsibility map

| ID | Product or decision subject | Kind | State | Recorded position | Responsibility | Boundary | Accept when |
|---|---|---|---|---|---|---|---|
| product:everymatrix:player-account-management | GamMatrix · Player account management | Player account management | recorded | GamMatrix is recorded for EveryMatrix 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:everymatrix:payments | Payments · Payments | Payments | recorded | Payments is recorded for EveryMatrix as payments. The record establishes the named product-to-provider relationship only. | Cashier or payment-orchestration state, connector routing and payment lifecycle handling in the named module. | A PSP contract, funds custody, supported methods, market availability, approval rate or settlement ownership. | Payment-state tests for authorization, failure, retry, refund, reversal, chargeback, settlement and reconciliation. |
| product:everymatrix:game-aggregator | CasinoEngine · Game aggregator | Game aggregator | recorded | CasinoEngine is recorded for EveryMatrix 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:everymatrix:sportsbook | OddsMatrix · Sportsbook | Sportsbook | recorded | OddsMatrix is recorded for EveryMatrix 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:everymatrix:affiliate-system | PartnerMatrix · Affiliate system | Affiliate system | recorded | PartnerMatrix is recorded for EveryMatrix 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: EveryMatrix: 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: EveryMatrix: 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-05 — Player and risk controls

- Procurement context: Sportsbook platform
- Current state: unknown
- Recorded position: EveryMatrix: Anti-fraud is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Do player limits, exclusions, affordability, fraud, AML and trading-risk interventions work across pre-bet and in-play paths?
- Request: Control matrix; decision timing; limit hierarchy; acknowledgement events; fail-closed tests; manual-action permissions; audit and report samples.
- Accept when: Every mandatory control applies before acceptance within its required time bound and remains enforceable during partial platform failure.
- Stop when: A restricted player or disallowed wager can be accepted because risk, PAM and sportsbook control ownership or timing is unresolved.
- Contract destination: Player protection, AML and risk-control schedule

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

### 4. AGG-06 — Commercial chain

- Procurement context: Casino game aggregator
- Current state: unknown
- Recorded position: EveryMatrix: 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. PAM-05 — Change isolation

- Procurement context: Modular PAM / API platform
- Current state: partial
- Recorded position: EveryMatrix: this review includes 3 bounded deployment records, but none is classified as both current and live. This review does not establish that no live deployment exists.
- Question: Can either party upgrade a component without silently breaking events, reports, integrations or control semantics?
- Request: Compatibility policy; contract tests; schema registry; feature flags; release rings; rollback; end-of-life notices; dependency inventory.
- Accept when: Backward-compatibility and breaking-change rules are automated, release evidence is visible, and rollback preserves transaction and audit continuity.
- Stop when: The supplier can impose a breaking interface or data change without a tested migration path, adequate notice and buyer-controlled release gate.
- Contract destination: Change, compatibility and release schedule

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