---
title: "Season passes"
description: "Sell a pass that covers a regular rider's own place on chosen tickets for 1 to 12 months."
---

> Documentation Index
> Fetch the complete documentation index at: http://localhost:4321/llms.txt
> Use this file to discover all available pages before exploring further.

# Season passes

> **Administrators only**
>
> This part of the portal is only visible to people with the **Administrator** role. If you can't see it in your menu, ask an administrator. See [Roles and permissions](/reference/roles-and-permissions).

A **season pass** is bought once, up front, and then covers the holder's **own place** on the tickets you choose for as long as it lasts. Manage passes under **Operations > Passes**.

## Create a pass

| Field | Notes |
|---|---|
| **Name** | For example "Summer season pass". |
| **Description** | Shown to customers on the booking site. Supports formatting. |
| **Price** | Must be above zero, in your system currency. Paid in full on purchase. |
| **Valid for** | 1, 3, 6 or 12 months, counted from the day the customer pays. |
| **Tickets it covers** | Tick at least one. Events can't be covered. |
| **Enabled** | Untick to stop sales. |

## How a customer uses it

1. They buy the pass on the booking site's **Passes** page with their email address. That email becomes a customer if it isn't one already.
2. The pass starts the day payment **arrives**. Until then it shows as **Awaiting payment** and does nothing. They get a "Season pass purchased" email.
3. When they book with the same email, Gravity Pass spots the pass by itself. If it's still valid **on the date of the session** and covers a ticket in their basket, **one place is free**: the dearest covered ticket.
4. Anyone else on the booking pays as usual. A pass is **personal** and can't be passed on.

Prices are worked out in this order: **tickets**, then any **season pass** the booker holds, then **vouchers**. A booking that ends up at zero is confirmed straight away, with no payment.

The pass used is recorded on the booking and shown to you in [Bookings](/daily/bookings), as a "Season pass" line in the price breakdown.

> **Returning customers prove they own their email**
>
> Existing customers have to enter a code emailed to them before booking. That is what stops anyone else using their pass.

## Editing and deleting

- **Changes only affect passes sold from now on.** Holders keep the price, tickets and dates they bought.
- **Delete** stops new sales. Passes already sold keep working until they expire.
- Passes show on the customer's page in the portal, with their dates and an **Active**, **Expired** or **Awaiting payment** badge.

> **No refund button for passes yet**
>
> There's no way to refund or cancel a pass from the portal yet. Refund it in your Stripe dashboard, then disable or delete the pass if you don't want to sell it any more.

Source: http://localhost:4321/selling/passes/index.mdx