#shehzadnizamani_webhooks
true pivotBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- shehzadnizamani_docs, 1 day ago, 7 messages
limber larkBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1260238246408093919
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
median pulsar
Hi there 👋 if your flow always generates a customer.subscription.updated Event when the Subscription first becomes active, then listening for that and specifically looking for the status switching from incomplete to active sounds like a good approach. I believe it's possible to create Subscriptions in such a way that they only generate a customer.subscription.created Event when they start, but if that isn't part of your flow you may not need to listen to those.
gleaming monolith
Hi Toby,
Could you send me a link to the document for flow you are talking about when only customer.subscription.created is generated?
What I have done is I followed your guide from this documentation:
https://docs.stripe.com/billing/subscriptions/build-subscriptions
I create a checkout session on backend and then follow the checkout link, when I complete purchase it generates two events right now as I mentioned in my OP
median pulsar
If you're using Checkout Sessions, I don't believe the other flow I referenced is relevant. That may be relevant if you were making requests to create Subscriptions directly, rather than letting the Checkout Session handle that.
gleaming monolith
Ok thank you for your help Toby, sounds good then we will only listen for customer.subscription.updated event and only activate user's subscription in our system when their status switching from incomplete to active
Thanks for your help, this issue is resolved
median pulsar
Any time! I would strongly recommend making sure that works the way you're hoping in testmode before going live, you can use test clocks to help with that testing, but I think it'll be sufficient for you.
https://docs.stripe.com/billing/testing/test-clocks