You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Subscriptions eventually get cancelled if they fail that max-retry-attempts number (e.g. 5).
This causes loss of revenue if not seen/caught- even with the payment failed notification emails which already get sent.
Describe the solution you'd like
If a subscription is cancelled by the lack of payments, send an email
to the subscriber and the shop owner to let all know, what their next steps are.
Describe alternatives you've considered
Additional context
Anecdote: The failed payment email notifications: "We don't need, all that does is fills up the mailbox. We don't need those"
The text was updated successfully, but these errors were encountered:
chrisjsimpson
changed the title
If a subscription is cancelled by the lack of payments, send email to shop owner and subscriber
If a subscription is cancelled by a lack of payments, send email to shop owner and subscriber
Mar 4, 2024
Is your feature request related to a problem? Please describe.
Subscriptions eventually get cancelled if they fail that max-retry-attempts number (e.g. 5).
This causes loss of revenue if not seen/caught- even with the payment failed notification emails which already get sent.
Describe the solution you'd like
If a subscription is cancelled by the lack of payments, send an email
to the subscriber and the shop owner to let all know, what their next steps are.
Describe alternatives you've considered
Additional context
Anecdote: The failed payment email notifications: "We don't need, all that does is fills up the mailbox. We don't need those"
customer.subscription.deleted
, andreason
object: https://docs.stripe.com/api/events/types#event_types-customer.subscription.deletedcancellation_details
within thecustomer.subscription.deleted
event object:The text was updated successfully, but these errors were encountered: