Subscription Plans

Build the pricing tiers subscribers pay for — pricing, billing cycles, trials, and eligibility rules.

By the end of this page, you'll have created your first subscription plan and know how to shape every option — from trial days to "churned-only" eligibility filters.

A subscription plan is the product your members actually buy. Each plan defines a price, a billing cycle, a set of resources it unlocks, and any eligibility or usage rules. You can create unlimited plans per project — monthly, yearly, lifetime, access-code-only — mix and match to fit your business.

Navigating to Subscription Plans. Select a project first (top-left project picker), then open Subscription Plans from the sidebar.

Prerequisites

Before creating a plan, you should have at least:

One payment method enabled — otherwise there's nothing for the plan to charge through.
One resource available — plans require at least one linked resource to define what the subscriber unlocks.

Create a plan

From the Subscription Plans page, click Create New Subscription Plan at the top-right. A multi-section form opens. The sections below walk through every field in order.

Choose the kind of plan

Three cards sit at the top of the form, and this is the choice that decides which half of the form you see next. Everything on the rest of this page describes a Recurring Subscription, which is the default.

Kind	What it sells	Renews
Recurring Subscription	The traditional subscription. Nothing is scheduled — members pay each cycle and keep access for as long as they keep paying.	Yes, on a cycle
Time-Limited Pass	A ticket to one dated session — workshops, match days, one-off events. Access opens and closes on its own and never renews.	No
Pass Series	A season ticket over many passes — seasons, courses, cohorts. One payment covers every pass you bundle from your pass plans.	No

The two scheduled kinds replace the pricing, billing-cycle and trial sections below with their own controls, because access comes from a date rather than from a period. They are unlocked by the same capability — included in Growth, or on Free and Starter with the Passes Addon — and neither carries an extra transaction fee.

Switching cards discards the shape you moved away from

A plan is saved as exactly one kind. Half-composed pass slots are not kept if you save as a subscription, and a half-composed series is not kept if you switch to a pass. Pick the kind first, then fill the form.

See Time-Limited Passes and Pass Series for those two in full.

Basic details

Plan Name (required) — 5–255 characters, must be unique within the project. Public-facing, so make it descriptive: "Pro Monthly", "Annual Lifetime Legacy".
Description (optional) — up to 1,000 characters. HTML is allowed (bold, italics, lists, links) and sanitized for safety. Use it to sell the plan.

Linked resources

At least one required. Tick the resources this plan grants access to.

Ordering matters: the sequence you select is the order they appear on the invoice and in the member's portal view.
For Telegram channel / group / supergroup resources, Subscriby automatically invites and removes subscribers on lifecycle events.

Pricing

Currency (required) — pick one of the currencies your enabled payment methods support. If no enabled method supports it, the plan will be blocked from saving until you either change the currency or enable a compatible method.
Price — at least the $1.00 USD equivalent in your chosen currency. Payment providers reject dust amounts, so a plan priced at a few cents could never actually be bought. Enter something below the floor and the error names the minimum in both your own currency and USD.
Price of 0 publishes a free plan, which is available on Starter and Growth. On the Free tier the price field will not accept 0 and the form points you at an upgrade.

Billing cycle

Cycle type — Days, Weeks, Months, Years, or Lifetime.
Cycle count — an integer ≥ 1 representing how many of the cycle units pass between charges.

Examples:

Monthly billing → cycle type Months, count 1.
Every-3-months plan → cycle type Months, count 3.
Weekly plan → cycle type Weeks, count 1.
Annual plan → cycle type Years, count 1.
Lifetime (pay once, keep forever) → cycle type Lifetime. Count is locked to 1.

Trial period (optional)

Trial days — 0 or more. Zero disables trials entirely.
Trial type —
- "Once for project" — the subscriber gets one trial across all plans in this project. Switching plans during trial doesn't reset it.
- "Once for plan" — the subscriber can trial this plan even if they trialled a different plan previously.
Cardless trial —
- On — we don't ask for payment details up front. Access stops when the trial ends unless they convert.
- Off — we take a card during signup and auto-charge when the trial ends (recurring plans only).

Renewal behaviour

Recurring (default on) — plan auto-renews. At the end of each billing cycle, Subscriby tries to charge the saved payment method and extends access on success.

If turned off, the plan becomes a one-time purchase: access is granted for the billing duration, then expires. No automatic renewal. Think "season pass" or "lifetime deal".

Recurring can't be enabled for crypto or platform-currency plans (CoinPayments, CeyPay, Telegram Stars) — they only support one-time charges by nature. Subscriby will block the save and explain why.
Allow disabled plan renewal (default off) — if you later mark this plan Inactive, existing subscribers on it either keep renewing (this toggle on) or are locked out of renewal (this toggle off).

Turning it on is how you grandfather early supporters into legacy pricing while hiding the plan from new buyers.

Access restrictions (optional)

Pick at most one of the following audience filters:

Newcomers only — only users who have never subscribed before. Great for intro offers.
Customers only — only users with an active subscription. Perfect for VIP upgrades.
Churned only — only users whose subscription has expired. Great for win-back campaigns.

