Posted: June 24, 2014 at 10:04 pm
|
WordPress v 3.9.1 Not new, not recently upgraded. http://www.westerncoloradoconcert.com/buy-tickets I think there’s something going on with the relay response, but no combination I’ve tried has solved the problem. I’ve Added ../thank-you and ../?page_id=10 to the relay response settings in Auth.net, I’ve added MD5 hash, I’ve turned force HTTPS on return off and back on and I’ve deactivated and reactivated Authorize.net SIM. I get a receipt from Authorize.net, so I know the transaction is going through, but EE isn’t getting the message for some reason. I tried (unsuccessfully) to find an ipn log. |
|
UPDATE: I turned logging on and determined that Auth.net is responding with “x_response_code = 1 & x_response_reason_code = 1 & x_response_reason_text = This transaction has been approved” but, EE is not updating the payment status. |
|
Hi, Is it not updating on just the front end or both the front end and the admin? |
|
It’s not updating on either the front or back end. The return page does load, but it shows the payment status is incomplete. |
Hello, Could you share some information about this plugin: SSL 1.0 Is it similar to WordPress HTTPS? Any security plugins being used on the site or is that the complete list? — |
|
|
It’s the Event Espresso – SSL/HTTPS plugin |
|
I’m not using any security plugins. I was using IQ Block Country, but I disabled it because I thought that might be interfering. That did not help. |
Hi there, The issues you’re running into are likely from using the out dated Espresso SSL plugin, which was dropped two years ago. You can use the WordPress HTTPS instead to secure your pages. |
|
|
I removed the Event Espresso HTTPS plugin and installed WordPress HTTPS. Then, I verified the pages that were forced to use HTTPS. No change. |
Which pages did you verify? |
|
|
“Secure post” is checked on the pages containing the following short codes: [ESPRESSO_EVENTS] |
It may help to change unsecure the page with the espresso_payments shortcode -or- alternatively go into your authorize.net account and make sure it’s pointing the a relay response URL that has https in it. Also, please note that while the site is in maintenance mode, Authorize.net will not be able to communicate with your site. You will need to put the site in live mode in order to test payments. |
|
|
SUCCESS! For anyone else who might have this cantankerous problem in the future, here is how I fixed it: In Authorize.net SIM payment settings: UNcheck force HTTPS on return and UNcheck MD5 Hash Thanks for your help, Josh, Lorenzo and Dean, I really appreciate it. See you at the show. HA! |
The support post ‘Authorize.net SIM Gateway not Working’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.