Authorize.Net integration

Hi. Authorize.net is upgrading their system to TLW 1.2 and previous versions (TLS 1.0 and TLS 1.1) will be disabled. Is there anything that needs to be done with the Infusionsoft integration?

1 Like

Do you have a reference? There’s no mention by search engine or on authorize.net of TLW anything?

@Kim_Wanamaker1, I confirmed with our Product Management team that we are good to go with TLS 1.2.

@John_Borelli, here is a link to the change notice: https://support.authorize.net/authkb/index?page=content&id=A1623&actp=search&viewlocale=en_US&searchid=1516912371261#Support

So TLW is a typo then right? Thought it was something I hadn’t heard of yet lol

Yeah, I’m pretty sure that was a typo :yum:

1 Like

This is from an email we received:

As you may be aware, new PCI DSS requirementsstate 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.

Right, we’ve seen the email copied alot today lol The TLW reference is what threw me :stuck_out_tongue_winking_eye:

Yeah. Sorry. Thanks for the help! Love that Infusionsoft is on top of it!

2 Likes