cancel
Showing results for 
Search instead for 
Did you mean: 

Relay Response (SIM)

I know there are a number of threads open in regards to SIM and the relay response URL, but since those seem to be resolved and I don't see where they resolved it, I thought I'd try a new thread.

 

I am having a problem getting the relay response URL to work through the SIM method in the development environment.

 

I set up my developer account to have a default relay response URL.  I've ensured it's a valid URL and is accessible to the outside world.  It's a simple HTML form just to ensure there are no other issues with response times.  Once the checkout page submits, it the progress bar sits for 5, maybe 10 seconds then it returns the standard error message.  The Transaction Error Notification email  I receive has this in it's text:

 

Your script timed out while we were trying to post transaction results to it.

   Transaction ID: 0

Transaction Result: This transaction has been approved.

 

I've tried it with the URL in the x_relay_response_url and without it.  I'm not sure what I'm missing here.

 

This is one of the last steps I need to get this process rolling (I need to validate the returned form) but until I hit this, I was doing OK.  I had customized the header and got all the form values loaded, so I'm not a complete idiot (though stymiee may disagree on that point from his days at SPF).  But this is baffling me.

davemaxwell
Member
22 REPLIES 22

Are you setting the x_relay_url on the submit page or using the default on the merchant account?

Were you able to resolve this? My app is also experiencing the same issue. Starting 01/23/2014, Authorize.net has stopped posting relay responses to my server. I did not change anything on my end. It was sporadic at first, but now no trascations are working properly. 

 

Thank you for your help!

Hello @venturebang,

 

We're not aware of any production issues that would impact your system from working.

 

If you continue having this issue, I would recommend opening a new thread with the specific troubleshooting steps you have performed so we can take a fresh look at the problem.

 

Richard