First sorry for my bad english,
I have a problem with the SIM relay response, i have always 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.
I have read 4-5 topic about this error, but nothing resolve this error.
What i have check :
- Relay URL the website is using (x_relay_url) <-- THIS is OK
- Confirm that you can load the Relay URL in a Web browser <-- THIS is OK
- can only use ports 80 and 443 for all Web traffic. <-- THIS is OK
- review the settings to ensure that the correct Relay Response URL is configured in your account <-- THIS is OK
The account is in test mode and this is my PHP code :
Payment Form :
<form method='post' action="https://secure.authorize.net/gateway/transact.dll">
<input type='hidden' name='x_relay_response' value="true" />
<input type='hidden' name='x_relay_url' value="http://www.woolandthegang.com/basket/authorize" />
<input type='hidden' name='x_relay_always' value="true" />
And my relay url is :
(you can check this url, the delay is verry good and all is OK)
Do you have an idea of what is the problem ?
Ok. Here is what I found. Note, I'm using asp.net
1)It error "The remote server returned an error: (403) Forbidden."
when doing a "POST" method WebRequest in code to http://www.woolandthegang.com/basket/authorize . It work fine with "GET" and "PUT".
2)It will work with "POST" method if I add a UserAgent e.g. "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)".
Since the relay response use the "POST" method and I don't think authorize.net will add a fake UserAgent. It might be setup change on your apache site.
You'd think the UserAgent would be set to something - but on the other hand it's a little silly to block access to blank UserAgents as well, considering they're set by the computer initiating contact and any hacker is going to take about 30 seconds to get around that problem. Any chance of your hoster changing the settings for you?