Connection Timed Out because plugin tries HTTP instead of HTTPS

Hi TechDaddyK

I just checked on my local installation, and everything seems to work fine.

Url where user is redirected for payment is hardcoded in plugin script, and protocol used in https

(you can check it in wp-content/plugins/yith-woocommerce-authorize-net/includes/class.yith-wcauthnet-credit-card-gateway.php:46

const AUTHORIZE_NET_PRODUCTION_PAYMENT_URL = 'https://secure.authorize.net/gateway/transact.dll';

)

Can you please share with us a link where I can check your installation?

Thanks for your patience!
Have a nice day! ??

Thank you for replying. That particular problem seemed to go away, but we still haven’t been able to get ANY successful transactions to go through. I just tried two test orders and received two different results…

ORDER 1 seemed to go through fine; I received both order confirmations (customer and internal) and the Merchant Receipt Email from Authorize.net. However, I show in WooCommerce that the order is on hold because of a verification error:

Validation error: Authorize.net responses from a different email address than (BSFf33ds). Order status changed from Pending Payment to On Hold.

ORDER 2 failed, displaying the following message to the “customer” (at the URL https://secure2.authorize.net/gateway/transact.dll):

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.

(A real customer also complained she received the same error message.) I received both the customer receipt and merchant receipt from Authorize.net on this one, but WooCommerce did not send order confirmations… presumably because the error message occurred before the transaction made its way back to our website.

I verified that Authorize.net is not in “test mode” and the transactions all show in my Unsettled Transactions in Authorize.net.

Any additional insight you can provide would be greatly appreciated.

Oh, the store is at https://bluesealcountrystore.com.

Hi again, TechDaddyK

I’m sorry for the issue you’re experiencing; thank you for your patience!

I checked your checkout process, and all seemes to work just fine until authorize.net page (to proceed, a payment should be issued, so I cannot go further).

I’m a little confused for the other errors you’re reporting, as they should not happen on the same installation:

2nd problem suggests that authorize.net received a wrong rely url, and could not report completed payment to your server, for woocommerce processing.

1st problem, otherwise, suggests that authorize.net reports some data that differs from information sent within the order (customer email)

This is the most upsetting problem, as authorize should simply echo order data, as they received it (this is an exemple of complete response from authorize.net servers)

My best guess is that there are some comunication problems; here’s the text of a newsletter sent to all developers from authorize dev team

As part of our continuous upgrades to enhance system performance and security, on September 21, 2015, we are upgrading api.authorize.net to new security certificates, which are signed using Security Hash Algorithm 2 (SHA-2) and 2048-bit signatures.

These upgrades were already completed on secure.authorize.net in May. If your websites or payment solutions connect to api.authorize.net and any updates are necessary to use the new certificates, please refer to this blog post in our Developer Community, which has all of the certificate information you will need for this update. Our sandbox environment has already been updated so that you can validate that your solution will continue to work using SHA-2 signed certificates, prior to September 21st.

After the update is complete on September 21st, any website or payment solution that connects via api.authorize.net that cannot validate SHA-2 signed certificates will fail to connect to Authorize.Net’s servers.

Authorize.net is making same changes on its network, and maybe this caused some connection problem between your server and theirs; can you please read this post and ensure that your server satisfy all their criteria?

Thank you
Have a nice day!