eMerchantPay
All Systems Operational

About This Site

Status page for eMerchantPay, global leader for international online payment processing gateway services

Agent Portal   ? Operational
emerchantpay.com   ? Operational
FTP server   ? Operational
Analysis backend   ? Operational
Genesis - API (PRODUCTION)   ? Operational
Genesis - web payment form (PRODUCTION)   ? Operational
Genesis - merchant console (PRODUCTION)   ? Operational
Genesis - admin console (PRODUCTION)   ? Operational
Genesis - API (STAGING)   ? Operational
Genesis - web payment form (STAGING)   ? Operational
Genesis - merchant console (STAGING)   ? Operational
Genesis - admin console (STAGING)   ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Genesis API (PRODUCTION) - response time
Fetching
Genesis - web payment form (PRODUCTION) - response time
Fetching
Genesis - merchant console (PRODUCTION) - response time
Fetching
Genesis - admin console (PRODUCTION) - response time
Fetching
Genesis - API (STAGING) - response time
Fetching
Genesis - web payment form (STAGING) - response time
Fetching
Genesis - merchant console (STAGING) - response time
Fetching
Genesis - admin console (STAGING) - response time
Fetching
Past Incidents
Apr 21, 2018

No incidents reported today.

Apr 20, 2018

No incidents reported.

Apr 19, 2018
Completed - The scheduled maintenance has been completed.
Apr 19, 09:16 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@emerchantpay.com if any assistance is required. Do not hesitate to ask any additional questions on the subject.

Kind regards,

eMerchantPay Technical Support Team
Apr 18, 09:15 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@emerchantpay.com if any assistance is required. Do not hesitate to ask any additional questions on the subject.

Kind regards,

eMerchantPay Technical Support Team
Apr 4, 09:24 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@emerchantpay.com if any assistance is required. Do not hesitate to ask any additional questions on the subject.

Kind regards,

eMerchantPay Technical Support Team
Mar 30, 14:38 UTC
Apr 17, 2018

No incidents reported.

Apr 16, 2018

No incidents reported.

Apr 15, 2018

No incidents reported.

Apr 14, 2018

No incidents reported.

Apr 13, 2018
Completed - The scheduled maintenance has been completed.
Apr 13, 13:15 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 13, 12:16 UTC
Scheduled - For details on this release, please contact our technical support team at Tech-Support@emerchantpay.com

No interruptions in processing are anticipated but if you notice any issues please let us know at our support email listed above. Apologize for any inconvenience caused.
Apr 13, 12:13 UTC
Apr 12, 2018

No incidents reported.

Apr 11, 2018

No incidents reported.

Apr 10, 2018

No incidents reported.

Apr 9, 2018

No incidents reported.

Apr 8, 2018

No incidents reported.

Apr 7, 2018

No incidents reported.