eMerchantPay incident

emerchantpay - Genesis Gateway - Temporary service disruption with the 3DS MPI provider

Notice Resolved View vendor source →

eMerchantPay experienced a notice incident on November 28, 2020 affecting Genesis - web payment form (PRODUCTION) and Genesis - API (PRODUCTION), lasting 3h 38m. The incident has been resolved; the full update timeline is below.

Started
Nov 28, 2020, 04:17 PM UTC
Resolved
Nov 28, 2020, 07:55 PM UTC
Duration
3h 38m
Detected by Pingoru
Nov 28, 2020, 04:17 PM UTC

Affected components

Genesis - web payment form (PRODUCTION)Genesis - API (PRODUCTION)

Update timeline

  1. investigating Nov 28, 2020, 04:17 PM UTC

    Dear Valued Partner, We have identified partial service disruption, affecting some of the 3DS transactions. We are working towards resolution with our 3DS MPI service provider. The issue is causing some of 3DS transactions to fail due to communication errors with the Directory Server. We have already addressed this incident to the responsible departments and are working towards the resolution of the issue. Please accept our apologies for the caused inconvenience.

  2. identified Nov 28, 2020, 05:36 PM UTC

    Dear Valued Partner, We have narrowed down the issue - it is affecting only 3DSv1 transactions with VISA card brand only. It’s due to Directory Server issues at Visa, not related to our MPI provider. We are working closely with the necessary third parties in order to get this issue resolved as soon as we can and to get additional information about it. Please note, Visa and MasterCard 3DSv2 processing is still fully operational and there is no impact. Please accept our sincere apologies for any caused inconveniences. Kind Regards

  3. monitoring Nov 28, 2020, 06:44 PM UTC

    Dear Valued Partner, Please note, the issue has been resolved and all Visa 3DSv1 processing is fully operational. We will continue monitoring and inform you timely if any further issues arise. Please accept our sincere apologies for any caused inconveniences. Kind Regards

  4. resolved Nov 28, 2020, 07:55 PM UTC

    This incident has been resolved.