#stripe101-subscription-pause
stiff gate
You cannot update a paused subscription in a way that creates new invoice items. Unpause the subscription before attempting to update a subscription in this way.
stoic valve
gotcha so that must be because you're causing proration in that case which isn't allowed since the subscription is paused
stiff gate
that's a bummer. i wonder why it's designed that way. if invoices are still drafts why not draft the proration? ... i'm sure there's complexity i'm not taking into account ...
stoic valve
because proration doesn't make sense in this case since the user is not using the time during that period, it's paused
in some case you might just pause payments and keep access enabled, but some business block access during the pause and we can't really know
stiff gate
hmm, i'm thinking that if its blocked or not for the user doesn't matter - that is, if access is blocked than cool no changes are made in the subscription but if access is allowed for the user then changes can't be made to the Stripe subscription? - and so, what matters is the subscription can't be updated to reflect changes in the subscription during the paused time.
seems that it should be up to the Stripe consumer to decide what to do with the invoices that are drafted instead of Stripe not allowing those changes.
but again, i could be missing something
example, a company says they'll pause payments for a client but wants to keep tabs on their usage/prorations/qty/etc. so later they can go over the usage and decide how much to bill.
stoic valve
the problem is not knowing what users are doing and so we just block all writes for now
I agree we could offer the option, it's just not something I've seen anyone asked before and that feature shipped almost 2 years ago
stiff gate
haha, i'm the finder of the bugs.
yeah, its just not making sense to me why keep draft invoices and not draft prorations.
"the problem is not knowing what users are doing and so we just block all writes for now"
i don't follow. the api consumer decides when to increment a qty or update the subscription for a user. right?
why is the problem that stripe doesn't know what the user is doing?
stoic valve
I wouldn't call it a bug really, that's a decision we made, we block those updates and we'll see if devs want it different and you're the exception
stiff gate
ah, yeah, i was using bugs loosely. i agree its not a bug.
stoic valve
the problem is what if you use proration_behavior: 'always_invoice' for example, then what? Do we pay it synchronously, does it stay as draft? It's full of edge-cases so you start with the least permissive and you add things over time
stiff gate
yeah, as i've mentioned already, i understand there's complexity. i'm only trying to help - not being complain-y.
fwiw, in the case of 'always_invoice' i would expect that the invoice would be generated as a draft - since when pause is used i'd expect all invoices to be drafts, but still created.
stoic valve
yeah but that goes against the spirit of always_invoice :p
but really I've flagged internally as a feature request, I agree we could do better here. I just don't think we'll change this in the near future unfortunately.
stiff gate
cool thanks for entertaining my curiosity. its not necessarily something that's being asked for yet from my team, just an unexpected quirk i came across. an explainer in the docs would be helpful.
have a great weekend!
stoic valve
Sure and thanks for clarifying the use-case too, have a great week end!
ashen sierra
This feature has been disabled for this account. Please reach out to issuing-support@stripe.com for more information.、
how to slove this
@stoic valve