subscription-use-cases
subscription-use-cases copied to clipboard
Ambiguity with regards to proration
Bug report
Describe the bug
The docs have some ambiguity as far as how to prorate per-seat licensing.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
- Go to https://stripe.com/docs/billing/subscriptions/per-seat#change-price
- Note the example has you manually create an invoice then pay it immediately.
- And yet, there's also an entire set of
proration_behavior
options.
Ambiguities
- Why does this example manually create an invoice and bill it?
- What's the difference between doing that and instead just passing
proration_behavior
into theSubscription.modify
command? - If the example can be simplified by using
proration_behavior
, then what's the right value to use to mirror the documented example? - When you go on the Stripe dashboard itself and manually increase/decrease per-seat quantities, what's the behavior being applied behind the scenes? Basically, what value is used for
proration_behavior
there?
Thanks guys. Great docs, just some ambiguity.
@silviogutierrez - thanks for the feedback, you're absolutely right that we should clarify this ambiguity in the guide and the repo. We don't have a PR ready yet but will be working on something, stay tuned!
Thanks @dawn-stripe . I look forward to the updates.
Do note I filed another issue (#29) related to the same documentation
Any updates on this?
Hello, This issue seems to be not a sample of this repository, but rather feedback related to Stripe Docs. In the past four years, the content and sample code in Stripe Docs have been renewed.A page related to proration has also been added, so please check it out. https://docs.stripe.com/billing/subscriptions/prorations
Additionally, feedback regarding Stripe Docs can be submitted through the "Was this page helpful?" section located at the bottom of the page. You can directly send feedback to the Document team, so please make use of it.
Best,