# Soft2Bet procurement pack

Review path: /review/soft2bet

Primary procurement model: White-label operating 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 | 7 |
| Product responsibility kinds | Player account management · Sportsbook · Payments · Bonus & loyalty · CRM & engagement · Front-end & apps · Engagement tool |
| Recorded permission markets | Malta (MGA) · Ontario |
| Recorded permission kinds | Operator licence |
| 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 |
| 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:soft2bet:player-account-management | PAM · Player account management | Player account management | recorded | PAM is recorded for Soft2Bet 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:soft2bet:sportsbook | Turnkey Sportsbook · Sportsbook | Sportsbook | recorded | Turnkey Sportsbook is recorded for Soft2Bet 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:soft2bet:payments | Payments & KYC/Risk · Payments | Payments | recorded | Payments & KYC/Risk is recorded for Soft2Bet 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:soft2bet:bonus-loyalty | Bonus Engine · Bonus & loyalty | Bonus & loyalty | recorded | Bonus Engine is recorded for Soft2Bet as bonus & loyalty. The record establishes the named product-to-provider relationship only. | Eligibility, issuance, wagering state, expiry, cancellation and promotional liability. | That a promotion is permitted, its rules are correctly configured or its liability reconciles to the wallet. | Promotion state-transition tests and a bonus-liability reconciliation for award, play, expiry and reversal. |
| product:soft2bet:crm-engagement | CRM · CRM & engagement | CRM & engagement | recorded | CRM is recorded for Soft2Bet 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. |

## Five priority questions and acceptance gates

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

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: Soft2Bet: 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: Soft2Bet: 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: Soft2Bet: 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-03 — Market and brand perimeter

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

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

- Procurement context: Turnkey iGaming platform
- Current state: unknown
- Recorded position: Soft2Bet: 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 |
|---|---|---|---|
|  |  |  |  |