Is there a timeout, and if so, what is it???

[danmar]

I work at a service provider that has several clients using Authorize.net as their payment gateway.

Our system has a 60-second timeout for API requests, and if a transaction takes longer than that, our system will not receive the response about the success or failure of the transaction. This happens infrequently but often enough that some of our clients have noticed and reached out about it.

We are trying to evaluate what will provide the best user experience, and part of that is to determine whether Authorize.net's payments API has a time out, and if so, how long the timeout is. Or, is there a recommendation or best practice for how long we should wait for a response before timing out the request?

[tadchristiansen]

We have the same question. Last year we had ours set to 30 seconds and were told to set it to 60 seconds to make sure we give them enough time to respond. We still run into issues though where we don't receive a response after waiting 60 seconds. It would be nice if they would terminate any transactions that take longer than 30 seconds so we do have to worry about duplicate payments on a retry. What did you end up doing to handle this?