# Bragg Gaming Group procurement pack

Review path: /review/bragg

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 | 5 |
| Product responsibility kinds | Game aggregator · Game content · Player account management · CRM & engagement · Other |
| Recorded permission markets | Alberta · Connecticut · Delaware · Malta (MGA) · Michigan · Ontario · Pennsylvania · UK (UKGC) · West Virginia |
| 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 | PAM / API |
| 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:bragg:game-aggregator | Bragg Hub · Game aggregator | Game aggregator | recorded | Bragg Hub is recorded for Bragg Gaming Group 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:bragg:game-content | Bragg Studios · Game content | Game content | recorded | Bragg Studios is recorded for Bragg Gaming Group 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. |
| product:bragg:player-account-management | Bragg PAM · Player account management | Player account management | recorded | Bragg PAM is recorded for Bragg Gaming Group 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:bragg:crm-engagement | Fuze · CRM & engagement | CRM & engagement | recorded | Fuze is recorded for Bragg Gaming Group 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:bragg:other | Bragg RGS · Other | Other | recorded | Bragg RGS is recorded for Bragg Gaming Group as other. The record establishes the named product-to-provider relationship only. | Only the exact named scope recorded for the product; no adjacent responsibility is inferred. | Membership of another module class, package inclusion, market availability or an unstated system authority. | A signed scope boundary naming inputs, outputs, system authority, dependencies, exclusions and acceptance cases. |

## Five priority questions and acceptance gates

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

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: Bragg Gaming Group: 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: Bragg Gaming Group: 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. AGG-05 — Failure containment

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

### 4. TK-06 — Economics and exit

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: Bragg Gaming Group: commercial terms are not recorded for this profile. This does not imply a price level.
- Question: Does the commercial perimeter cover every module, environment, third party, volume step, managed service, migration and exit event?
- Request: Three normalized demand scenarios; complete rate card; pass-through register; indexation; minimums; change rates; exit inventory and priced transition plan.
- Accept when: All proposals reconcile to the same scope and demand assumptions, and data extraction, transition assistance, residual fees and termination events are enforceable.
- Stop when: A material charge, revenue basis, third-party dependency, minimum commitment, data extraction right or termination cost remains undefined at award.
- Contract destination: Charges, data portability and exit schedules

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

### 5. PAM-04 — Cross-supplier controls

- Procurement context: Modular PAM / API platform
- Current state: unknown
- Recorded position: Bragg Gaming Group: Anti-fraud is not confirmed for this profile. This is not a statement that the capability is unavailable.
- Question: Do limits, exclusions, AML actions, fraud decisions and responsible-gambling controls propagate across every connected product?
- Request: Control precedence; event timing; fail-closed rules; product acknowledgements; exception queues; audit output; multi-product test results.
- Accept when: A control change reaches and is enforced by every required product within an agreed bound, with deterministic treatment during dependency failure.
- Stop when: A launch product can accept activity after a mandatory player restriction because propagation, acknowledgement or fail-closed behaviour is unresolved.
- Contract destination: Player-protection and financial-crime control schedule

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