Solutions / Bonus Engine

Promotions with a budget that actually stops.

Versioned programmes authored under dual control, wagering computed from settled bets, and every grant executed through the wallet rather than by this service.

Programmes Versioned
Authoring Dual control
Budget Ledger-enforced
What it owns

Bonus Engine, precisely

01

Programme templates

Deposit match, reload, free rounds, no-deposit and bonus shop — each versioned and signed off by two named people before it can go live.

02

A running grant keeps its terms

Changing a programme today never rewrites what a player already accepted. The grant carries the version it was issued under.

03

Wagering from real settlement

Progress is computed from settled bet funding splits, deduplicated by event and safe to replay out of order.

04

Caps that bind

Per player, per campaign and per day. One leaked code cannot empty a budget overnight.

05

Withdrawal impact

The cash desk asks this service what a payout does to an active bonus and receives one named, recorded answer.

06

Clawback

When a funding deposit is reversed, the bonus it paid for is resolved deliberately instead of quietly surviving.

Contracts it exposes
CommandsGrantBonus · ConvertBonus · ForfeitBonus · ResolveClawback
ReadsEvaluateWithdrawalImpact · GetGrant
EventsBonusGranted · BonusConverted · BonusForfeited · WageringProgressed
What it never does
Hold bonus balance itself
Pay a player directly
Grant value the wallet has not authorised

Every module on this platform is defined as much by what it is forbidden to do as by what it owns. That is what makes a boundary auditable instead of aspirational.

A campaign spends its budget and never more — enforced by the same ledger that holds the money, not by this service’s own arithmetic.

See it running

Every module here surfaces as screens an operator uses on a Monday. Ask for a walkthrough of the ones that decide your week.