NopCommerce's Payment.Authorize.net free plugin is TLS 1.2 supported?

Hi,

We use NopCommerce's Payment.Authorize.Net free plugin with NOP 3.60 framework.
(https://www.nopcommerce.com/p/2320/authorizenet-payment-module.aspx)

Authorize.Net is suggesting the users to comply with PCI SSC standards.
i.e., to migrate to TLS1.2 from ssl & early tls
https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls

So, is the latest version of 'Payment.Authorize.Net' plugin supports TLS1.2?
Please advise.

Esskay wrote:

I think TLS1.2 issue is solved in version 3.90

@Sohel,

So, do you say the free plugin (Payment.Authorize.Net) supports TLS1.2?

Esskay wrote:

I told default nop 3.90 solved it

===> you will see the following code for resolving it
\Nop.Web\Global.asax.cs

  protected void Application_Start()
        {
         
     
 //most of API providers require TLS 1.2 nowadays
            ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

......
}

@Esskay

if you are about latest version of 3.6 then i think is should not have the fix of TLS1.2

so you need to apply @Sohel solutions to either global.asax or on the plugin it self before calling the authorize.net API.

From 3.9 its fixed but for older version we need to add it manually.

Thank you @Sohel and @Vipul. Appreciate it.

I applied the tls12 line in the plugin itself before calling the authorize.net API.

Authorize.net plugin in version 3.8 and 3.9 also don't display any error messages to costumers when the transaction get declined.

deselt wrote:

Have you tested and verify it ??

I think it should working good.

Yes I did many times. It was working fine in version 3.7. We have Fraud Detection Suite turn on in Authorize.net for the billing address verification. If the billing address don't match transaction get Declined, but don't show any message to customer so keep trying and than they have pending transaction on account.

I am using version 3.7. Where is my Global.asax.cs file? Please help I'm a newbie