Skip to Content
FluxStore is currently invite-only. Some sections of this documentation are still being written and expanded.
ProductsSubscriptions

Subscriptions

Subscriptions let you sell packages with recurring payments. They automatically renew and deliver commands on a regular schedule. They’re ideal for ongoing perks like VIP ranks, monthly kits, or recurring currency drops.

Billing and renewals are handled by your connected payment provider (Stripe or PayPal).

Setting Up a Subscription Package

Create a package as usual from Products in your dashboard. In the pricing section, choose Subscription instead of one time purchase, then configure:

  • Interval: how often the customer is billed (weekly, monthly, quarterly, every six months, or annually)
  • Price: the amount charged each billing cycle
  • Trial period (optional): number of days before the first charge. During the trial, delivery commands execute immediately but payment is deferred. If the customer cancels during the trial, no charge is made.

A package’s pricing model (one time vs. subscription) cannot be changed after customers have purchased it. Create a new package if you need to switch models.

Subscription Lifecycle

StageWhat happens
ActiveThe subscription is running. Payments are collected on schedule.
RenewalAt the end of each billing cycle, the payment provider charges the customer. On success, delivery commands execute again.
Past DueA renewal payment failed. The payment provider will retry according to its retry schedule.
CancelledCancellation requested. The subscription stays active until the end of the current paid period, then expires.
ExpiredThe subscription has ended. No further payments or command deliveries occur.

Subscription Commands

Delivery commands execute twice: on the initial purchase and on each successful renewal. This means your commands need to be safe to run repeatedly.

Think about what “repeated execution” means for each command:

  • Idempotent commands are safe. Running lp user {player} parent set vip every month just reapplies the same rank. Same for permission grants, rank assignments, and similar commands that set state.
  • Additive commands run every cycle. Running give {player} diamond 32 on each renewal gives 32 diamonds every billing cycle. This is often intentional for “monthly kit” packages, but make sure it matches what you’re selling.
  • Currency grants are additive too. eco give {player} 1000 adds 1000 each renewal. Great for a monthly allowance, but be aware it accumulates.

A typical monthly VIP subscription might combine both types:

lp user {player} parent set vip give {player} diamond 32 eco give {player} 1000

Make sure your commands match your intent. Idempotent commands (like setting a rank) are safe to repeat. Additive commands (like giving items or currency) will stack on every renewal.

Customer Self Service

Customers can manage their subscriptions through their account portal on your storefront. They can view active subscriptions and renewal dates, or cancel a subscription.

When a customer cancels, the subscription is set to cancel at period end. They keep their perks until the current billing period expires, and no further charges are made.

Customers are not charged again after cancelling. Their perks remain active until the end of the already paid billing period.

Managing Subscriptions from the Dashboard

From Orders in your dashboard, filter by subscription orders to see active, cancelled, and expired subscriptions. Click any subscription to view its full history, including renewal payments and command delivery logs. You can also cancel a subscription on behalf of a customer from this view.

Next Steps

  • Packages: learn about package configuration, commands, and variables
  • Managing Orders: view order history and manage command deliveries