#CaptainYarb-pending-update
1 messages · Page 1 of 1 (latest)
Hi there, so your goal is to remove pending updates if the invoice attempts failed, correct?
Context: I'm resolving state management for the upgrade process in our app.
Bad Answer; I was under the (probably bad) assumption that once the invoice was marked uncollectable it would cancel the pending updates.
Realistic Answer: I am willing to remove it only if there isn't a better alternative.
Gotcha. Thanks for context. I'm looking as I don't recall off top of head best way to handle this. Can you share your subscription ID so I can also look at that as well?
sub_0L1BOzF23R9jbzPTVnx0OkHF
Request req_DY9JiAXPlk1Fw8 seems to have triggered the invoice to become uncollectable. Is this a setting?
The invoice will change state based on your Subscription Settings
Those settings are in your Dashboard here: https://dashboard.stripe.com/settings/billing/automatic
Got it!
That should help us avoid that situation. Is it still expected to resolve that pending update?
Still checking on that.
Great! Thank you so so much! 😄
Okay yeah so we discuss canceling or updating pending updates here: https://stripe.com/docs/billing/subscriptions/pending-updates#canceling-changing.
So you would void the invoice itself if you want to cancel it.
Dumb question: why is it our problem to resolve the uncollectable status differently from void?
Sorry not exactly sure what you mean by that?
You can dictate that the invoice voids via your Subscription settings if you so desire
Wait no
That's wrong
Sorry, yeah you are right
It would go uncollectible and you would need to void yourself if you so desired.
I hate it when I'm right in this discord LOL
lol
The thing is, you can just leave the invoice uncollectible if you want to.
The pending_update will expire
It leaves the user in a weird state. I guess my only resolution is a webhook to void the uncollectable invoice. :S
I do think that is the best thing to do here