Currencycloud Status Page

Jun 15, 2026

We are currently investigating an issue impacting a subset of RON local payments, where a file has not been successfully processed by an external network partner. This is resulting in delays to affected payments, and our teams are actively working with the partner to validate and progress resolution. Further updates will follow.

Jun 10, 2026 · resolved Jun 10

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

Jun 8, 2026 · resolved Jun 8

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

Jun 5, 2026 · resolved Jun 5

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

Jun 3, 2026 · resolved Jun 3

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