#shybes_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1352359755791863862
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi Pompey, how you doin?
Doing well!
great to hear it
It seems like what I found is a pretty big bug on stripes' end, but, I just wanted to confirm
Figured I should report it to you guys and double check we don't have something configured wrong
Interesting, do you have the ID of the subscription that this happened with?
Yes
Let me pull it up
sub_1Oo9h2GPm0Cf1OFAPVjmv2ka
It seems like after the subscription_delete event was handled, the user was still able to update their payment method and be charged, but, the subscription could not update as it had been deleted
My guess is that it got wonky because the user updated their payment method with Link
They also updated their payment method within 7 minutes of the subscription being cancelled on the backend, which also probably added to the issue
Here's the log history if you dont already have it pulled up
Ah gotcha, that is actually expected behavior. Subscriptions being cancelled is a terminal state, so a new subscription would need to be created at that point. I think your dashboard settings can allow you to void invoices when the subscription is deleted
Interesting ok
Any guidance or FAQ articles on how I can void invoices after the subscription has been deleted? I'd assume I can change it right now.
It looks like our dashboard setting only supports leaving the invoices as is and marking them as uncollectible, both of which leave the invoice still payable. So I think what you will want to do is have your integration listen for customer.subscription.deleted events and then make a call to void the latest_invoice on the subscription for that event
Our app has been live for a while, so I feel like we would have caught this in the past
Or can you direct me to the documentation for subscription mangement that mentions this quirk so I can be sure we don't run into similar issues with the platform going forward?
I'm not really seeing a callout of this specific aspect of this behavior in our docs. These docs are pretty good overviews of how invoices and subscriptions work, but they don't really go into implications like that
https://docs.stripe.com/invoicing/overview
https://docs.stripe.com/billing/subscriptions/overview#voiding-invoice
Haha we've definitely gone through those plenty of times. We've got some pretty angry customers over here, so I'd urge the team to at least get quirks like this mentioned on the FAQ asap
or, ideally, provide a config to auto-void invoices after subscription_delete events ๐
Yeah I will add feedback about that and see where we can put this in the docs, I am a bit surprised we don't support auto-void
Awesome. While I have you, do you have any guidance on how I can start a new subscription for the user without charging them? I believe I could just start a new subscription and just set the "Bill yearly starting" to March 20, 2026
But, I worry that they'll be charged for the year of 2025 on march 20, 2026, not for their year of 2026
(ie. payment at end of period vs. beginning of period)
Good question, I think you would either want to create the new subscription with either a credit note for the full amount or a one-time 100% off coupon.
yeah I figured the coupon might be the better option too, was just trying to avoid extra steps xD