# SOFTSWISS procurement pack

Review path: /review/softswiss

Primary procurement model: Turnkey iGaming 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 | 6 |
| Product responsibility kinds | Casino platform · Sportsbook · Game aggregator · Managed services · Affiliate system · Prediction markets |
| Recorded permission markets | Malta (MGA) |
| 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 |
| 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:softswiss:casino-platform | SOFTSWISS Casino Platform · Casino platform | Casino platform | recorded | SOFTSWISS Casino Platform is recorded for SOFTSWISS 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:softswiss:sportsbook | SOFTSWISS Sportsbook · Sportsbook | Sportsbook | recorded | SOFTSWISS Sportsbook is recorded for SOFTSWISS 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:softswiss:game-aggregator | SOFTSWISS Game Aggregator · Game aggregator | Game aggregator | recorded | SOFTSWISS Game Aggregator is recorded for SOFTSWISS 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:softswiss:managed-services | SOFTSWISS Managed Services · Managed services | Managed services | recorded | SOFTSWISS Managed Services is recorded for SOFTSWISS 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:softswiss:affiliate-system | Affilka by SOFTSWISS · Affiliate system | Affiliate system | recorded | Affilka by SOFTSWISS is recorded for SOFTSWISS 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: SOFTSWISS: 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. SB-04 — Feed and event integrity

- Procurement context: Sportsbook platform
- Current state: unknown
- Recorded position: SOFTSWISS: 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 |
|---|---|---|---|
|  |  |  |  |

### 3. AGG-06 — Commercial chain

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

### 4. SB-05 — Player and risk controls

- Procurement context: Sportsbook platform
- Current state: unknown
- Recorded position: SOFTSWISS: 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 |
|---|---|---|---|
|  |  |  |  |

### 5. SB-06 — Peak resilience and economics

- Procurement context: Sportsbook platform
- Current state: unknown
- Recorded position: SOFTSWISS: no bounded deployment record is included in this review. This does not mean that the provider has no deployments.
- Question: Can the proposed service and price survive event peaks, feed disruption, settlement bursts and managed-trading escalation?
- Request: Peak-load profile; capacity and failover tests; incident history; recovery objectives; support model; complete price basis and event-volume scenarios.
- Accept when: Capacity, recovery, support and price are tested against buyer volumes and event shapes, with measurable service levels and remedies.
- Stop when: The service has no accepted peak-load boundary, recovery evidence or comparable commercial basis for the proposed event and bet volumes.
- Contract destination: Capacity, SLA, support and charges schedules

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