Expected response time for Webhooks and policy to deal with Webhooks responses that extend beyond that time limit

HIU Implementation
#1

Hi @adnan_360
We need to know the expected response time for all the Webhooks. Without this knowledge it is not possible to properly implement a retrial mechanism for the end user. If we implement a custom timeout on our side, it can create problems like this:
Suppose we set a timeout of 4 hours, but a particular HIP’s response always arrives in 5 hours, then on every subsequent retrial, our shorter timeout will trigger before HIP’s response reaches us, and hence there will be no way to actually process such a response, unless we keep track of all past requests for which Webhooks did not arrive in anticipation that they might arrive.
Also, in case an expected response time for Webhooks is communicated to us, we need a mechanism in place to inform us in face of a delayed webhoook response, preferably in response of the gateway call we make on retrial, the Webhooks response for our previous api call.

#2

@IntegrationSupport: Can you please let us know the timelimit of the following

  • Response time limit on the Gateway’s API

  • Time limit within which HIU/HIP’s will get the response on the callback-url

#3

@ashishkyogi response time limit on the Gateway’s API: every api have different response time. For all gateway sessions will be 30 sec only.

  • Time limit within which HIU/HIP’s will get the response on the callback-url - 3600 seconds
#4

@IntegrationSupport
Is there a time limit within HIU/HIP server supposed to respond to requests (callbacks) received from Gateway ?

#5

@IntegrationSupport: Can you respond to this last question please?

Is there a time limit within HIU/HIP server supposed to respond to requests (callbacks) received from Gateway ?

thanks

#6

@ashishkyogi already responded in the thread - 3600 seconds