Sage Exchange Desktop 1.0 & TLS Compliance

Paya has set an obsolescence date for SED 1.0 of June 25^th, 2018.  Sage Exchange Desktop 2.0 has a legacy service built into the program to support SED 1.0 integrated products.   Customers using these versions of Sage 100 must complete a transition to Sage Exchange Desktop 2.0 (SED 2.0).

Completely uninstalling SED 1.0 and repairing the Module SDK must be completed before installing SED 2.0.  

Please refer to this article for information about this process.

Please refer to this article for the process of installing Sage Exchange Desktop 2.0.

Your infrastructure may need additional actions to become compliant with TLS 1.1and 1.2 communication protocols.

TLS 1.1 and 1.2 minimum requirements  for compliance

Our customers and vendors need to continue working on being TLS 1.2 compliant. If you were unable to process payments using a software solution, please contact your vendor to discuss how your software is currently leveraging TLS. Your vendor may suggest possible upgrades to those solutions to ensure that you can use the TLS 1.2 protocol. Paya has updated our Donate Now, Shopping Cart and Mobile products to be TLS compliant. No further action is needed for these products.

 You will need to enable TLS 1.1 and 1.2 security protocols on your servers and workstations. The minimum operating systems that support TLS 1.1 and 1.2 options are Windows Server 2008 R2, and Windows 7. Please ensure that all updates and patches have been applied.  If you are using Linux, please check the Open SSL changelog for the version of your Linux OS that will support TLS 1.2.

For more information about how to enable TLS 1.1 and 1.2 for Windows operating systems, please refer to this link.  Paya has built a program that simplifies the necessary Registry Edits mentioned in the Microsoft article; please click here to download this program.

Disclaimer:  Usage of these programs should be limited to systems administrators because they could impact system critical services and applications. Specific services and applications may not be capable of communication over certain TLS protocols; you may need to contact your vendor for TLS 1.1/1.2 compatible version of their solutions.

For further detailed information about the transition for TLS 1.2, please review this article from the PCI SSC.

For guidelines on selection, configuration and use of TLS implementations, please review this help document from National Institute of Standards and Technology. 

If you have questions or require additional information, please contact us, and we will be in touch with you shortly.