- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
webhook delayed notification
We are using the Accept Hosted redirect and have set up the webhooks. Right now we are seeing a delay in getting the notification back from our webhook. We are using PHP if this makes a difference. The delay could be from a few seconds on up and it seems like there should be a faster way to get this information. What is recommended? We feel that the customer is not going to wait for the response after already seeing their response come back on the Hosted Redirected form.
I have looked for examples of how to possibly query but have come up empty handed. There is a lot of information out there.
12-16-2021 07:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The purpose of webhooks is to receive real-time notifications, there maybe time when delays occurs, but this should be the odd cases, for failures there is a mechanism to retry sending the failed notification.
If your issue is persistent, you may want to contact Authorize.net Customer Support.
Thanks
-Mansour
12-20-2021 10:25 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I spoke to customer support and they said that the response could be delayed. I have added the refId and now I will try to use the get transaction details method...hopefully.
12-28-2021 05:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Goal here is to expose a simple HTTP POST endpoint. This endpoint must:
Receive webhooks
Store the request headers & body in a queue
Return an HTTP 200 status code
Once you have your webhooks in a queue, you can safely process them. Just be sure to do so at a rate that is reasonable for your infrastructure and use case. Different queues take different approaches to processing — but, generally speaking, you will want a set of worker services, each pulling from the queue at its own pace.
02-03-2022 08:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Webhook Delays can be cause by Zoom not receiving a 200 OK response from your Event Notification Endpoint URL after you receive a Webhook. In the case where a 200 OK response is not received, Zoom assumes the Webhook request failed, and will send it 3 more times.
02-06-2022 09:23 PM - last edited on 06-06-2022 06:39 AM by KH-Taylarie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Webhook Delays can be cause by Zoom not receiving a 200 OK response from your Event Notification Endpoint URL after you receive a Webhook. In the case where a 200 OK response is not received, Zoom assumes the Webhook request failed, and will send it 3 more times.
02-07-2022 10:54 PM - last edited on 06-06-2022 06:39 AM by KH-Taylarie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
have you used a API to integrate webhook for notification?
if so then I think you have to use twilio Because once I also had a similar issue when I am trying to integrate this with webhook via API, Which I fixed by using twilio...
02-08-2022 02:34 AM - last edited on 06-06-2022 06:40 AM by KH-Taylarie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I contacted customer support and they said this was normal that there would be a little bit of a delay. I eneded up calling the api for transactions and then searching for a match for the customer.
02-08-2022 07:08 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Web hook delays may be due to Zoom not receiving a 200 OK response from your event notification and point URL after receiving the web hook. In case the 200 OK response is not received, Zoom assumes that the Webhook request failed, and will send it 3 more times.
Regards: printers Insider
03-04-2022 08:13 AM - last edited on 06-06-2022 06:42 AM by KH-Taylarie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As a developer, ensuring your back-end works smoothly is key to delivering reliable services. If you don’t ingest and process your webhooks properly, you risk poor performance and server outages, which can negatively impact your product, your users, and your team.
In this language-agnostic reference guide, you’ll learn to take your webhook game to the next level by implementing delayed processing, one of the most important concepts when building reliable webhooks. Along the way, we’ll cover the basics of ingestion, queueing, processing, retries, and alerts.
03-16-2022 02:26 AM