CardinalCommerce incident

Centinel Transaction Impact

Minor Resolved View vendor source →

CardinalCommerce experienced a minor incident on August 21, 2024 affecting Cardinal Consumer Authentication (3DS) and Cardinal API and 1 more component, lasting 35m. The incident has been resolved; the full update timeline is below.

Started
Aug 21, 2024, 09:57 AM UTC
Resolved
Aug 21, 2024, 10:33 AM UTC
Duration
35m
Detected by Pingoru
Aug 21, 2024, 09:57 AM UTC

Affected components

Cardinal Consumer Authentication (3DS)Cardinal APICardinal Hybrid API

Update timeline

  1. investigating Aug 21, 2024, 09:57 AM UTC

    Cardinal monitoring has detected intermittent issues processing consumer authentication (3DS) transactions. We are investigating the cause and working urgently to resolve the issue. Impact: Merchants and Partners may be experiencing downgraded performance when attempting to complete 3DS authentication. We regret any inconvenience this may cause for our affected Merchants and Partners. We will provide regular updates until the issue is mitigated. Please do not hesitate to contact the Cardinal support team if you have any questions or concerns: https://support.cardinalcommerce.com [email protected]

  2. resolved Aug 21, 2024, 10:33 AM UTC

    This issue has now been fully resolved. Cardinal is conducting an internal review of the event to mitigate against future occurrences. Reported Start Time: 9:15 UTC Reported End Time: 9:27 UTC Impact: Merchants may have experienced higher than normal latency while processing 3D-Secure transactions resulting in an increase in Enrollment Status B (Bypass) and U (Unavailable). Depending on merchant specific business logic, these transactions may not have been authorized or would have been authorized as standard E-Commerce or Attempts transactions. Please do not hesitate to contact the Cardinal support team if you have any questions or concerns.