Clients experiencing Multiple Invalid SCA Error

Update timeline

1. investigating May 21, 2026, 10:19 PM UTC

   We are currently investigating an issue causing some clients to receive Invalid SCA errors. Some clients may also experience issues with 2FA/Authy authentication and may need to use SMS login as a fallback, where available. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. Thank you for your patience, and we apologize for any inconvenience caused.

2. monitoring May 22, 2026, 01:18 AM UTC

   Some clients experienced errors when creating payments or logging in due to issues with authentication checks. The issue was linked to a recent service change that affected how authentication requests were processed, but this has now been rolled back, and systems are stable with no repeated errors seen. We are currently confirming recovery with affected clients and continuing to monitor for any further issues.

3. resolved May 22, 2026, 05:35 AM UTC

   The issue affecting errors when creating payments or logging in have been resolved. Service restored to expected behaviour. We apologize for any inconvenience this may have caused.

4. postmortem May 28, 2026, 08:57 AM UTC

   # Overview On 21 May 2026, we identified an issue in the production environment that impacted payment validation and authentication flows. A small number of clients experienced errors when attempting to complete payment-related actions and multi-factor authentication \(2FA\). Corrective actions were implemented to address the issue, and normal system behaviour was re-established within 3 and a half hours, following stability checks and confirmation that systems were operating as expected. # Client Impact During the incident, clients may have experienced: · Errors when attempting to create or validate payments · Issues completing authentication using 2FA methods · Intermittent disruption within payment workflows The impact was limited to a subset of clients, while other payment and authentication activities continued to process successfully. No data integrity issues were identified. Clients were not required to take any action. # Root Cause The issue was caused by a recent change within a supporting service involved in payment validation and authentication processes. This resulted in unexpected behaviour when handling certain requests, which led to errors affecting dependent payment and authentication flows. ###### Currencycloud Confidential