phi148 Posted April 27, 2017 Share Posted April 27, 2017 Hi I received an email today from Authorize.net that stated the following: Dear Authorize.Net Partner: As you may be aware, new PCI DSS requirements state that all payment systems must disable early TLS by 2018. In preparation for this requirement, Authorize.Net plans to disable TLS 1.0 and TLS 1.1 on the following dates: Sandbox: April 30, 2017 Production: September 18, 2017 We are disabling the sandbox in advance of production to allow you and your merchants time to test your solutions and ensure you are no longer using TLS 1.0 or 1.1. Please check the code for your solutions and systems to confirm that they can default to TLS 1.2 for your API connections. You can review our API Best Practices for details about TLS 1.2 platform support and other integration suggestions. Thank you for your attention to this matter and for being an Authorize.Net developer. Sincerely, Authorize.Net Does anyone know if this AIM package is TLS 1.2 compliant ?? Thanks! Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.