AllProWebTools was upgraded to use TLS 1.2 over a year ago and is already compatible with the planned deprecation. AllProWebTools clients do not need to be concerned by these notices as AllProWebTools is already prepared for this.
Here is the notice sent by Cayan:
Another message from Cayan:The end of TLS 1.0 – Don’t get caught off guard
To enhance data security across the industry, the PCI SSC has mandated that the TLS 1.0 encryption protocol be disabled. That’s why all systems connecting to Cayan must support TLS 1.1 or 1.2 by June 30, 2018.
If these updates aren’t made by July 1, 2018, your merchants will no longer be able to process transactions – with Cayan or any other payment solution provider.
This is expected to be as disruptive and costly as the shift to EMV. Many merchants will need to make major updates to their POS software, hardware and operating systems, so it’s crucial to act quickly.
We’ll be communicating with our merchants on Thursday, June 29, and instructing them to reach out to their POS providers for insight on how to prepare.
Watch this webinar to find out how we can help you:
Understand your exposure
Prepare for your merchants’ questions
Update your systems
Better serve our mutual customers
If you have any questions, don’t hesitate to reach out to your Partner Development or VAR Manager.
The Cayan Partner Support Team
Here is a message from Authorize.net:The Payment Card Industry (PCI) has declared that the widely-used TLS 1.0 encryption protocol is no longer secure. That’s why all systems connecting to Cayan must support TLS 1.1 or 1.2 by June 30, 2018.
If these updates aren’t made by July 1, 2018, you will no longer be able to process transactions – with Cayan or any other payment solution provider.
This might seem like a long way off, but it’s crucial to act quickly. You may need to make major updates to your POS software, hardware or operating systems.
Don’t wait. Start preparing today. Contact your POS provider to discuss next steps now.
The Cayan Customer Support Team
Important TLS Disablement Notice
Your Authorize.Net Partner ID: 19429
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 partner.