QA for iGaming: match-day releases without surprises

Betting and gaming platforms live by the event calendar: a release cannot be postponed because the match will not be. We build checks around that rhythm — regression a day before launch, payment flows on real providers, promo materials against regulator rules.

How iGaming differs from a regular product

Three traits break the standard approach to testing. First, time: peak load and peak releases coincide with the sports schedule, and an error that would cost one ticket in a regular SaaS here costs an evening's revenue. Second, money: every flow from deposit to withdrawal goes through external payment providers, each with its own limits, timeouts and failure behaviour. Third, regulation: copy, buttons and creatives must meet the requirements of a specific market, and that has to be checked before publication, not after a complaint.

What we check

• Registration and verification: all KYC branches, age and geography restrictions, retries, account recovery.
• Deposits and withdrawals: every provider, minimum and maximum amounts, cancellation, timeouts, provider-side failure behaviour, double charges.
• Promotion mechanics: promo codes, free bets, bonuses with wagering conditions — correct crediting, validity period, no repeat use.
• Line and bet slip: adding and removing events, odds changing mid-flow, payout calculation, stake limits.
• Live scenarios: delays, event cancellations, result recalculation.
• Promo pages and creatives: mandatory disclaimers, age labels, prohibited wording, compliance with platform rules and the market's regulator.
• Load: a profile from logs of past events, peak scenarios with target thresholds for p95 and error rate.

The pre-promotion cycle

1. A week before: we receive the promotion plan and build or update the regression suite for its mechanics and languages.
2. Three days before: a run on the test environment, LQA of promo materials in the interface in all market languages, creative checks against the regulator checklist.
3. A day before: regression on pre-production on iOS, Android and major browsers, a report with prioritized defects in the team chat.
4. Launch day: on duty for the first hours, quick checks of hot flows after hotfixes.

Localization and support for operators

Operators rarely enter a single market, and each market has its own languages, currencies and rules. We localize promo materials with LQA in the interface so clipped strings and wrong amount formats never reach players. We take the first line of support during promotion peaks, when requests multiply, and run user content moderation and creative checks against a log — for disputes with platforms and regulators.

• Russian, English and Uzbek in-house; other languages through partners under our checklist.
• A separate requirements checklist for each market: mandatory disclaimers, age labels, wording restrictions.
• Support on peak days with escalation of financial questions to your side under the playbook.