> ## Documentation Index
> Fetch the complete documentation index at: https://voucherify-rc-lv2-guides.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Rewards overview

> Understand how rewards let Loyalty v2 members redeem their points for material products or digital incentives

A reward is what a member actively redeems by spending points, unlike a [benefit](/api-reference/loyalty-v2-benefits-overview), which is granted automatically by an earning rule. Rewards are optional and only become redeemable once assigned to a program with a stock configuration.

## Reward types

A reward requires `name`, `type`, and `costs`, plus exactly one type-specific object matching its `type`:

* `MATERIAL`: A physical product or SKU, defined in the `material` object.
* `DIGITAL`: A discount coupon or gift card, defined in the `digital` object.

## Costs and program assignment

A reward's `costs` array can define a different point price per card definition, so the same reward can be connected to multiple point wallets – even across different programs – each with its own price. The reward itself doesn't carry stock; stock is set per program when the reward is assigned through the [Programs](/api-reference/loyalty-v2-programs-overview) batch assignment endpoint, and can be updated afterwards without going through the batch flow again.

## Validity and refunds

A reward can define `validity_hours` to restrict when it's redeemable (defaulting to any time), and `refunds` behavior for what happens to spent points when a reward purchase is refunded.

## Lifecycle

A reward can be created directly in `DRAFT` or `ACTIVE` status. From there, it follows the same three-state pattern as earning rules and tier structures: `DRAFT`/`INACTIVE` > `ACTIVE` with the [reward activate endpoint](/api-reference/rewards/activate-reward), `ACTIVE` > `INACTIVE` with the [reward deactivate endpoint](/api-reference/rewards/deactivate-reward), and `ACTIVE` > `DRAFT` with the [reward draft endpoint](/api-reference/rewards/move-reward-back-to-draft) for unassigned rewards. While in `DRAFT`, every property can be updated; once active or inactive, only `name`, `metadata`, `refunds`, `validity_hours`, `start_date`, `end_date`, and `costs` can still change. Deleting a reward moves it to a `DELETED` status.

## Redeeming and checking availability

Members redeem rewards through the [member reward-purchase endpoint](/api-reference/programs/purchase-reward-with-points), which spend points from the card tied to the reward's cost configuration and can later be [refunded](/api-reference/programs/refund-a-reward-purchase). Before building a redemption flow, use the [Examine overview](/api-reference/loyalty-v2-examine-overview) endpoint to check which rewards a member can currently afford and why any others are unavailable.

## Related resources

* [Loyalty v2 API: Overview](/api-reference/loyalty-v2-api-overview) for the full Loyalty v2 API map.
* [Programs overview](/api-reference/loyalty-v2-programs-overview) for assigning rewards and their stock to a program.
* [Members overview](/api-reference/loyalty-v2-members-overview) for purchasing and refunding rewards.
* [Benefits overview](/api-reference/loyalty-v2-benefits-overview) for the automatically granted counterpart to rewards.
* [Create loyalty rewards](/build/create-loyalty-rewards) for the dashboard perspective on configuring rewards.