Spike in Unavailable transactions for 3D Secure 1.0.2 on Secure4
Between 1815 GMT and 1915 GMT on 03 September, Transaction Manager service experienced a problem due to which 3D Secure version 1.0.2 transactions requiring cardholders to authenticate themselves via a challenge step were failing with 3D Secure status Unavailable. The problem was found to be caused due to Transaction Manager ACS not being able to connect with callouts that make API calls to Issuer backends in order to perform certain operations for cardholder authentication flow.
Find Your Subscription
We’ll find your subscription and send you a link to login to manage your preferences.
Check Your Inbox
We’ve found your existing subscription and have emailed you a secure link to manage your preferences.
Subscribe to Status Updates
We’ll use your email to save your preferences so you can update them later.
-
Email{{ value }}
-
Text Message{{ value }}
-
Slack
-
Microsoft Teams{{ value }}
-
Google Chat
Subscribe to other services using the bell icon on the subscribe button on the status page.
Unsubscribe Completely?
You’ll no long receive any status updates from Broadcom Service Status, are you sure?
{{ error }}
You’re Unsubscribed!
We’ll no longer send you any status updates about Broadcom Service Status.