A member cannot arrange for a subscription paused by an operator's grant to continue on the granted tier or a higher one when the grant ends #279
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#279
Reference in New Issue
Block 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, for a term or with no end date. 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. When the grant ends, by expiry or by an operator's revocation, collection resumes and the subscription's own tier is delivered again (#270).
So an organization granted Max while it pays for Plus drops to Plus the moment the grant ends. It cannot arrange in advance that Max, or a tier above it, carries on as its paid plan from that moment. Its only way to keep Max with no gap is to pay for Max while the grant still gives it, which #278 would allow, at the cost of paying for a tier the grant already covers.
What they should be able to do
While the subscription is paused, choose on the card of the granted tier or of a tier above it that the subscription moves to that tier when the grant ends, and nothing is billed until then. The card shows the chosen tier while the choice stands, and the member can withdraw it. When the grant ends, the act that ends it (the expiry or the revocation) moves the subscription to the chosen tier and resumes collection in the same step that delivers the subscription's tier again today, so delivery has no gap and no period is billed twice.
A grant with no end date gives Stripe no date to schedule the move against, so the console makes the move itself when the grant ends, rather than through a Stripe subscription schedule.
Why it matters
A member who wants to keep the granted tier, or have more, after the grant can neither do it without paying twice nor be sure of it without watching for the grant's end.
Where
The acts that end a grant, a revocation and an expiry, where #270 delivers the subscription's tier again; the paid plan's card on the Products page (
internal/server/member_plans.go,internal/embeds/templates/partials/member_plans.html); the switch at Stripe (internal/fulfillment/plan_change.go); the console's record of a scheduled plan change, which today holds moves Stripe fires at a period boundary.Done when
A member whose subscription is paused because a grant holds its ladder can choose the granted tier or a higher one for when the grant ends, see that choice on the card and withdraw it; at the grant's expiry or revocation the subscription delivers the chosen tier and is billed for it from that moment, with no gap in delivery; and a test drives the choice through an expiry and through a revocation, at the granted tier and above it.