#kreesm23_webhooks

1 messages · Page 1 of 1 (latest)

pastel stumpBOT
#

👋 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/1303088321118863461

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

cobalt cipher
#
  1. Once the free trial is over, what events do I need to capture to ensure a user is kept/removed on my app?
    Hello, can you tell me more about this. Are you trying to do something like send a reminder if they don't have a payment method saved by the end of the trial? Or something else?
#
  1. When a user cancels their subscription, what event do I watch for/how do I setup to ensure their access is removed at the end of the current period, not immediately?
    If you let them change things via our Customer Portal, there is a setting for this in your Customer Portal dashboard settings. If you are making API calls to cancel the subscriptions, you can set cancel_at_period_end to true to accomplish this.
unique juniper
#

Hi Pompey.

  1. For the end of the trial, I need to know what changes occur on the backend i.e. does the subscription status change? In essence, once a trial ends, what events occurs such that I can decipher whether or not to keep a user on my app?
pastel stumpBOT
unique juniper
#
  1. Understood, thank you.
languid pumice
#

Hi, I'm stepping in and catching up.

#

You can let Stripe handle sending the email as a reminder for when it would expire: https://docs.stripe.com/billing/revenue-recovery/customer-emails#trial-ending-reminders. However, if you're looking to handle this on your end/ add logic to how you handle these we document the events you'd want to listen to here: https://docs.stripe.com/billing/subscriptions/event-destinations. Specifically, you'd want to listen to customer.subscription.trial_will_end. This event is sent three days before the trial period ends. You would also want to look at this document, https://docs.stripe.com/billing/subscriptions/overview and https://docs.stripe.com/billing/subscriptions/overview#payment-status. If there is not payment method for that subscription, https://docs.stripe.com/billing/subscriptions/overview#requires-payment-method the subscription would be in incomplete status.

unique juniper
#

Thank you! From the docs you shared, can I conclude that I can activate/reactivate/deactivate my app users by solely listening for the customer.subscription.created , customer.subscription.deleted and customer.subscription.updated events? Or should I be watching invoice events too? I'm simply looking to activate/reactivate/deactivate them based on whether or not their payments are up to date

languid pumice
#

No, I think you would want to listen to invoice level events: https://docs.stripe.com/billing/subscriptions/event-destinations#payment-failures. It all depends on what specifically you're looking to do and overall up to you. You could just look at the subscription status, https://docs.stripe.com/billing/subscriptions/overview#provisioning as you mentioned to provision. However, if you're trying to add logic depending on if the payment failed or not, you would want to listen to https://docs.stripe.com/billing/subscriptions/event-destinations#payment-failures for instance.

unique juniper
#

got it, happy with that. I think you've given me all the documentation I need to get started with some basic dev. Thank you for all the help 🙂