|
|
I would have posted this to topic “Authorize.net SIM integration – post payment transaction timeout, HELP PLEASE!” but don’t seem to have the authority to do so. The problem is authorize.net SIM declaring a timeout when waiting for the Relay Response (Thank You) page from Espresso. I have communicated with Authorize.net on this and this is the thread so far: ME: I am in integrator with several sites using SIM and Relay Response. I persistent problem is Authorize.net timing out when accessing the site’s relay response page. I have seen elsewhere that you say you want 10 seconds for a response. Our page reacts in 1 – 2 seconds, but times out. Paring it down to respond in less than that fixes the problem, but it not always a satisfactory solution. Please have your developers confirm that you’re not waiting long enough for a response, and fix accordingly. Searching the net indicates many others are having the same problem. THEM: The timeout error can occur anytime during the 10 seconds our system waits for a response from the website. We are not able to change the waiting time our system takes. ME: That makes no sense to me. Either you wait 10 seconds for a response or you don’t. A timeout would be if you got nothing back after 10 seconds. If you declare a timeout before 10 seconds then you’re not waiting 10 seconds. The proof of this is that you timed out after 1 to 2 seconds but not after 0 to 1 seconds (when I simplified the response page). Please have your developers confirm that you are waiting the full 10 seconds for a response before declaring a timeout. Please search the web to confirm that lots of people are having just the same problem. With PCI forcing more and more sites to use SIM, it’s important that you get it working right. Their reply seems nonsensical to me. I’ll keep you posted.
|
|
|
|
|
|
Continuing my dialog with authorize.net on this issue: Them:Can you tell me when this issue occurred last, and how frequently it has occurred. We did discover an issue with Relay Response that we resolved last week, and the merchants we were working with confirmed that the issue was resolved for them. Please note that the issue is that there are possible connection issues which would cause the “Unable to Send Notification” error to occur far faster than 10 seconds. If it appears we can connect to your server, but it takes 10 seconds or longer to complete the connection, then the connection would in fact time out. But if there is a connection issue–such as refused connections, DNS issues, or SSL issues–the Unable to Send Notification error would occur in less than 10 seconds. To help you resolve this issue, we would like to know what specific troubleshooting you have done, and the results. If you have not done so yet, you may want to consider using our testing environment to help test your setup. You may sign up for a test account at https://developer.authorize.net/testaccount/. Me:Thanks for a much better response. I can tell you that there are no public connectivity issues with the site. I can also tell you that, when I stripped down the response page to its minimum, you do not time out. Also, even with the unstripped-down version, when I instrumented the time between first seeing the request and delivering the page, the elapsed time was only 1-2 seconds. This, of course, does not take into account any delay in us getting the request or you receiving our output. I am not in a position to try this in your test environment, but I am confident that the code is OK because the site is not timing out with the stripped-down response page, which responds in less than 1 second. This testing was all done last week so would be post the change you mentioned. I would say that an overall 10 second timeout is too short, if that’s actually how long you’re waiting, when you take into account the potential latency just getting the request to the Relay Response server and you receiving the reply after it is sent. I have seen comments about sending at least something back to the caller (you) earlier in the Relay Response page. Although this might help, it complicates the site as usually the output is buffered and sent in at least 4096 byte chunks. It would require special handling of the Relay Response page. I would think a relaxing of the 10 seconds to more like 20 would be a reasonable fix. Watch for more follow-up later.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The support post ‘Authorize.net SIM integration – post payment transaction timeout’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
