Reward process status flow
The Reward Processor manages the complete lifecycle of player rewards β from creation and claiming to activation and expiration. The reward claiming process can be initiated in two ways: either through the user interface (UI) or by an administrator, both with the goal of awarding a reward to the player. Rewards can also be automatically granted through other gamification products such as Missions, Tournaments, Campaigns, or purchased directly by the player through the Reward Shop. When a claim is initiated, the system first checks whether the reward has already been claimed. If it has, the process ends there. If the reward is still available (Unclaimed), the process continues depending on its type and activation configuration.
π Types of Rewardsβ
Each reward type has its own logic during activation and claiming:
| Reward Type | Description |
|---|---|
| Bonus Offer | Sends a promotional bonus to the player through the external Bonus System. |
| Tokens / XP | Grants virtual tokens or experience points directly to the player's account. |
| Boosters (Level, Mission, Token) | Temporarily multiply the player's progress or points. They may activate automatically or manually. |
| MiniGame | Unlocks special interactive mini-game rewards. |
| External | Rewards from external systems, directly marked as Granted. |
| Manual | Rewards manually created and assigned by administrators. |
π Reward Lifecycleβ
Rewards move through several stages to ensure full traceability and reliability:
| Status | Description |
|---|---|
| Unclaimed | The reward is available but has not yet been claimed by the player. |
| Pending | Booster-type/Mini-Games rewards waiting to be activated. |
| In Progress | Reward activation is ongoing. |
| Granted / Completed | The reward was successfully delivered or used by the player. |
| Failed | An error occurred while processing the reward. |
| Declined / Deleted / Expired / Bounced | The reward was declined, removed, expired, or abandoned (e.g., mini-games). |
βοΈ Claiming and Activation Flowβ
The reward claiming process can be initiated in two ways: either through the user interface (UI) or by an administrator, both with the goal of awarding a reward to the player. Rewards can also be automatically granted through other gamification products such as Missions, Tournaments, Campaigns, or purchased directly by the player through the Reward Shop.
When a claim is initiated, the system first checks whether the reward has already been claimed. If it has, the process ends there. If the reward is still available (Unclaimed), the process continues depending on its type and configuration.
Once validated, the system determines the type of reward and executes the appropriate flow:
- Automatic rewards are activated immediately after being created.
- Manual or player-activated rewards remain in Unclaimed or Pending status until the player or administrator triggers activation.
- Once activation starts, the reward transitions to In Progress and then to Granted or Completed depending on the result.
- If any error occurs during the process, the status changes to Failed, providing traceability for support and debugging.
This ensures that all rewards β whether earned, purchased, or manually granted β follow a consistent, transparent, and reliable process from creation to delivery.
π― Reward Processor (RP) β User Journey Overviewβ
The Reward Processor (RP) manages the complete reward lifecycle β from creation to delivery β based on platform configuration.
Each reward goes through a set of statuses that describe its current state in the process.
How the reward moves between these statuses depends on two main configuration flags:
- PlayerShouldClaimRewards β determines if the player must manually claim the reward.
- AutomaticActivation β determines if the reward is automatically activated or needs manual activation.
π§ User Journey Scenariosβ
Scenario 1 β Player Must Claim and Activateβ
Actors: π€ Player β βοΈ Reward Processor (RP) β π§© Mechanic or service
(Typical for boosters, mini-games, or rewards with expiration)
- A new reward is registered in RP.
- Since
PlayerShouldClaimRewards = true, the reward is stored in the Chest β status: Unclaimed. - The player clicks Claim in the widget β status: Pending Activation.
- The player then clicks Activate β RP validates expiration date.
- If the reward expires before activation β status: Expired.
- If valid β reward moves to In Progress and is delivered to the corresponding mechanic (e.g., Missions, Ranks).
- The service processes the reward:
- Applies effects (XP, multipliers, etc.)
- Reports completion β status: Granted or Complete.
- If any delivery error occurs β status: Failed.
Scenario 2 β Automatic Activationβ
(Typical for XP, Tokens, Bonus, External rewards)
- A new reward is registered.
- Since
PlayerShouldClaimRewards = false, the reward goes directly to Pending Activation. - If the reward expires before activation β status: Expired.
- If
AutomaticActivation = true, the RP immediately delivers the reward to the mechanic. - Reward moves to In Progress, and after successful delivery β Granted.
- If thereβs a communication or system error β Failed.
π§© Status Tableβ
| Status | Set When | Who Triggers It | Description |
|---|---|---|---|
| Unclaimed | Reward created and stored in chest | RP | Player must claim before activation. |
| Pending Activation | Player claims the reward or system schedules activation | RP | Waiting to be activated or automatically delivered. |
| In Progress | Reward delivery started | RP β Mechanic | Mechanic is processing or validating reward (XP, mission, bonus, etc.). |
| Granted | Reward successfully applied | Mechanic β RP | Reward applied to player (e.g., XP added, bonus granted). |
| Complete | Temporary reward finished | Mechanic β RP | Booster or timed reward expired after use. |
| Expired | Reward validity period ended before activation | RP | Reward is no longer valid. |
| Failed | Delivery or communication error occurred | RP | Mechanic could not process reward; flagged for retry or support. |
| Declined | Player rejects the reward | Player | Reward is canceled and not stored. |
π Reward Type Summaryβ
| Reward Type | Activation Method | Expires | Delivered To | Example / Description |
|---|---|---|---|---|
| XP | Automatic | β No | Ranks | Player receives experience points instantly; rank system updates player progress. |
| Tokens | Automatic | β No | Wallet / Token mechanic | Virtual currency or points are added automatically to the player balance. |
| Bonus | Automatic | β No | Bonus Service / Casino | External casino bonus granted directly (e.g., 10 β¬ bonus). |
| External | Automatic | β No | Do nothing | β |
| Mission Booster | Player Manual | β Yes | Missions | Player activates a booster (e.g., Γ2 contribution) valid for a set period (e.g., 3 hours). |
| Token Booster | Player Manual | β Yes | Tokens | Multiplies earned tokens for a time window (e.g., Γ3 tokens for 1 hour). |
| Level Booster | Player Manual | β Yes | Ranks | Temporarily increases XP gain in rank progression. |
| Mini-Game | Player Manual | β Yes | Mini-Game Mechanic | Unlocks a game that must be played before expiration (e.g., spin-the-wheel). |
| Manual Reward | Admin Manual | β No | Defined by Admin | Administrator assigns reward directly to player. |
β Quick Summaryβ
-
Automatic rewards: delivered immediately β no user action.
(XP, Tokens, Bonus, External) -
Manual rewards: require player activation, may expire.
(Mission Booster, Token Booster, Level Booster, Mini-Game)