#stenerali_webhook-delivery-failure
stoic thistleBOT
👋 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/1216794890072232046
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
solemn rapidsBOT
uncut pike
Hi 👋
Taking a look at the event, I don't see any response from your server for the failed delivery
Unfortunately this isn't something I can shed much light on other than say that we did not receive any response from your server for the first delivery attempt, which is why the event was retried. The retry was handled successfully
gilded hull
is it normal for integrations to rely on webhooks for "real time" payment intents like credit cards? Retries would create a bad customer experience if we used them for marking the transaction complete.
uncut pike
Cards are a synchronous payment method so the API returns a status that tells you whether the payment was successful or a failure.
So, for that specific payment method, you can rely on API responses only. However, it's good practice to design your integration to handle asynchronous payment methods as well. For those we would recommend using webhooks to stay informed of payment statuses and update your customers.
gilded hull
thanks, i'll look in to it!
uncut pike
Happy to help 🙂