#heisend3rp_webhooks
rough tinselBOT
👋 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/1351869800720105524
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
inner thicket
I don't see a refunds field in either of those events? We changed this in the 2022-11-15 API release – no longer included in Charge payload by default https://docs.stripe.com/changelog/2022-11-15/deprecates-charges-auto-expand
Do you have an example evt_xxx that behaves differently to the examples shared?
supple hatch
this is evt_3QoiV0Ltk7rShy5b0dLj1V81
inner thicket
Where is that screenshot from? Because that doesn't reflect the payload we actually sent to the webhook endpoint at https://mx-tickets.com/api/stripe/connect-webhook?version=2024-06-20
supple hatch
yes, i can see it now. if i scroll down to the webhook it does not show up, gimme one second, i think there was one that worked
humble hedge
Hey, taking over here. Let me know if there's any follow-up Qs I can answer!
supple hatch
ok, still here, just doing some research
supple hatch
found the bug, it was on our side. changed sth with metadata check last week. were just confused becuase we use the 'charge.refund.updated' webhook, but this one does not show up in the payment intent overview, only 'refund.updated' which did not fire any webhooks
thanks for the quick help 🙂