eMerchantPay Outage History

eMerchantPay is up right now

eMerchantPay had 3 outages in the last 2 years totaling 30h 8m of downtime — averaging 0.1 incidents per month.

There were 3 eMerchantPay outages since September 12, 2024 totaling 30h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.emerchantpay.com

Notice March 24, 2025

emerchantpay - Temporary 3DS network issue 24/03/2025

Detected by Pingoru
Mar 24, 2025, 03:49 PM UTC
Resolved
Mar 25, 2025, 11:32 AM UTC
Duration
19h 43m
Affected: Genesis - web payment form (PRODUCTION)Genesis - API (PRODUCTION)
Timeline · 2 updates
  1. investigating Mar 24, 2025, 03:49 PM UTC

    Dear Valued Partner, We have identified a partial disruption affecting 3DSv2 authentication of transactions processing with Mastercard and VISA. We are in close communication with the 3DS provider to resolve the problem as soon as possible and keep monitoring the transactions. Please accept our apologies for the caused inconvenience. Kind regards, Technical Support Team

  2. resolved Mar 25, 2025, 11:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 5, 2024

emerchantpay - ECP acquirer - Temporary issues in transaction processing with Mastercard only 05/11/2024

Detected by Pingoru
Nov 05, 2024, 03:05 PM UTC
Resolved
Nov 05, 2024, 04:35 PM UTC
Duration
1h 30m
Affected: Genesis - web payment form (PRODUCTION)Genesis - API (PRODUCTION)
Timeline · 2 updates
  1. identified Nov 05, 2024, 03:05 PM UTC

    Dear customer, Note we have identified an issue related to transaction declines with an unknown reason related to Mastercard card brand only with the ECP acquirer. The issue seems to affect Mastercard transactions only partially, as most are passing successfully. Please rest assured that we have escalated to the ECP acquirer already and are working together with the highest priority on the matter to resolve it as soon as possible. We appreciate your understanding, and please accept our apologies for any inconvenience caused. Should you have any questions or require further assistance, please do not hesitate to contact our Tech Support team at [email protected]

  2. resolved Nov 05, 2024, 04:35 PM UTC

    Dear Customer, A hotfix resolving the Mastercard issue has been deployed successfully by the ECP acquirer, and thus the issue has been fully rectified. If you experience any problems during payment processing, please don’t hesitate to contact our Tech Support team. We’ll continue to monitor our systems closely and keep you informed as needed.

Read the full incident report →

Major September 12, 2024

emerchantpay - Genesis - External Provider Partial Outage - 12/09/2024

Detected by Pingoru
Sep 12, 2024, 06:04 AM UTC
Resolved
Sep 12, 2024, 02:59 PM UTC
Duration
8h 55m
Affected: Genesis - web payment form (PRODUCTION)Genesis - API (PRODUCTION)
Timeline · 3 updates
  1. investigating Sep 12, 2024, 06:04 AM UTC

    Dear Valued Partner, Please be informed that we are currently experiencing issues with one of our external providers ECP and the transaction processing through this acquirer was temporary disabled. There is no impact on transactions submitted through other acquirers. We will update the status page immediately once the processing thru the ECP acquirer is restored and all is back to normal. For more information, please contact us at [email protected] Thank you for your patience on the matter. Kind Regards, Tech-Support Team

  2. monitoring Sep 12, 2024, 12:29 PM UTC

    Dear Valued Partner, Please be informed that the recent disruption in payment processing services with the ECP acquirer has been resolved, and normal transaction processing has resumed. We are continuing to actively monitor the situation. We will update the status page accordingly once we are assured that the issue is resolved permanently at the upstream provider. For more information, please contact us at [email protected]. Thank you for your patience on the matter. Kind Regards, Tech Support Team

  3. resolved Sep 12, 2024, 02:59 PM UTC

    This incident has been resolved.

Read the full incident report →