#Thomas B-subscription-statuses
upper lake
Thanks bud. 🙂
If I am correct, then I guess that would mean that EVERYTHING in regards to handling access to Customers could be managed just with the customer.subscription.created|updated|deleted events and the status property they provide. Even failed payments since Stripe sends emails about the issue if I am correct + an hour after the failed payment an ...updated event would set the status to past_due so I can restrict access until it's active again.
- Can't think of anything missing, other than maybe retrieving the Invoice to provide a more specific fail message to the Customer.. But the access only itself, should be fine with the above only if I am correct. 🙂
foggy folio
Hey there, at least for unpaid you're correct, this would only be used if you configured your settings to do that.
ancient cradle
Also correct for not being incomplete if you have a trial.
foggy folio
Yes, that should always go active
upper lake
Sorry for the delay. 🙂
So just to be sure.. Does that mean that you agree with both of the two questions? All statuses to lookout for in a Subscription would be trial, active, canceled & past_due with the customer.subscription.created|updated|deleted events only? invoice.payment_failed is actually not really required.
(when using Stripe Checkout, a trial and all settings pointing to cancelled instead of unpaid that is) 🙂
Can you think of anything I could be missing?
foggy folio
If you don't intend to handle failed payments yourself, because you rely on Stripe's automatic collection/dunning then that sounds reasonable. After those payment attempts fail your subscriptions would follow the configuration you chose in settings and if the status was updated yes you'd get the subscription updated event
upper lake
Yeah, the only 'failed payment'-handling I would be doing is to restrict the access client side when a failed payment happens and the customer.subscription.updated event sets the status to past_due after that 1 hour. And then let Stripe handle the automatic collection and notifying via email and such. That should work just fine according to my research. 🙂
- But that sounds amazing. Awesome access can be handled with just those events and that one property, and Stripe handling all the failure stuff for us!
If you think all that sounds good and I am not missing anything obvious, then I would just like to say thank you once again for such quality help!
You guys are doing a great job. 🙂
foggy folio
Happy to help , and thanks!
upper lake
🙂 🙂 🙂