The player terms, configuration, account history and financial record should all explain the same outcome.
Map the promotion before configuring it
Specify qualifying events, eligible players, award amount, wagering contribution, expiry and restrictions. Define the order in which cash and bonus funds are used and what happens when a player requests a withdrawal.
For illustration, if an eligible €10 stake contributes 20% toward a requirement, it contributes €2. The engine test should use the configured contribution rule, including excluded games and rounding. This example is not a recommended wagering condition or a claim that every market permits it.
Test the states after the award
| Case | What the test should establish |
|---|---|
| Qualifying event repeated | Whether it is the same event or a distinct eligible award |
| Excluded game used | The specified contribution and any permitted balance effect |
| Partial completion at expiry | The treatment of remaining bonus funds and related obligations |
| Withdrawal requested | The displayed condition and resulting account state |
| Promotion canceled | Which awards are affected and how the adjustment is explained |
Inspect balances and transaction history after each event. A successful award screen alone does not prove the promotion settles correctly.
Keep changes accountable
Attach the applicable rule version to the award. Separate stopping future awards from changing the treatment of awards already issued. Define the approvals and player communication required for an authorized correction.
The team should be able to see why an award or contribution was accepted or rejected. Agree who can change a rule, pause an offer and approve a financial adjustment without erasing the original record.
Scope the promotion and its interfaces
Connect the bonus engine to the PAM, game events, wallet and any CRM journey that triggers the offer. Identify which system owns eligibility and how changes reach the other components.
Send one complete promotion and its terms, with the intended markets, games and currencies. Include expiry and withdrawal scenarios in the acceptance brief.