Reward Types

A reward type defines something players earn. You define reward types once, on the Reward Types surface in Studio, and reference them from tier earn rates and milestone rewards. Reward types must exist before you can build tiers or milestones.

Each reward type maps to a stable ID that appears as itemId in webhook reward payloads. Grant against that ID, not the display name.

Loyalty XP

Loyalty XP is the progression currency of the program. It is tracked entirely by Stash and is not spendable: a player's XP total determines their tier and which milestones they have reached.

• Earned automatically on every purchase at the current tier's XP earn rate.
• Reversed proportionally on refund. See Refunds & XP adjustments.
• Reported to your backend as totalPoints and xpDelta in the loyalty webhook payload.

Loyalty XP is often named natively per game (for example "Race Points"). The display name is cosmetic; the reward type ID is what identifies it on the wire.

In-game currency

An in-game currency is a currency, token, or item in your game's economy that Stash grants to players as a loyalty reward. Stash does not hold in-game currency balances. Stash tells your backend what to grant and when; your backend owns the balance and applies the grant.

In-game currency is granted two ways:

• As a tier earn rate, per USD of webshop spend, applied automatically at checkout. See Tiers.
• As a milestone reward, a fixed one-time amount the player claims. See Milestones.

Catalog products (SKU rewards)

A milestone reward can also deliver an arbitrary product from your catalog: a bundle or item (a SKU), rather than a currency amount. Use this for reward moments that should grant a packaged product instead of raw currency.

SKU rewards appear in the milestone claim payload the same way currency rewards do: an itemId (the catalog SKU) and a quantity. Your backend grants the product on receipt.

Assets

Each reward type takes a square icon (162 x 162 px), uploaded in Studio, shown next to the reward in the loyalty hub. Icons are display fields and stay editable after the program is published.