CardinalCommerce experienced a minor incident on January 22, 2025 affecting Cardinal Consumer Authentication (3DS) and Cardinal API and 1 more component, lasting 1h 11m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jan 22, 2025, 06:25 PM UTC
Cardinal monitoring has detected intermittent latency processing Consumer Authentication with a downstream ACS provider at this time. Impacted ACS URL: maybankcardsmsos.maybank.com.my Reported Start Time: 07:47 GMT 22 January 2025 Impact: Transaction processing would experience increased latency with this ACS resulting in increased directory server timeouts (enrollment Status B and U) and Attempts, Incomplete, or Unavailable Authentications. 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. Cardinal engineers are currently engaging the Card Networks and the ACS provider. Next Update: 60 minutes or as the current status changes. Please do not hesitate to contact the Cardinal support team if you have any questions or concerns.
- resolved Jan 22, 2025, 07:36 PM UTC
The issue has now been mitigated by the third-party downstream provider. We are continuing to monitor closely to ensure the issue has been fully resolved. Reported Start Time: 07:47 GMT 22 January 2025 Reported End Time: 17:48 GMT 22 January 2025 Next Update: As status changes. Please do not hesitate to contact the Cardinal support team if you have any questions or concerns.