And optionally one or both usage filters:

Single use — plan hides from the subscriber's view after they've bought it once.
Access codes only — plan never appears on the public portal or in the bot's plan list. The only way to subscribe is by redeeming a pre-generated access code.

Sales limit (optional)

Sales cap — stop selling after this many successful purchases. When the last one lands, Subscriby switches the plan off on the spot and marks it Sold Out in the plan list, so you can see the platform paused it rather than a teammate. Existing subscribers are untouched.
Switch the plan back on to sell another batch of the same size; the counter restarts at zero. Changing the cap while the plan is on sale restarts the counter too. Leave it empty for no limit.
Only paid purchases count. Access-code redemptions and cardless trials do not spend the cap.

The cap works on every kind of plan — a subscription, a pass or a season. A pass_series plan also has a seat cap in its season settings: the seat cap refuses the next checkout the moment the seats are taken, the sales cap counts confirmed purchases and pauses the plan after the last one. When a season fills its last seat, the plan is paused with the reason Seats Full.

Save and activate

Active (toggle) — when on, the plan is visible and buyable. Turn off to hide without deleting.
Click Create Subscription Plan.

Field reference

A quick summary of every configurable field on a plan:

Field	Type	Default	Notes
Name	string	—	Required, 5–255 chars, unique per project
Description	rich text	(empty)	Up to 1,000 chars, HTML allowed & sanitized
Price	decimal	—	≥ the $1.00 USD equivalent, or 0 on Starter / Growth
Currency	enum	—	Must be supported by ≥ 1 active payment method
Billing cycle	enum	Months	Days / Weeks / Months / Years / Lifetime
Billing cycle count	integer	1	≥ 1; must be 1 for Lifetime
Trial days	integer	0	≥ 0
Trial cardless	boolean	false	Can't require payment up front
Trial type	enum	Project	Project / Plan
Recurring	boolean	true	Can't be on for crypto / platform currencies
Disabled renewal	boolean	false	"Grandfather" early subscribers
Newcomers only	boolean	false	Mutually exclusive with Customers / Churned
Customers only	boolean	false	Mutually exclusive with Newcomers / Churned
Churned only	boolean	false	Mutually exclusive with Newcomers / Customers
Single use	boolean	false	Hides plan from users who've bought it
Access codes only	boolean	false	Plan never appears publicly
Sales cap	integer	(none)	1–100,000; pauses the plan after that many purchases
Active	boolean	true	When false, plan is hidden (but existing subs continue)
Resources	array	—	Must link at least 1

Common plan recipes

Name: Pro Monthly - Price: $9.99 - Billing: Monthly (count 1) - Recurring: On - Resources: Main group, premium channel

Sync with payment providers

Recurring plans need to exist in your payment provider's own catalogue for automatic billing to work. See Sync subscription plans for the one-click sync action.

Create or update the plan in Subscriby first, then run Sync. Running Sync before saving changes won't propagate them.

Edit, deactivate, or delete

Edit a plan

Change any field on the plan form and save. Edits apply immediately to new subscribers. For existing subscribers:

Price changes apply at their next renewal.
Resource changes apply immediately (existing members gain / lose access on the next sync).
Eligibility filters don't kick existing members out — they only affect new purchases.

Deactivate a plan

Flip the Active toggle off. The plan disappears from the public portal and the bot's plan list. Existing subscribers keep renewing only if Allow disabled plan renewal is on — otherwise they lapse at cycle end.

Paused automatically

A plan the platform switched off shows an amber Sold Out or Seats Full badge instead of a plain No in the Active column, and the plan's detail panel says why. Switching the plan back on clears the badge and, for a sales cap, starts a fresh batch. A season whose seats are full keeps them full: raise its seat cap before switching it back on.

Arrange the storefront order

By default the portal and the bot list passes first, then seasons, then subscriptions, each group cheapest first. To pin a different order — a weekly bundle above the four daily passes it contains, say — click Arrange Storefront Order above the plan list, drag the plans into place and Save Order. The portal and the Telegram bot follow immediately.

Plans you create later join the end in the default order until you arrange again, and Reset to Default Order removes every pin. The same order is available to integrations through POST /v1/projects/{project}/plans/order and the reorder_plans MCP tool, and every change fires the plan.order_changed webhook.

Delete a plan

Permanent. Active subscribers on a deleted plan lose access at their current cycle end. Use with care — prefer Deactivate unless you truly need the plan gone.

Frequently asked

Resources — what plans unlock.
Payment methods — where plans get paid.
Access codes — generate codes for access-code-only plans.
Transaction fees — how Subscriby calculates its cut on every transaction.

Subscription Plans

Can I have multiple plans at the same price?

Can I create a plan priced at 0?

What currencies are supported?

Can I change a plan's billing cycle after subscribers are on it?

Can a user be on multiple plans in the same project?

What's the difference between 'Single use' and 'Access codes only'?

Can I limit a plan to a set number of people?

Can I choose the order plans appear in on the portal and in the bot?

On this page