Operations Guide · 2026

Casino bonus engine and wagering rules: how to configure promotions that stay compliant

Since 19 January 2026, wagering on bonuses in Great Britain has been capped at 10x. Bonuses must also stay within one product and keep their terms once a player qualifies. Those three rules make a useful test for any bonus engine, whatever market you serve. This guide covers how promotions are built, how wagering is counted and how to keep every change on the record.

What a bonus engine has to handle

A bonus engine turns a promotion into rules the platform enforces on every bet. It decides who is eligible, what they receive, how the bonus is released and when it lapses. Most operators run four basic types.

• Deposit match: bonus funds credited against a qualifying deposit, up to a set cap.
• Free spins: a set number of spins on named games at a fixed stake, with winnings usually paid as bonus funds.
• Free bets: a sportsbook stake credited to the player, usually without the stake returned on a win.
• Cashback: part of net losses over a period, returned as cash or bonus funds.

Each type needs the same building blocks: eligibility, wagering, contribution, max bet, expiry and product scope. When these live in one template rather than in campaign notes, they can be checked before anything goes live.

How wagering is counted

A wagering requirement is a multiplier applied to a base, usually the bonus amount and sometimes bonus plus deposit. The player must bet that total before bonus winnings can be withdrawn. Store the base explicitly in the template, because the same multiplier means very different things on different bases.

Not every bet counts equally. Game contribution sets how much of each stake goes towards the requirement. Slots often count in full, while table games, live casino and low-risk bets often count partly or not at all. The engine needs a game category for every round to apply this. Through the IGP casino API, round-level data arrives in one format from every provider, as described in casino API reporting and reconciliation.

Maximum bet while wagering limits the stake per round or bet while a bonus is active. Enforce it at the moment of the bet, with a clear message, rather than voiding winnings afterwards. A rejected bet is easier to explain to a player and to a regulator.

Expiry, product scope and per-market rule sets

Expiry needs two clocks: how long a player has to claim the bonus, and how long to complete wagering. Show both in the player account. Decide in advance what happens to bonus funds and unused free spins when time runs out, and write it into the terms.

Product scope says where a bonus can be used and where its wagering counts. A single-product bonus stays in casino or in sportsbook. A cross-product bonus spans both, which some markets allow and others do not. When casino and sportsbook share one wallet, tag every bonus balance by product.

The cleanest set-up is a rule set per market. The player’s licensed market selects the multiplier ceiling, eligible products, contribution table, max bet and expiry limits. On a white label casino, which runs on a licence that is already live, those rule sets must also match the licence holder’s conditions.

Great Britain from 19 January 2026

The rules that took effect in Great Britain on 19 January 2026 translate directly into engine settings. They apply to bonus money, free bets and free spins alike.

Before you set the ceiling, check how the regulator’s own wording defines the base for 10x.

Terms that stay fixed, and a full audit trail

The GB rule on qualifying faster than expected targets a familiar habit: tightening a promotion once it performs too well. In the engine, the answer is versioning. Every template change creates a new version, and each player’s bonus record keeps the version that applied when they opted in or qualified.

An audit trail sits on top. For every change, log who made it, when, the old and new values and how many players were active on the earlier version. Keep the same log for manual credits, cancellations and expiries. Feed bonus events into the same reports as wallet and game data, so finance and compliance can reconcile bonus balances against real-money activity.

When promotions must stop at once

Bonus rules can change overnight for reasons outside your control. On 8 October 2026, the Federal Court of São Paulo granted Stake a partial preliminary injunction. It may operate in Brazil until 25 October 2026, the licence expiry date set by a provisional measure. Its 12 conditions include no new promotions or acquisition bonuses and guaranteed withdrawals. The ruling applies only to Stake.

For a bonus engine, the lesson is a stop switch by market and by brand. It should end new opt-ins and acquisition offers at once, while existing balances, withdrawals and records stay intact. Test it before you need it.

Checklist before a promotion goes live

• The template sits in the right market rule set, with multiplier and base stated.
• Contribution, max bet and both expiry clocks are set and visible to the player.
• The bonus is single-product wherever the market requires it.
• Terms are versioned, and the version is stored on each player record.
• Changes, manual credits and cancellations are logged.
• The stop switch for the market has been tested.

Sources: UK Gambling Commission rules effective 19 January 2026, as reported by OLBG; SBC Americas, 8 October 2026.

Frequently asked questions