|
Tom Semmes
|
October 20, 2013 at 6:54 am
I keep getting the error message from Authorize.net
“The following errors have occurred. (14) The referrer, relay response or receipt link URL is invalid.”
According to my IT guy the relay response has been added at Authorize.net
It is the correct page. The one with the Espresso Payments shortcode.
I wondered if the page needed to be SSL protected. I added SSL protection to the page but it does not show the “https” in the Payment Settings page.
Now the IT guy might be wrong about the relay response URL but in case he is right is there anything else I can look into?
I am able to process credit cards with the Gravity Form plugin so I know the process is working. They don’t seem to require a RElay REsponse page. Can I disable that in Events Espresso in case we can’t work around this?
|
|
Sidney Harrell
|
October 21, 2013 at 9:11 am
What is displayed in the admin payment settings will be http or https based on whether the admin payment settings page is http or https. If you are forcing https on the relay response url page, then you will want to change it to https where you enter the relay response url in the authorize.net admin. Also, if you are not using https on the payment page that sends the user off to authorize.net for payment, then you will want to use the “force https on return url” option in the EE->payment settings->authorize.net settings.
|
|
Tom Semmes
|
October 21, 2013 at 9:46 am
Thanks. Though the Thank You page is SSL, the URL in the settings page is `http://`.
But I don’t think this is why I can’t get the relay return to work with Authorize.net.
The system works fine with Authorize.net AIM. My client thinks that somehow SIM is more secure since it is PCI-certified. Anything justification you know of why I should use AIM instead?
|
|
Josh
|
October 22, 2013 at 7:54 am
I think it’s a matter of preference. Some folks want to the payment form on their site, but some folks feel better about capturing/entering credit card info on a site like Authorize.net/Stripe.com/PayPal.com.
|
|
Tom Semmes
|
October 22, 2013 at 9:10 am
I found the solution. The Payment settings gave me a URL to add to the Authorize.net list or relay response URLs. It was wrong. Instead of starting with http: it should have started with https:. Since I tried both enabling and disabling SSL for that page, I don’t know if that made a difference; The URL always should have been https.
|
