09-09-2014 08:43 PM
Full url is required because authnet is posting response to your server and relative urls will not work.
Also, you are required to specify the "full url of the file" that will be receiving the relay-responses, both in your code as well in the Merchant Panel. It is a sort of cross-verification by Authnet to ensure that only the urls listed in the merchant panel get the relay responses.
An example of a relay response URL will be: http://yourdomain.com/payment-folder/relayresponse.php
I hope this helps.
09-10-2014 12:33 PM
Wow! That is insane! :smileylol: How can I add all my relay URL when it's all dynamic because it's an Event Registration payment.
Do you happen to work on this using Sandbox?
I actually work on the payment gateway code authorize.net sandbox and using relative URL, everything works fine until I switch to live where I constantly getting that replay response error.
Auth.net engineer, anyone from you, please comment to this. I just need a clear answer on how to fix this issue.
09-10-2014 12:44 PM
It work on the sandbox? Did you have the relay response url setup on the sandbox account? are they the same as the production account settings?
Are your sandbox account test on the same server as the when you switch to live?
The other way is to ask the developer support to see what response are they getting when they post the response to your relay response url. http://developer.authorize.net/support/
09-10-2014 12:56 PM
Here's my setup.
Authorize.net Sandbox has to be a different account from the Production Live Merchant Account, unless, I'm wrong understanding this. But I created an entirely new Sandbox Merchant account separate from our Production Merchant Account.
Sandbox Relay/Receipt URL
Live Relay/Receipt URL
Both installation are running on the same server by different Apache host name and all the settings are identical.
In Sandbox installation, I am not getting a Relay error and I am sure it relay back because whatever I echo out on the relay url gets printed in the scree.
On the other hand, on Live installation, I don't get any of my echoed text. It's like Authorize.net never even bothered to relay it and just spit an error.
09-10-2014 01:07 PM - edited 09-10-2014 01:20 PM
So it running https? I remember authorize.net having issue with some ssl cert. might need to search on the forum.
SNI not supported