authorize.net TLS 1.2 coming what do we need to do?

Hi,
We are running Nop 3.6. We will not be able to update it to a more recent before this deadline.
So does the Authorize.net plugin for 3.6 work already with TLS 1.2?
Is there a 3rd party plugin that works with 3.6 that supports these changes?

Chris

Here is the info we got form them --
---------------------------------------

TLS Disablement Reminder

Your Payment Gateway ID: 656425
Dear Authorize.Net Merchant:

As you may be aware, new PCI DSS requirements state that all payment systems must disable early TLS by June 30, 2018.


    TLS FAQs
    Merchant Interface


Transport Layer Security (TLS), is a technology used to encrypt sensitive information sent via the Internet. TLS is the replacement for Secure Sockets Layer (SSL).

In preparation for this requirement, Authorize.Net plans to disable TLS 1.0 and TLS 1.1 on the following dates:

Sandbox: COMPLETE
Production: February 28, 2018

We have disabled the sandbox in advance of production to allow you and your developer time to test your website or payment solution and ensure you are no longer using TLS 1.0 or 1.1 prior to February 28th.

Please contact your web developer or payment solution provider, as well as your web hosting company, to confirm that they can support TLS 1.2 for your API connections.

---------------------------------------------------

Hi Karma,
Did you end up figuring this one out? I believe this is the issue to the order processing errors we are getting.

Thanks for the help!

This is old but you just need to add this line at the top of the ProcessPaymentResult method of the Authorize.Net plugin:

ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;