#hephe_webhooks
1 messages ยท Page 1 of 1 (latest)
๐ 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/1227666876365279313
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello! We show that evt_1P44EyRtWHFwXPdFvIKQ9j3P was successfully delivered to your Webhook Endpoint.
You should be able to see the successful delivery details in your Dashboard here: https://dashboard.stripe.com/events/evt_1P44EyRtWHFwXPdFvIKQ9j3P
Hey! Thanks for the quick reply. That is indeed correct, however based on the test env/account I was expecting to receive a customer.subscription.updated. The one you linked says: customer.subscription.created. Sorry if I'm missing anything!
Ah, sorry, checking...
this is on my test account/env:
Yeah, there is no customer.subscription.updated Event for this Subscription because it's never been updated. There's only the customer.subscription.created Event.
correct, just wondering what am I missing that I don't get that event
The Subscription immediately became active when created and hasn't been updated, so there is no .updated Event to send.
ohh ok
and is there a way to have the customer.subscription.updated event sent somehow?
right, so I need to update my code basically:
You need to change your code to also listen for customer.subscription.created Events and handle them appropriately.
roger, then just last question for my sanity please: why is this being send in test data setting/mode?
is there a rule to it? just want to make sure I cover all cases
In test mode the Subscription originally had a status of incomplete when it was initially created. Then a payment was made, which transitioned it to active and resulted in the .updated Event. This is the request that triggered the .updated Event: https://dashboard.stripe.com/test/logs/req_fHfcfhVJ6YmqMn