|
clrc
|
September 11, 2018 at 9:26 am
Transactions through our Authorize.NET Gateway are failing, giving users the message “This registration step could not be completed. Please refresh the page and try again.” I’ve tried resetting the Authorize.NET transaction key and updating it in Event Espresso, but that didn’t work. I don’t see any error codes or logs on Event Espresso, so I can’t provide those. When I open the Transaction Session Details, I’m given a Registration Session ID and the following Step Progress:
Attendee Information : Completed
Payment Options : Initiated September 11, 2018 10:59 am
Finalize Registration : Never Initiated
I’ve spoken with Authorize.NET support and they are not seeing any record of the transactions reaching them.
Any ideas for how to resolve this?
|
|
Josh
|
September 11, 2018 at 9:31 am
Hi,
The recommended way forward will be to switch over to the newer Authnet Accept payment method because Authorize.net is phasing out SIM anyway. You’ll find more information here:
https://eventespresso.com/wiki/eea-authorizenet-accept/
|
|
clrc
|
September 11, 2018 at 11:20 am
Are payments in Authorize.NET Accept done within our website, like SIM or does it route users to another website to complete the transaction? We had feedback from our users that some of their PCards purchases were not accepted when they were sent to another domain.
|
|
Josh
|
September 11, 2018 at 11:42 am
The Accept gateway uses an iframe so the users are not redirected to another site like they’re redirected with SIM. SIM actually routes users to another website.
|
|
clrc
|
September 12, 2018 at 9:49 am
I tried installing the Authorize.NET Accept Gateway. Now the button at the bottom of the page freezes on “Processing…” I got a payment receipt from Authorize.NET so it must be getting to that point, but it’s not going to a confirmation page on our website. Any suggestions?
|
|
Josh
|
September 12, 2018 at 9:54 am
The way forward will be to follow the troubleshooting steps outlined here:
https://eventespresso.com/wiki/troubleshooting-checklist/
|
|
clrc
|
September 12, 2018 at 11:30 am
This reply has been marked as private.
|
|
Josh
|
September 12, 2018 at 1:18 pm
It looks like your server is blocking communication from Authnet. If you go to Event Espresso > Payment Methods > Logs is there anything getting logged there?
|
|
clrc
|
September 12, 2018 at 2:13 pm
This reply has been marked as private.
|
|
Josh
|
September 12, 2018 at 4:06 pm
Thanks for posting the screenshot, that’s not from the Payment Method logs. The Payment method logs are located in Event Espresso > Payment Methods > Logs.
Also, you could check the server’s PHP error logs (or if you followed the troubleshooting steps from the documentation, WordPress will write the PHP errors to a debug.log file in the wp-content directory). The PHP errors may have helpful information too.
|
|
clrc
|
September 17, 2018 at 8:12 am
This reply has been marked as private.
|
|
Josh
|
September 17, 2018 at 10:34 am
Hi,
I’m afraid the PHP error log shows nothing related to using the Authnet gateway, and the log entry you sent says the payment transaction was a success.
May I ask which browser are you using when you test the gateway?
|
|
clrc
|
September 17, 2018 at 12:05 pm
This reply has been marked as private.
|
|
Josh
|
September 17, 2018 at 12:20 pm
May I ask is that an apache server or nginx?
|
|
clrc
|
September 18, 2018 at 7:12 am
This reply has been marked as private.
|
|
Josh
|
September 18, 2018 at 7:19 am
OK good. Can you check the .htaccess file to see if either of the following are set there:
Content-security-policy
X-Frame-Options
|
|
clrc
|
September 18, 2018 at 9:59 am
This reply has been marked as private.
|
|
Josh
|
September 18, 2018 at 10:33 am
OK I think you’ll need to remove that in order for the Authnet iframe do be allowed to work with your site.
|
|
clrc
|
September 18, 2018 at 2:23 pm
This reply has been marked as private.
|
|
Josh
|
September 18, 2018 at 2:25 pm
You could use the AIM payment method, which does not use iframes. The AIM payment method is bundled with EE4 core.
|
|
clrc
|
September 19, 2018 at 7:27 am
This reply has been marked as private.
|
|
Josh
|
September 19, 2018 at 7:53 am
Does the PHP error log show what the 500 error was? Many times there will be an error that’s labeled “Fatal Error” when there’s a 500 error.
|
|
clrc
|
September 19, 2018 at 8:38 am
This reply has been marked as private.
|
|
Josh
|
September 19, 2018 at 8:51 am
That explains it. The Authorize.net AIM gateway requires the CURL module. You or your host will need to install CURL support for PHP. Can you contact your host to see if they can install this?
|
|
clrc
|
September 19, 2018 at 10:42 am
That fixed it. Thank you!
|
