Currencycloud Status

The issue impacting the flow of account related updates has now been resolved. Our engineering teams have restored normal data processing and completed additional validation to ensure all affected services are operating as expected. Any delays in reflecting account, permissions, or contact updates have been addressed, and systems are now processing new changes as normal. We will continue to monitor closely to ensure ongoing stability.

The issue impacting transaction processing has now been resolved. All affected transactions have been successfully submitted for processing and are being completed. Our teams have worked through the disruption and normal service has been restored, although a small number of transactions may still experience minor delays while final processing completes. We apologise for any inconvenience caused and thank you for your patience while we resolved this issue.

This incident has been resolved.

**Overview**  On June 10, 2026, we identified an issue affecting pricing responses in our Demo environment, where a portion of requests returned errors. The incident was fully resolved within approximately 1 hour and 31 minutes.  The issue was caused by a configuration inconsistency that impacted connectivity between internal services responsible for pricing. Pricing responses returned to normal and remained stable following resolution.  **Client Impact**  The issue was limited to the Demo environment and did not affect Production services. Clients using Demo for testing experienced intermittent failures when requesting pricing, with some requests returning errors. No data loss, security concerns, or financial impact occurred as a result of this incident.  **Root Cause**  The incident was caused by a configuration mismatch in the Demo environment, which led to a loss of connectivity between dependent services involved in pricing. This resulted in requests being routed to unavailable endpoints, causing elevated error rates. Restoration of the correct configuration and service synchronization resolved the issue and re-established normal connectivity.  Currencycloud Confidential

**Overview** On 8 June 2026, an issue in our production environment temporarily affected access to [Paydirect.io](http://Paydirect.io) for customers using custom domains. The disruption lasted approximately 37 minutes, during which some users were unable to access the DIRECT web interface and saw an “Access Denied” message. The issue was quickly identified and resolved by rolling back a recent change, after which normal service was fully restored and monitored to ensure stability. **Client Impact** During this period, some customers may have experienced: * Difficulty accessing the DIRECT web interface via [Paydirect.io](http://Paydirect.io) * “Access Denied” messages when opening their custom domain URLs The impact was limited to the web interface only. API services continued to operate normally throughout, and no data loss or data integrity issues occurred. No action is required from customers. **Root Cause** This change interacted unexpectedly with production configuration, resulting in valid requests from certain custom domains being incorrectly rejected. CurrencyCloud Confidential

**Overview**  On 5 June 2026, a technical change in our production environment affected how the status of some local payments in TRY, CHF and MXN was displayed.  This lasted approximately 6 hours, during which some payments appeared to be delayed because their status was not updating as expected.  The situation was resolved through a service update, after which normal processing resumed. A follow‑up remediation was completed to ensure all affected payments reflected the correct final status.  **Client Impact**  During this period, some customers may have seen their payments remain in a “submitted” status for longer than expected.  We want to reassure you that payments continued to be processed successfully by our network providers, and funds were transferred as normal.  The impact was limited to how payment statuses were displayed in the platform. All affected payment statuses have since been corrected, and no action is required from customers. No data integrity concerns were identified.  **Root Cause**  This was related to a recent application update affecting how payment status messages are handled.  As a result, some status updates from external network providers were not reflected correctly in the platform.  Currencycloud Confidential

## **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

## Overview On 29 May 2026, an issue within the production environment affected certain FX trading services, including trade and swap execution for a subset of clients. The disruption occurred between 15:05 and 15:37 UTC, with an incident duration of approximately 32 minutes from onset to full service restoration. The issue was addressed through corrective actions, after which services resumed normal operation, supported by ongoing monitoring. ## Client Impact During this period, a limited number of clients may have experienced: * Intermittent issues when submitting trade request * Temporary delays in swap processing, primarily relating to automated activity Functionality remained available throughout. The impact was limited in scope and duration, and other platform services continued to operate as expected. No data integrity issues were identified, and no client action was required. ## Root Cause The issue was associated with a service configuration inconsistency between dependent components involved in trading flows with network partners. Currencycloud Confidential

# 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

# Overview On 19 May 2026, an external industry-wide issue was identified affecting local EUR payments, where a sub-set of payments failed with the failure reason “RJCT reason: Technical problem. Try again.” The external issue was subsequently resolved, internal impact analysis was completed, and the incident was formally marked as resolved. Services returned to normal, and local EUR payments could be processed as expected. # Client Impact During the incident, a subset of payments were failed back to the Client due to a Euro central bank clearing issue. All affected payments failed back to the remitter account. Customers with previously failed payments may need to resubmit their transactions. # Root Cause The issue was caused by an industry-wide disruption affecting external clearing infrastructure used for SEPA Instant / RT1 processing. ‌ ###### Currencycloud Confidential

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.