You may have recently received an E-mail from Authorize.NET notifying you that early TLS will be disabled on September 18, 2017, and noting you should confirm your applications can use TLS 1.2 for API connections.
If you are using SOLO Server Shared or Dedicated URL, no action is needed – our servers are compatible with this change.
If you are providing your own hosting for SOLO Server, action may be required depending on the version of SOLO Server you are currently running.
Please contact us with any questions.
Maximizing email deliverability with SOLO Server Automation
SOLO Server 220.127.116.11 Released with New Support for Consumption-Based Licensing and More!
SOLO Server 18.104.22.168 – Improved Add License and Monthly Statements
SOLO Server 22.214.171.124 Released with New Integration User Accounts
What is Cloud-Controlled Network Floating Licensing?
Introducing API Transaction Fee Policy