A member cannot move a subscription paused by an operator's grant to the granted tier or a higher one before the grant ends #278
Closed
opened 2026-10-27 06:24:32 +00:00 by cgalo5758
·
2 comments
Labels
Clear labels
accessibility
area/billing
area/catalog
area/discourse
area/domains
area/entitlements
area/fedwiki
area/identity
area/integrations
area/licensing
area/member-ui
area/meta
area/operator-ui
area/ops
area/testing
duplicate
good-first-issue
invalid
privacy
security
upstream
wontfix
A barrier for people using assistive technology or a keyboard alone.
The Stripe mirror, checkout, subscriptions, invoices, fulfillment.
Products, prices, plan ladders, purchasability.
The Discourse integration.
The domains registry, claims, placements, the certificate ask.
Entitlement sets, rules, grants, pools, provisioning.
The Federated Wiki integration and farm sync.
Sign-in, sessions, persons, organizations, workspaces, roles.
The provider registry, outbox and webhooks in general.
Licenses, the contributor agreement, SPDX headers.
Member pages.
The repository itself, its contributing guide, CI, the tracker and the workflow.
Operator pages, forms, lists, the design system.
Deployment, configuration, migrations, workflows, instance settings.
The test stack, screens, lint, walkthroughs.
Closed because another issue already covers it.
Small, self-contained, and explained enough to be a first contribution.
Closed because it is not a ticket for this repository.
Touches what a person's data reveals.
Touches authentication, authorization, secrets or data exposure.
Waits on another repository or project before it can move.
Closed because it will not be done, with the reason in the last comment.
kind
bug
The software does something other than what it promises; closed when it again does what it promises.
kind
debt
Code, tests or tooling to clean up with nothing visible changing; closed when they are cleaner.
kind
design
A question to settle before work can be defined; closed when the decision is written down.
kind
docs
Documentation that is wrong or missing; closed when it says the right thing.
kind
enhancement
Something the software does not do yet; closed when it does.
priority
critical
Blocks the active milestone or harms members now.
priority
high
Next in line inside the active milestone.
priority
low
Inside the active milestone, when nothing else is left.
priority
medium
Inside the active milestone, after the high ones.
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#278
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What a person cannot do today
Some terms first. A plan ladder is a ranked sequence of tiers, and an organization holds one tier per ladder at a time. A grant is an operator's record that gives an organization a tier without payment. When an operator grants a tier on a ladder where the organization's own subscription holds a tier, the grant takes the ladder: the subscription delivers nothing there until the grant ends, and, as decided on #269, its payment collection is paused at Stripe for that time. The paid plan's card on the Products page then reads "Paused while Pro is granted" and offers Cancel plan, and no tier on that ladder is sold through Checkout, so the member does not end up paying two subscriptions for one ladder (#277).
A member in that state cannot make the granted tier, or a tier above it, their own paid plan now. An organization granted Max while it pays for Plus, which wants Max to stay with no gap however the grant ends, has no way to pay for Max until the grant has ended; neither has one that wants a tier above Max.
What they should be able to do
On the card of the granted tier and on each tier above it, switch the paused subscription to that tier. The switch takes the ladder from the grant at once, collection resumes, and the new tier is billed from the switch with Stripe's proration. The grant is superseded: if the operator marked it to resume, it delivers again when the subscription ends, while the grant's own term lasts; otherwise it ends.
This decides a product question the console has answered the other way so far: a subscription never takes a ladder back from a grant, and the paid plan waits until the grant ends. Here a member's payment would end an operator's grant on that ladder, for a tier at or above the granted one only.
Why it matters
A member who wants to keep a granted tier past the grant, or to have more than the grant gives, has to wait for the grant to end and then buy, with a gap between the two, or ask an operator.
Where
The offer decision (
plans.Offer,internal/plans/offer.go), which decides what each tier's card offers; the switch (SwitchPlanandresolveLadderSubscription,internal/fulfillment/plan_change.go), which today starts from the position the organization holds and refuses one no subscription backs; the rule that the subscription reconcile leaves a product alone while another plan holds a ladder it took from the subscription (docs/models/plan-ladders-transitions.md;DisplacedProducts,internal/fulfillment/reconcile.go); the rule that a marked grant delivers again when the plan that replaced it ends (docs/models/plan-ladders-transitions.md, grant resumption).Done when
A member whose subscription is paused because a grant holds its ladder can switch it to the granted tier or a higher one from that tier's card; the switch supersedes the grant, resumes collection and bills the new tier from the switch; a marked grant resumes when that subscription later ends;
docs/models/plan-ladders-transitions.mdstates the exception beside the rule it changes; and a test drives a switch at the granted tier and one above it.This becomes part of #269's change, and closes with it. While a grant holds a ladder against the organization's paused subscription, the Products page offers, on the granted tier and on each tier above it, a switch of that subscription: the switch takes the ladder from the grant at once, resumes collection and bills the new tier from the switch. No tier on that ladder is sold through Checkout meanwhile, so the organization never holds two subscriptions on one ladder.
The product question above was already answered for an organization that holds only a grant: the Products page sells Checkout on any tier above a tier no subscription pays for (
internal/plans/offer.go, the offer's rule for a tier above a rung no subscription pays for), and that purchase supersedes the grant. The switch gives an organization whose subscription is paused the same move, at the granted tier too.Cancel plan on the paused subscription ends it at its period end, as everywhere else.
A member whose subscription is paused behind a grant can now switch it to the granted tier or a higher one from the Products page. The console lifts the pause at Stripe and then sends the usual upgrade, which is charged at once for the rest of the period, and the subscription takes the ladder from the grant; a grant marked to come back returns when the subscription ends, while its own term lasts. Two requests are needed because Stripe refuses an upgrade while the subscription is paused, and refuses lifting the pause in the same request as an upgrade that can wait for the bank's approval. When the card is declined, the bank's approval is pending, or anything else fails, the console pauses the subscription again at once and nothing is charged; a delayed job the console writes before the first request does the same a few minutes later if the console stops between the two requests. While a renewal Stripe made during the pause is about to be finalized, the switch answers "We couldn't complete that change. Try again in a moment.", so that renewal is still voided. Cancel plan on the paused plan voids an upgrade still waiting for approval, so paying it later cannot move a plan that is set to end. On the granted tier's own card the button reads "Pay for this plan" and the confirmation's heading "Pay for Pro?"; on a higher tier's card they read "Upgrade" and "Switch to Max?"; either confirmation then reads "Your subscription replaces the grant." before the charge sentence. When the higher tier is priced over another period, monthly to yearly for example, the switch is still offered, and the confirmation reads "Your card is charged $300.00 now, minus a credit for the unused part of your current plan, then $300.00 a year from today.": Stripe then charges the new price's full period, less the unused part of the current one, and the billing date moves to the day of the switch. A tier priced in another currency is not offered, since Stripe cannot change a subscription's currency. Nor is the switch offered when the paid plan or the target is a tier of more than one ladder: the switch ends the whole grant, and the other ladder would be left with nothing on it. A switch whose steps take longer than eight seconds can lose its answer page while its outcome still lands; #290 covers that. Stripe's charge credits the unused part of the period whose renewal was voided, so the member pays the price difference rather than the new price for that period, or, on a switch to another billing period, the new period less that credit; #280 covers it.
When the grant is of a lower tier than the paid plan, the paid plan's card offers Resume plan instead, and the tiers between the grant and the paid plan offer nothing. Resuming takes the ladder back from the grant for the plan the subscription already pays for, at its own price: nothing is charged at that moment, the pause is lifted at Stripe within seconds, and the next renewal is charged as usual. A downgrade the member scheduled before the grant, landing at or above the grant's tier, also takes the ladder back, and billing resumes at the lower price.
Commits:
23e5689d, 688e3622; built on84709d96(#285)