#Jangus
nimble aspen
copper depot
Event: evt_1MUnc1CdDL2ItXJ9WY3xMhZv
Customer: cus_N1rtZ47E5MbXRZ
Subscription: sub_1MHo9eCdDL2ItXJ9iPjrkWXm
gritty dust
Hi, can you share the request id for the subscription? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Thank you, taking a look
Thank you for your patience, still taking a look on my end.
copper depot
Thank you!
gritty dust
So any invoice created before the subscription cancels can still be paid. Canceling a Subscription does not void or cancel outstanding Invoices. You'd need to be void, https://stripe.com/docs/api/invoices/void them manually. Here is a documentation on how this work: https://stripe.com/docs/billing/subscriptions/cancel#invoice-items-and-usage.
copper depot
But... we didn't cancel the subscription. How did it get canceled?
The event says it was done automatically, but why?
gritty dust
I was able to confirm that this was cancelled to a Failed Payment. After the subscription was cancelled, they tried paying the invoice and it looks like that succeeded
copper depot
And it all just happened within a few minutes of each other? Weird. All of our emails are done through Stripe. How can the system automatically cancel a subscription and allow them to pay for it without us being notified? That seems like a major flaw. Is there anything we can configure to avoid this?
gritty dust
you can listen to this customer.subscription.deleted events and void the invoices that way.
copper depot
Okay, we can hook that up on our end. I guess I'm confused–given that this was all automated through Stripe, it seems weird that we have to manually manage that edge case 🤔
Follow up question - as per our Subscription settings, we shouldn't cancel the subscription until the payment is incomplete for 15 days.
The invoice with the failed payment came out on January 22nd and the subscription was canceled on January 27th, only 5 days later.
What triggered the cancelation? Why did this failed payment cancel the subscription?
left void
Hi @copper depot I'm taking over, give me a sec to catch up
Is it the same subscription ( sub_1MHo9eCdDL2ItXJ9iPjrkWXm ) that you are talking about?
copper depot
That’s right!
left void
There's another payment failed event on Jan 27 https://dashboard.stripe.com/events/evt_1MUnc1CdDL2ItXJ9iNaibKme that happened right before the customer.subscription.deleted (evt_1MUnc1CdDL2ItXJ9WY3xMhZv)
copper depot
Why would that cancel the subscription though? 🤔
left void
Did you change the Smart retries settings (https://stripe.com/docs/billing/subscriptions/overview#smart-retries) recently? Stripe will cancel, make as unpaid or leave it as is based on your settings.
copper depot
Hmmm, I don’t believe so, but someone on our team may have. I’ll go with that for now and hope this is a one off. Given this situation, is there anyway at all to mark that subscription as active again?
left void
canceled is a terminal state that can't be updated. Hmm, looking at your subscription again, it's still active but there's a customer.subscription.deleted event, it looks odd to me.
This is going to require a bit more investigation. Sorry to redirect you, but can you write in to https://support.stripe.com/contact/email with the information and subscription ID that you provided. We'll respond via email/ticket after looking into it further.