#eoghanobrien_webhooks
valid aspenBOT
đ 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/1267973336986816592
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
dry radish
Hi there
gloomy silo
Hi
dry radish
Ah, I think in this case we don't actually create the invoice so the only events to look out for are charge.failed and payment_intent.payment_failed
gloomy silo
and payment_intent.canceled I guess
that's strange though because it starts off with the context of the subscription but loses that context as it processes payment
I just wanted to confirm that there's nothing else I can do to get that context back
dry radish
Hm, I guess you could use pending updates: https://docs.stripe.com/billing/subscriptions/pending-updates
and inspect the pending_update hash
The 402 you received in this case ties back to payment_behavior: error_if_incomplete since this was the default behavior with the API version you're using: https://docs.stripe.com/api/subscriptions/update#update_subscription-payment_behavior
gloomy silo
So in that case what would I be inspecting the pending_hash for exactly? To see if it changed?
dry radish
The pending_update hash would include details about the changes you tried to make but are now "pending" until a payment succeeds