---
title: "Age-related rules"
slug: "altersbedingte-regeln"
updated: 2026-06-09T11:47:26Z
published: 2026-06-09T11:47:26Z
canonical: "help.frisbii.com/altersbedingte-regeln"
---

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

# Age-related rules

## Preliminary Remarks

The **age-related rules** can be used to realize different prices for an offer depending on the age of those requesting it (e.g. if the customer is younger than 25, he receives the discounted offer X, if he is older, then offer Y).

In order to be able to implement age-related rules in the checkout, the [age verification](/frisbii-media/docs/identitäts-und-altersprüfung-1) module must be activated for a fee. Age verification can be implemented either with [Frisbii Media's own age verification](/frisbii-media/docs/option-plenigo-altersverifikation) or with [Stripe Identity](/frisbii-media/docs/option-stripe-identity).

---

## Create age-related rules

- Click on **+Add rule**.
- Define **an internal title*** and optionally add a **description**.

#### Define rule

- **This offer applies for ages over/under/equal to X**: A discounted time-based offer can be selected here.
- **Otherwise the following offer is made**: The alternative offer is selected here (e.g. full price).
- **If the condition no longer applies, the following offer becomes valid**: As soon as the customer exceeds the age limit, the subscription is automatically converted to the specified subscription.

![](https://cdn.document360.io/b84e1b5d-2ba6-4465-8c62-fb45a2f31314/Images/Documentation/image-VFEYMMZP.png)

- Define the **title*** to be displayed to customers in the checkout.
- Define the **description*** to be displayed to customers in the checkout. e.g. the information that this is an offer with age verification.
- Define the texts that are displayed to the customer if the **condition** **applies** and **does not apply**.

---

## Application example

The following rule was defined in the Merchant Backend:

![](https://cdn.document360.io/b84e1b5d-2ba6-4465-8c62-fb45a2f31314/Images/Documentation/image-JL86M74C.png)

The description is displayed in the checkout above the entry of personal data.

| Settings in the Merchant Backend | View in the checkout |
| --- | --- |
| ![](https://cdn.document360.io/b84e1b5d-2ba6-4465-8c62-fb45a2f31314/Images/Documentation/image-XSPSH4T9.png) | ![](https://cdn.document360.io/b84e1b5d-2ba6-4465-8c62-fb45a2f31314/Images/Documentation/image-CA0OUL1V.png) |

Depending on whether the person **fulfills the condition** or **not**, the corresponding text is displayed.

| Settings in the Merchant Backend | View in the checkout |
| --- | --- |
| ![](https://cdn.document360.io/b84e1b5d-2ba6-4465-8c62-fb45a2f31314/Images/Documentation/image-FXVFJ4PX.png) | ![](https://cdn.document360.io/b84e1b5d-2ba6-4465-8c62-fb45a2f31314/Images/Documentation/image-SBH9FRHN.png) In this case, the customer is not under 25 and is automatically redirected to the alternative offer (full price). |

---

## Callback behaviour

When a subscription ends due to an age-related rule, the callback triggered an `ENDED` callback. The age-related subscription expires naturally at its `endDate`. It is not actively canceled.

> [!WARNING]
> No `CANCELLATION` callback is sent when the age threshold is reached. Integrators relying on `CANCELLATION` alone will miss age-triggered handovers — listen for `ENDED` with `successorReason: "AGE"` instead.

Example:

| Subscription | Callback type | Notes |
| --- | --- | --- |
| Young (under-25) subscription at conversion date | `SUBSCRIPTION` + `ENDED` | No `cancellationDate` set. `successorReason: "AGE"` is present. |
| Adult follow-up subscription | `SUBSCRIPTION` + `CREATION` | Sent at the time of original purchase, not at the conversion date. |

> [!TIP]
> **Good to know**: The follow-up subscription already exists by the time the age conversion happens — no new `CREATION` callback is sent at the birthday. The `ENDED` callback on the young subscription is the signal for the handover. `successorId` in the payload points to the follow-up subscription ID.