Reply
Member
Posts: 2
Registered: ‎12-30-2011

SIM relay response error

[ Edited ]

I am using SIM method in asp.net for payment, after user submits information to "https://test.authorize.net/" ,instead of redirecting to my local site using response relay, I am getting this error

 

"An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

      This transaction has been approved.
It is advisable for you to contact the merchant to verify that you will receive the product or service."

 

 

Could you please tell me what I am doing wrong and How can get the response of transaction on my local site in ASP.NET.

Posts: 1,476
Topics: 33
Kudos: 37
Solutions: 126
Registered: ‎09-14-2009

Re: SIM relay response error

This error can happen for a variety of reason and has been asked here often. Start by reading the blog post Relay Response Basics and Troubleshooting and don't forget to search the forums, too, as relay response questions have een asked often. They seem to be caused by slow webservers or coding issues the majority of the time so I would start by looking there.


-------------------------------------------------------------------------------------------------------------------------------------------
John Conde :: Certified Authorize.Net Developer (Brainyminds) :: Official Authorize.Net Blogger

NEW! Handling Authorize.Net's Webhooks with PHP

Integrate Every Authorize.Net JSON API with One PHP Class (Sample code included)

Tutorials for integrating Authorize.Net with PHP: AIM, ARB, CIM, Silent Post
All About Authorize.Net's Silent Post
Posts: 1,609
Topics: 15
Kudos: 209
Solutions: 121
Registered: ‎06-23-2011

Re: SIM relay response error

Make sure the relay response URL is configured in your control panel to match whatever you're passing from your script.

 

Make sure the URL works. If your site lags or dies randomly, that could be what's causing the problem, in which case you need better hosting. Also, Authorize.net can only access standard http or https ports (80, 443).

 

If using SSL, make sure it's from a major issuer and that it's current.

 

If that doesn't identify the problem, try increasing the refresh time on your domain's DNS from the default (usually 1 hour) to something a lot larger, like 7 days. Sometimes DNS lookup is slow due to nameservers or whatever, and if Authorize.net is taking more than 10 seconds to look up the domain, that particular relay response is going to time out. At least increasing the refresh will reduce the problem to once every 7 days (or whatever you set it to).