Hi, PHP cart, 6.5.5, and just since 8 am yesterday, all orders from authorize.net are in red and unauthorized, even though client has received the authorization email from a.net. Client has contacted a.net and they say it's the cart. Would an update solve the problem, even though it was working perfectly at 7 am yesterday? Currently, even today, all orders are unauthorized so client is unsure whether customers are getting their receipts.

Any suggestions?

Hi LadyM, I would recommend updating the site, and checking that the return urls in authorize.net are setup correctly if the site is on https the return url should also be on https.

Winners never quit, quitters never win
CSS and Responsive Designs
User Manual for Ecommerce Templates

Yes. that is the plan but I want to know what happened yesterday after 8 am? LOL. There must be a reason, surely.

Hi it could be a auth.net issue, more info might be found in the server logs if you check those for around the time the incident occurred it might show what error was occuring.

FYI - auth.net did send out notification to merchants regarding testing for TLS1.2 but that was supposed to happen Jan 30th and Feb 8th but these things do get pushed back sometime.

As you may be aware, new PCI DSS requirements state that all payment systems must disable earlier versions of TLS protocols. These older protocols, TLS 1.0 and TLS 1.1, are highly vulnerable to security breaches and will be disabled by Authorize.Net on February 28, 2018.

To help you identify if you’re using one of the older TLS protocols, Authorize.Net will temporarily disable those connections for a few hours on January 30, 2018 and then again on February 8, 2018.

Please refer to our TLS FAQs for important details.

Based on the API connection you are using, on either one of these two days you will not be able to process transactions for a short period of time. If you don’t know which API you’re using, your solution provider or development partner might be a good resource to help identify it. This disablement will occur on one of the following dates and time:

• Akamai-enabled API connections will occur on January 30, 2018 between 9:00 AM and 1:00 PM Pacific time.
• All other API connections will occur on February 8, 2018 between 11:00 AM and 1:00 PM Pacific time.
Merchants using TLS 1.2 by these dates will not be affected by the temporary disablement. We strongly recommend that connections still using TLS 1.0 or TLS 1.1 be updated as soon as possible to the stronger TLS 1.2 protocol.

Note: If you are not using a current version of a web browser, please take a few moments to upgrade it now. Browsers released prior to 2014 may not support TLS 1.2. You can check your browser's TLS support by visiting https://www.howsmyssl.com/.

If you have any questions about this email or the upcoming TLS disablement, please refer to our TLS FAQs. Thank you for your attention to this matter and for being an Authorize.Net merchant

Winners never quit, quitters never win
CSS and Responsive Designs
User Manual for Ecommerce Templates