#sumeetcallenqcom_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/1361647278003326976
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
๐ happy to help
Create an event destination to receive events at an HTTPS webhook endpoint. Receiving webhook events is particularly useful for listening to asynchronous events such as when a customer's bank confirms a payment, a customer disputes a charge, a recurring payment succeeds, or when collecting subscription payments.
yes sure
I am not able to find the alert from the alert ID mentioned in above events
would you mind elaborating? I'm not sure I understand
would you mind sending the two alert IDs so I could check please?
From stripe dashboard alrt_test_61SNUKTkClEJnHgVb41HJgsdx4qPxQ88
From the alert webhook event alrt_test_61SNTukxr56pBsiuN41HJgsdx4qPxDMm
thanks
From stripe dashboard alrt_test_61SNUKTkClEJnHgVb41HJgsdx4qPxQ88
From the alert webhook (evt_1RE61XHJgsdx4qPxPMdPyle8) event alrt_test_61SNTukxr56pBsiuN41HJgsdx4qPxDMm
yes this seems super weird
I will send you a private DM to submit a case so my team could take a closer look on this