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
Scheduled Maintenance
Scheduled - Dear Partner,

As part of the continued ongoing development of our gateway services we would like to advise you that our Gateway and API are being updated to meet the requirements of the card schemes about the AVS data usage. Please kindly note that as per their regulations we should add AVS data in the authorization requests to the schemes, and not have AVS as a separate transaction type.

Therefore we implemented the following changes as to how our gateway and API uses the AVS data:

1. The AVS transaction type has been decommissioned from our STAGING environment as of today, July 14th 2017. It will no longer be available as transaction type via the API or via the Gateway UI for reporting. We are planning to push this live in PRODUCTION on July 26. Please make sure you cease the usage of the AVS transaction type from your end in STAGING and make the necessary testing there to migrate to the new way of retrieving AVS data via your authorization requests till the July 26.

2. We added new flag on configuration level named enable_avs for all merchants who want to receive AVS data within their authorization requests. Same as the AVS transaction type it will mark all the needed API params as required to ensure that they will be sent with the authorization requests. It also controls whether the AVS result would be returned with the API responses. In our API documentation you can find more information on how and in what format the AVS data will be returned. We are planning to execute data migration to enable the new configuration flag for the merchants who currently use the AVS transaction type so they can continue retrieving AVS data without any interruption. Please contact our Tech Support team at tech-support@emerchantpay.com if you want this option to be enabled for your account or you have any questions in regards to it.

3. The AVS data can be received also via our notifications for 3DS async payments and the WPF. Please refer to our API documentation for more detailed explanation about the way how you can receive the AVS data via the notifications and its format.

Please note that the above changes will not cause any other interruption to your present processing ability. For those merchants who currently use the AVS transaction type please note that during the migration process our team will provide you with all the necessary support from our end.

Should you require assistance or experience any problems please contact us on our Tech-Support@emerchantpay.com mailbox.

Thank you in advance for your understanding and cooperation.

Kind regards,

eMerchantPay Tech Support Team
Jul 14, 17:31 UTC
System Metrics Month Week Day
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
Aug 19, 2017

No incidents reported today.

Aug 18, 2017

No incidents reported.

Aug 17, 2017

No incidents reported.

Aug 16, 2017

No incidents reported.

Aug 15, 2017

No incidents reported.

Aug 14, 2017

No incidents reported.

Aug 13, 2017

No incidents reported.

Aug 12, 2017

No incidents reported.

Aug 11, 2017

No incidents reported.

Aug 10, 2017

No incidents reported.

Aug 9, 2017

No incidents reported.

Aug 8, 2017

No incidents reported.

Aug 7, 2017

No incidents reported.

Aug 6, 2017

No incidents reported.

Aug 5, 2017

No incidents reported.