Recently, you may have seen a notice from Authorize.net announcing that they will be disabling early TLS* (version 1.0 or 1.1). New PCI DSS requirements state that all payments systems must disable early TLS by 2018. Authorize.net has already disabled early TLS in their test environment and will do so in the production environment on September 18, 2017.
What does this mean to you? eAuthorize 5.3 was designed to handle the most recent Authorize.net updates. We have already tested transactions using eAuthorize 5.3 in the Authorize.net test environment and transactions are processing successfully. If you are currently using eAuthorize 5.3, or if you are planning to make a purchase, you can be assured that it will process transactions as expected.
That being said, TLS 1.0 and 1.1 being disabled can be an issue if your using an older computer that has older libraries installed.
To test your own computers:
Install the plug-in on the machine you wish to test. Then open our example test database that was included with the download (eAuthorize_5.fmp12). On the test database, go to the Authorize.net tab and run a test transaction. Under the Settings, just make sure you have the Host set to:
If you get back messages that the transactions are successful, you should have nothing to worry about with the upcoming change.
*Transport Layer Security (TLS) is a technology used to encrypt sensitive information sent via the Internet. TLS is he replacement for Secure Sockets Layer (SSL).