Completed -
The scheduled maintenance has been completed.
Apr 19, 09:15 UTC
Update -
Dear partner,
This is a kind reminder that as of tomorrow, April 19st 2018 we are going to disable the support for TLS 1.1 and accept only TLS 1.2 as per the recommendations of PCI DSS 3.2.
All required changes and upgrades must be completed before the 19st of April 2018, Thursday - on this very date, we will implement the required changes on our end in PRODUCTION to apply the new TLS policies by removing support for TLS 1.1.
After the change the following protocols will be supported:
• PRODUCTION Merchant Console - TLS 1.2 only
• PRODUCTION Gate (API processing) - TLS 1.2 only
• PRODUCTION Web Payment Form - TLS 1.2 only
• PRODUCTION Admin Console – TLS 1.2 only
Please kindly note that these changes have already been implemented on our STAGING environment on April 4th 2018 in order to provide you with enough time to test and verify you are able to support TLS 1.2 without any negative impact on your PRODUCTION processing.
Please contact us at
Tech-Support@e-comprocessing.com if any assistance is required. Do not hesitate to ask any additional questions on the subject.
Kind regards,
E-Comprocessing Technical Support Team
Apr 18, 09:19 UTC
In progress -
Dear partner,
As per our earlier notice we have implemented the necessary changes in our STAGING environment today, April 4th 2018 in order to provide you with enough time to test and verify you are able to support TLS 1.2 without any negative impact on your Production processing.
After the change in STAGING the following protocols are supported:
• STAGING Merchant Console - TLS 1.2 only
• STAGING Gate (API processing) - TLS 1.2 only
• STAGING Web Payment Form - TLS 1.2 only
• STAGING Admin Console – TLS 1.2 only
Please make sure you are able to open and communicate with these applications from your end.
Please contact us at
Tech-Support@e-comprocessing.com if any assistance is required. Do not hesitate to ask any additional questions on the subject.
Kind regards,
E-Comprocessing Technical Support Team
Apr 4, 09:30 UTC
Scheduled -
Dear partner,
As part of our ongoing activities and improving the quality and the security of all our services we are going to disable the support for TLS 1.1 and accept only TLS 1.2 as per the recommendations of PCI DSS 3.2.
All required changes and upgrades must be completed before the 19st of April 2018, Thursday - on this very date, we will implement the required changes on our end in PRODUCTION to apply the new TLS policies by removing support for TLS 1.1.
After the change the following protocols will be supported:
• STAGING/PRODUCTION Merchant Console - TLS 1.2 only
• STAGING/PRODUCTION Gate (API processing) - TLS 1.2 only
• STAGING/PRODUCTION Web Payment Form - TLS 1.2 only
• STAGING/PRODUCTION Admin Console – TLS 1.2 only
This change will impact how customer browsers and merchant scripts/integrations will be able to communicate with our gateway services:
• Customers using older browsers that do not support TLS 1.2 will not be able to access our Web Payment Form (WPF).
• Merchants using scripts or libraries to connect to the Processing API and/or the WPF API that do not support TLS 1.2 will be unable to establish a connection with our system.
• Merchants using older browsers that do not support TLS 1.2 will not be able to access the Genesis Merchant Console application.
We are planning to implement these changes in the STAGING environment on April 4, 2018 in order to provide you with enough time to test and verify you are able to support TLS 1.2 without any negative impact on your production processing. Further notice will be sent to confirm once the change is being applied in STAGING.
A list of popular web browsers and support for TLS 1.2 can be viewed at
https://en.wikipedia.org/wiki/Transport_Layer_Security#Web_browsers
Thank you for your attention on this matter.
Please contact us at
Tech-Support@e-comprocessing.com if any assistance is required. Do not hesitate to ask any additional questions on the subject.
Kind regards,
E-Comprocessing Technical Support Team
Mar 30, 14:34 UTC