# Managing billing

> View licenses, change seats or cycle, and cancel — from the app or your account.

_Updated: 2026-06-08_

Billing is handled by railbase.app, but you can reach it from two places: your Railbase
admin, or your [account](/account) on this site. Both open the same secure vendor
billing portal.

## See what you own

- **In the app** — your Railbase admin's **Marketplace** has a *My licenses &
  billing* view listing every plugin you're licensed for, its seat count, and its
  renewal date.
- **On this site** — the same list is on your [account](/account), where you can
  copy a license key if you ever need it.

Both views read from railbase.app, so they always agree.

## Free trials

Some plugins offer a **free trial** — start it from the **Marketplace** in your
admin and the plugin installs immediately, no card required. A trial is **one per
plugin** and runs for a fixed period. Buy any time during the trial to convert it
to a paid subscription with no interruption; if it ends without a purchase, the
plugin gates off like a lapsed license — your data stays dormant and returns the
moment you subscribe.

## Change seats or billing cycle

Open **Manage billing** (from either place). It launches the vendor's billing
portal, where you can:

- add or remove **seats** (the count of billable users — see
  [Licensing & seats](licensing-and-seats)),
- switch between **monthly and yearly** billing,
- update your **payment method**, or
- **cancel** a subscription.

Changes propagate to your instance automatically over the license heartbeat —
a larger seat count or a renewed term rotates in without a reinstall.

> [!NOTE]
> Increasing seats takes effect as soon as the updated license reaches your
> instance. If a plugin reports it's over its seat limit, raise the seat count
> here and it reconciles on the next license refresh.

## Cancellations and lapses

If a subscription is cancelled or a payment lapses, the plugin gates **off**:
running requests get a *402 Payment Required*. Your data is not deleted — it stays
dormant, and the plugin comes back the moment a valid license is in place. A short
grace window covers an in-flight renewal so a transient payment hiccup doesn't
suspend production.

## Receipts and notifications

The vendor emails receipts, renewal notices, and dunning warnings (failed
payment) to your account email. Keep that address current in the billing portal so
you don't miss a renewal.

> [!TIP]
> For invoicing questions, refund requests, or anything billing-related the portal
> doesn't cover, use [Support](../support).
