Prize model setup
- Fixed, tiered, or percentage-based reward pools.
- Rank bands and shared pools for tiered placements.
- Budget caps with fallback strategies when exceeded.
Configure how winners are selected, what they earn, and how fulfillment progresses. Reward configuration makes payout logic transparent and operationally safe, from eligibility checks through to final completion and reconciliation.
This state model gives operators clear checkpoints, supports SLA tracking, and keeps player communication consistent during payout processing windows.
| Reward State | Description |
|---|---|
| REWARDED | The Tournament has ended and leaderboard processed and finalised |
| ACCEPTED | Player has either automatically (configuration) or manually accepted the award |
| FULFILMENT_PENDING | Reward has been sent to a downstream system to be processed. This could be calling operator endpoints to credit cash or free spins |
| IN_PROGRESS | Downstream system has picked up the reward to be processed |
| MANUAL_REVIEW | Manual intervention required by a human |
| COMPLETED | Reward, processed and completed end to end. |
| FAILED_RETRYABLE | Failure recorded, in the process of retry |
| FAILED_TERMINAL | Failure recorded which cannot be retried, manual intervention required |
| EXPIRED_UNCLAIMED | Reward was not claimed during the time configured. |
Strong reward configuration reduces payout errors, lowers manual interventions, and improves trust with both players and internal stakeholders.