Native Stripe billing for client sites - per-site subscriptions, the operator billing dashboard, and configurable non-payment enforcement.
Loading the guide...
Help us make the guides more useful.
0 helpful · 0 not helpful
Seedly Sites includes native Stripe billing so each client site can carry its own subscription - your client paying you, through your Stripe account. It is fully opt-in: sites without billing configured behave exactly as before and are never restricted.
| Piece | What it is |
|---|---|
| Your Stripe account | Owns the products, prices, customers, and payments |
| Per-site Billing page | Where a subscription is started and managed for one site |
| Operator billing dashboard | Every site's billing state in one table |
| Enforcement | What (if anything) happens to a site when payment lapses |
Plans and prices live in Stripe - the platform references a Stripe price and displays its nickname as the plan label. To change what you charge, change the price in Stripe.
Each site has a Billing page showing the subscription status, plan, and renewal date.
Once a subscription exists, Manage billing opens Stripe's hosted customer portal for that site: update the card, view invoices, cancel, or resubscribe. A canceled site's button becomes Resubscribe.
The operator also sees a Billing configuration panel on each site's Billing page:
The per-site Enforcement setting described below is on the site's record in /admin (Tenants).
Managing a site's billing requires administrator-level access on that site (or the operator) - see Users and Roles. Editors and below see the billing state but are told to contact their account manager. Payments are processed entirely by Stripe on Stripe-hosted pages; card details never touch your instance.
The platform mirrors the Stripe subscription into one of six statuses:
| Status | Meaning |
|---|---|
| No subscription | Billing was never set up for this site - never restricted |
| Trialing | In a Stripe trial period - healthy |
| Active | Paid and current - healthy |
| Past due | A renewal payment failed - delinquent |
| Unpaid | Payments kept failing - delinquent |
| Canceled | The subscription ended - delinquent |
Status updates flow in automatically from Stripe (via the webhook you configure at setup). Only the three delinquent states can ever trigger enforcement.
Each site has an Enforcement setting that decides what happens while its subscription is delinquent:
| Setting | Effect while delinquent |
|---|---|
| Instance default | Defers to your instance-wide default (edit-lock unless you configure otherwise) |
| None | Never restrict this site |
| Edit-lock | Client editing, publishing, and deploys are frozen; the live site stays up |
| Suspend | Everything edit-lock does, plus the live site is taken offline |
Points that matter in practice:
Operator portal -> Billing aggregates every site: status, plan, renewal date, and the enforcement that currently applies. Delinquent sites sort to the top, so the dashboard doubles as your "who needs a nudge" list.
Billing activates when your instance has its Stripe configuration set (as part of provisioning):
Until those are set, Billing pages show "Billing isn't configured for this instance yet" and nothing is enforced.