> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getkardy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Birthday rewards

> Offer a birthday-month perk without changing a member's stamp progress.

> [!NOTE]
>
> This feature is in development rollout. Consumer and merchant applications and
> the birthday-reward backend must be released together before it is available
> in production. This does not enable birthday marketing emails or SMS.

## Set up your business's reward

The Owner opens **Rewards → Birthday rewards**, enables the reward,
enters a reward name and terms, then saves. For example: “A birthday coffee, on us”
with a maximum drink value or qualifying-purchase condition in the terms.

Birthday rewards are **not configured during onboarding**. Set them up later,
preview the customer-facing text, edit the name or terms, or switch the reward off
and save to pause it. Discard changes restores the last saved settings. Only the
Owner can configure the reward; Managers and Staff can check and redeem it.

One birthday perk can be configured per business. It applies at any active outlet
of that business. It is separate from stamp rewards and does not spend stamps.
Turning it off or changing its terms invalidates previously generated, unclaimed
codes. A member who already claimed cannot claim again by regenerating a QR or
because the Owner changed the reward.

## Consumer birthday details

In personal account settings, consumers may voluntarily add their **month and
day**, with explicit consent to use it for reward eligibility. No birth year is
collected. Dates stay private by default, including previously saved dates. A
separate optional checkbox lets consumers share month and day with authorised
teams at businesses where they have an active membership. They can turn sharing
off anytime and still qualify for rewards. Neither choice subscribes them to marketing.

In **Members → More details**, the merchant team sees the shared month/day (or
“Birthday not shared”), current reward eligibility, the perk and terms, and this
year's redemption date if already claimed. No birth year, age or birthday export
is exposed. Employees cannot edit consumer birthdays or reset claims.

The date applies across the businesses they join. Consumers can remove it anytime,
which stops eligibility and clears the stored month/day. Date corrections are
limited to once every 365 days; support can help with a genuine mistake. Removing
the date does not erase claim history or reset the correction cooldown.

## Eligibility

* The reward is available during the consumer's **birthday month**, in Singapore time.
* Their active membership and saved birthday must both be at least **seven days old**.
* The business must have an active subscription and birthday rewards enabled.
* There is **one claim per consumer per business per calendar year**, shared across outlets.
* February 29 birthdays are valid; the birthday-month rule means they work every February.

Adding a birthday late in the month may leave no eligibility window that year
because of the seven-day wait. Never promise a reward before eligibility is confirmed.

## Redeem at the counter

1. The consumer opens the business's membership in their wallet.
2. Under **Your birthday perk**, they choose **Show birthday reward QR**.
3. Staff select an active outlet and scan that separate QR.
4. Staff review the reward, check its terms and confirm the redemption.
5. Hand over the perk only after the confirmation succeeds.

The code expires after ten minutes or at the end of the birthday month, whichever
comes first. A replacement code invalidates the previous one. Retrying a confirmed
redemption returns the same receipt instead of granting a second reward. The
consumer can refresh reward status to see that it has been redeemed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.