As you may be aware, PCI DSS 3.1 requires early TLS to be disabled by June 30, 2016. We're already working on our plans for meeting this requirement, and will make announcements as dates become m...
...equired for API connections utilizing the Advanced Integration Method (AIM), in which cardholder data is transmitted from the client server to the Authorize.Net server. However, will TLS 1.0 c...
I just happened to get off of a live chat with ANET technical support where I had asked if there was any way to test our application for TLS 1.2 compliance. They told me "no" and even said t...
We just had our site (hosted with Godaddy) migrated from a server that only supported TLS1.0 and 1.1 to a server that supports TSL1.0, 1.1, and 1.2. The site was developed years ago using V...
We are really struggling with multiple systems and getting ready for the 2/28/2018 TLS cutoff. We really need some hands-on help. Anyone know of any consultants we can pay to help us get this s...
Hi, We just migrated to a new server and ran ISS crypto to turn disable weak TLS so running 1.2 now. When testing in sandbox we get a new error we've not seen. Does anyone has a s...
Do we have any more information as to when Authorize.Net will remove support for earlier versions of TLS? I'm responsible for maintaining an old website that relies on one of these e...
...ts deadline for remediating existing TLS 1.0 standards has been moved to June 2018. (Source 1, Source 2)
To protect cardholders, merchants, solution providers, and the payment card i...
Another team member updated all Wordpress plugins and now all CC transactions are failing and Wordpress Admin panel shows: Authorize.Net CIM requires TLS v1.2 support to process transactions. P...