Currencycloud incident

Login Issues with MFA Authentication

Minor Resolved View vendor source →

Currencycloud experienced a minor incident on June 3, 2026 affecting Paydirect.io / Direct, lasting 3h 58m. The incident has been resolved; the full update timeline is below.

Started
Jun 03, 2026, 05:40 PM UTC
Resolved
Jun 03, 2026, 09:39 PM UTC
Duration
3h 58m
Detected by Pingoru
Jun 03, 2026, 05:40 PM UTC

Affected components

Paydirect.io / Direct

Update timeline

  1. investigating Jun 03, 2026, 05:40 PM UTC

    We are currently investigating an issue that is causing some customers to experience errors during multi-factor authentication (MFA/2FA) when attempting to log in to our platform. Our technical teams are actively working to identify the root cause and implement a resolution as quickly as possible to restore normal service. We sincerely apologise for any disruption this may cause and appreciate your patience while we work to resolve the issue.

  2. resolved Jun 03, 2026, 09:39 PM UTC

    The issue affecting a small number of customers experiencing errors during multi-factor authentication (MFA/2FA) when logging in has now been resolved. Our teams implemented changes and have confirmed that normal service has been restored. We sincerely apologise for any inconvenience this incident may have caused and appreciate your patience.

  3. postmortem Jun 03, 2026, 10:01 PM UTC

    ## **Overview** On 3 June 2026, an issue within the production environment caused intermittent errors during multi-factor authentication \(MFA/2FA\) when logging in to the platform. The issue began at approximately 16:50 UTC and was resolved at approximately 19:40 UTC, with a total duration of around 3 hours. A corrective change was applied, after which normal service resumed. The platform has remained stable under continued monitoring. ## **Client Impact** During this period, a small proportion of login attempts may have experienced: * Errors during MFA \(2FA\) authentication * Temporary difficulty accessing the platform The issue was intermittent and limited in scope. Other platform functionality remained available, and no data integrity or security concerns were identified. No client action was required. ## **Root Cause** The issue was related to a platform configuration inconsistency. Under certain conditions, this resulted in some login attempts not being processed as expected. Currencycloud Confidential