Currencycloud Outage History

Started Jun 08, 2026, 10:28 AM UTC· resolved Jun 08, 2026, 11:05 AM UTC

1. investigating Jun 08, 2026, 10:28 AM UTC

   We are investigating reports of customers getting Access Denied when accessing their paydirect.io urls

2. resolved Jun 08, 2026, 11:05 AM UTC

   This incident has been resolved.

3. postmortem Jun 09, 2026, 07:25 PM UTC

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

Read the full incident report →

Started Jun 05, 2026, 08:48 AM UTC· resolved Jun 05, 2026, 03:00 PM UTC

1. identified Jun 05, 2026, 08:48 AM UTC

   We are currently experiencing delays in the processing of some local payments in TRY, CHF and MXN. Payments may take longer than usual to complete while we investigate the issue with our external banking partners. We are working to resolve this as quickly as possible and will provide further updates as soon as more information becomes available.

2. identified Jun 05, 2026, 10:37 AM UTC

   We are continuing to work on a fix for this issue.

3. resolved Jun 05, 2026, 03:00 PM UTC

   The issue has now been resolved, and the service is operating as expected. A small subset of payments may continue to display an incorrect status; this is currently under investigation, and further updates will be provided once resolution is confirmed.

4. postmortem Jun 09, 2026, 07:24 PM UTC

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

Read the full incident report →

Started Jun 03, 2026, 05:40 PM UTC· resolved Jun 03, 2026, 09:39 PM UTC

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

Read the full incident report →

Started May 28, 2026, 03:05 PM UTC· resolved May 28, 2026, 03:37 PM UTC

1. resolved May 28, 2026, 04:02 PM UTC

   We experienced a temporary disruption impacting FX trading services between 15:05 and 15:37 UTC. During this time, some client trade requests were unsuccessful, while quote requests were not impacted. The issue has now been resolved, and services have been fully restored. We continue to monitor systems to ensure ongoing stability.

2. postmortem Jun 02, 2026, 09:45 PM UTC

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

Read the full incident report →

Started May 21, 2026, 10:19 PM UTC· resolved May 22, 2026, 05:35 AM UTC

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

Read the full incident report →

Started May 19, 2026, 05:22 PM UTC· resolved May 20, 2026, 09:38 AM UTC

1. investigating May 19, 2026, 05:22 PM UTC

   We are currently investigating an issue affecting SEPA Instant payments, which may cause some local EUR payments to fail. Our teams are actively investigating the issue and working to restore normal processing as quickly as possible. Thank you for your patience, and we apologize for any inconvenience caused.

2. identified May 19, 2026, 06:11 PM UTC

   The issue affecting SEPA Instant payments has been identified. Some local EUR payments may continue to experience delays, rejections, or failures while the external provider works to restore service. We are continuing to monitor the situation and will provide further updates as more information becomes available. Thank you for your patience, and we apologize for any inconvenience caused.

3. resolved May 20, 2026, 09:38 AM UTC

   The issue affecting local EUR payments has now been resolved, and services are operating normally. The disruption was caused by an industry wide EBA incident impacting SEPA Instant (RT1) processing, which has now been fully restored. Payments can now be processed as expected. Customers with previously failed payments may need to resubmit their transactions. We will continue to monitor the service to ensure stability. Thank you for your patience, and we apologise for any inconvenience caused.

4. postmortem May 28, 2026, 09:02 AM UTC

   # 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

Read the full incident report →

Started May 18, 2026, 05:05 PM UTC· resolved May 19, 2026, 08:51 AM UTC

1. investigating May 18, 2026, 05:05 PM UTC

   We are currently investigating an issue that may cause delays or missing details during the creation of some ARKEA and CFSB accounts in the DEMO environment. Our teams are actively working to restore normal processing as quickly as possible. Thank you for your patience, and we apologize for any inconvenience caused.

2. monitoring May 18, 2026, 08:14 PM UTC

   The issue that may have caused delays or missing details during the creation of some EUR and USD accounts in the DEMO environment has been identified and mitigated. Our teams are continuing to monitor the service to confirm normal processing has resumed. Thank you for your patience, and we apologize for any inconvenience caused.

3. resolved May 19, 2026, 08:51 AM UTC

   This incident has been resolved.

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

   # Overview On 18 May 2026, we identified an issue in the DEMO environment that caused delays and incomplete details during the creation of some EUR and USD test accounts. Our teams investigated and implemented a fix to address the underlying issue, restoring normal account creation performance within 2 hours. Full service was stabilised once processing backlogs were cleared and system behaviour returned to expected levels. # Client Impact During the incident, clients may have experienced delays in test account creation, with some accounts taking longer than expected to be fully provisioned. In certain cases, account details may not have been immediately available. The issue was limited to the DEMO environment. No transactions, funds, or data were impacted, and all affected accounts were successfully processed once the issue was resolved. No action was required from clients. # Root Cause The issue was caused by an internal processing error that resulted in duplicate account identifiers being generated. This led to repeated processing attempts and delays within the test account creation workflow until the issue was identified and resolved.

Read the full incident report →

Started May 10, 2026, 03:49 AM UTC· resolved May 10, 2026, 04:18 AM UTC

1. monitoring May 10, 2026, 03:49 AM UTC

   The planned platform maintenance has been extended.

2. resolved May 10, 2026, 04:18 AM UTC

   This incident has been resolved.

3. postmortem May 13, 2026, 08:14 AM UTC

   # **Overview** On 10 May 2026, we carried out planned maintenance on our as part of our ongoing efforts to maintain and improve reliability. This activity involved a controlled failover and failback process. During this time, access to the platform was intermittently unavailable. While the maintenance was completed successfully, it took longer than originally expected \(_00:00 – 02:00_\). Full service was restored at 04:18 UTC, once stability checks were completed. # **Client Impact** During the maintenance window, clients experienced temporary interruptions when accessing the platform, including delays or inability to create payments, conversions, and transfers, as well as disruptions to API and integration services. Despite these interruptions, all funds and data remained completely safe, no transactions were lost or altered, and normal service resumed once maintenance was completed without any action required from clients. # **Root Cause** This was a planned maintenance activity, not a system issue. However, the overall duration was longer than expected due to additional time needed to complete the failover process and perform thorough system checks before fully restoring access. These additional checks were necessary to ensure the platform was stable and operating normally before bringing all services back online. ‌ ###### Currencycloud Confidential

Read the full incident report →

Started May 08, 2026, 10:57 AM UTC· resolved May 08, 2026, 03:40 PM UTC

1. investigating May 08, 2026, 10:57 AM UTC

   We are currently experiencing an issue affecting the status updates for local EUR payments. While the displayed status may not reflect the latest state, payments themselves are processing as expected with no impact to settlement. Our teams are actively working to restore correct status reporting. We will provide a further update once the issue is resolved.

2. monitoring May 08, 2026, 11:35 AM UTC

   The issue affecting status updates for local EUR payments has been corrected. Payment statuses are updating correctly; however, due to earlier processing volumes, it may take a few hours for all outstanding payments to fully reflect their final status. Payments have continued to process and settle as expected throughout. We will continue to monitor closely until all status updates are fully reconciled.

3. resolved May 08, 2026, 03:40 PM UTC

   Payment statuses have been updated, now fully reflect their final status. During this period payments have continued to process and settle as expected throughout. Thank you for your patients.

4. postmortem May 13, 2026, 08:04 AM UTC

   # **Overview** On May 8th 2026, an issue was identified that affected the way status updates were displayed for local EUR payments. While payments continued to process normally, some statuses did not update in real time due to increased processing volumes. The issue was investigated, corrected, and status updates returned to normal. # **Client Impact** During the incident, a subset of local EUR payments temporarily displayed an incorrect status, such as remaining marked as “Submitted.” There was no impact to payment execution or settlement, and all payments were processed as expected. # **Root Cause** The issue was caused by an internal processing backlog triggered by an unusually high volume of payments released via our network partners within a short time frame. This delayed the handling of completion updates, resulting in slower status updates until processing capacity recovered and the backlog cleared. ###### Currencycloud Confidential

Read the full incident report →

Started May 08, 2026, 09:41 AM UTC· resolved May 08, 2026, 02:10 PM UTC

1. investigating May 08, 2026, 09:41 AM UTC

   We are currently experiencing an issue affecting our phone support service, which may make it difficult for customers to reach us by telephone. Our teams are actively working to restore full phone support as quickly as possible. In the meantime, customers are encouraged to contact us via alternative channels, including email and in‑app support, where services remain available. Further updates will be provided as more information becomes available.

2. resolved May 08, 2026, 02:10 PM UTC

   The issue affecting our phone support service has now been resolved. All support channels, including phone, email, and in‑app support, are fully operational. We apologise for any inconvenience caused and thank you for your patience.

3. postmortem May 13, 2026, 08:03 AM UTC

   # **Overview** On May 8th 2026, an issue was identified that temporarily affected phone support availability. During the incident, customers may have experienced difficulty reaching support by telephone while the issue was investigated and resolved. Alternative support channels remained available throughout. # **Client Impact** Some customers were unable to contact phone support for a period of time. Other contact options, including email and in‑app support, continued to operate as normal and were available for assistance. # **Root Cause** The issue was caused by an internal connectivity and configuration problem affecting systems used to handle phone support calls, which led to service disruption until corrective actions were completed. ###### Currencycloud Confidential

Read the full incident report →

Started May 07, 2026, 11:16 AM UTC· resolved May 07, 2026, 04:13 PM UTC

1. investigating May 07, 2026, 11:16 AM UTC

   We are currently aware that some customers may experience intermittent issues when using Authy for two‑factor authentication (2FA), which may affect the ability to log in. While we investigate this, customers experiencing issues are advised to temporarily use SMS‑based verification where available as an alternative method. Our teams are monitoring the situation closely and we will provide further updates as more information becomes available. We apologise for any inconvenience caused and thank you for your patience.

2. resolved May 07, 2026, 04:13 PM UTC

   The issue affecting Authy two‑factor authentication (2FA) has been resolved and customers should now be able to log in as normal. We will continue to monitor authentication services to ensure ongoing stability. Thank you for your patience while this was investigated.

3. postmortem May 13, 2026, 08:00 AM UTC

   # **Overview** On May 7th 2026, an issue was identified that caused intermittent errors during two‑factor authentication for a subset of users. The problem was detected through monitoring and user reports, and teams investigated to isolate the cause. Once identified, changes were made to stabilize authentication behavior and restore normal access. # **Client Impact** During the incident, some users experienced intermittent difficulty completing multi‑factor authentication when logging in. The issue was temporary, did not affect all users, and normal login functionality was restored once the corrective actions were completed. # **Root Cause** The incident was caused by an internal application change related to session handling that unintentionally affected the authentication flow. This resulted in elevated error rates during multi‑factor authentication until the change was rolled back and stability was restored. ###### Currencycloud Confidential

Read the full incident report →

Started May 04, 2026, 04:05 PM UTC· resolved May 05, 2026, 11:25 AM UTC

1. investigating May 04, 2026, 04:05 PM UTC

   We are currently investigating an issue affecting the status updates for some Erste payments. Payments are processing as expected, however status confirmations may temporarily appear delayed due to pending acknowledgements from our Erste network partner. This may cause some payments to display as incomplete even though they are being processed normally. We are working closely with the network partner to receive the outstanding acknowledgements and update payment statuses accordingly. No action is required from clients at this time.Thank you for your patience, and we apologize for any inconvenience caused.

2. investigating May 05, 2026, 11:16 AM UTC

   This incident has been resolved.

3. resolved May 05, 2026, 11:25 AM UTC

   This incident has been resolved.

4. postmortem May 07, 2026, 08:31 AM UTC

   # Overview On 4 May 2026, we identified an issue affecting a subset of RON, CZK & HUF payments processed via one of our network partners. While the payments themselves were successfully sent and debited by the network provider as expected, their final status updates were not reflected in our platform. This caused a number of payments to remain visible in submitted status even though processing had completed successfully at the bank level. All affected payments were completed via manual intervention and verified as debited. # Client Impact Affected clients experienced delayed or incorrect payment status updates within the platform. Although the status visibility was impacted, no payments failed and no funds were lost; all affected transactions were confirmed as successfully debited. Clients were not required to take any action during the incident. Once payment completion was directly confirmed with our network provider, all impacted payments were manually updated to their correct completed status, fully resolving the issue. # Root Cause The issue was caused by a delay in receiving final payment confirmation messages from our network provider for payments submitted during the high-volume bank holiday period. Although the payments were successfully received and processed and funds were debited as expected, an integration timing issue linked to the high-volume public holiday on 1 May meant that our network provider did not send the expected completion confirmation messages for that batch of payments. In the absence of these confirmations, the system was unable to automatically update the payment statuses, causing them to remain visible in submitted status despite having been completed. Once full processing was confirmed, the affected payment statuses were manually corrected to ensure accuracy. We continue to work closely with our network provider to prevent similar delays in status confirmations in the future and to improve monitoring for missing acknowledgements.

Read the full incident report →

Started Apr 28, 2026, 07:32 AM UTC· resolved Apr 28, 2026, 05:15 PM UTC

1. investigating Apr 28, 2026, 07:32 AM UTC

   We are currently investigating an issue affecting the functionality to create CAD virtual accounts.

2. investigating Apr 28, 2026, 10:13 AM UTC

   We are working with our Banking Partner to resolve this issue and will update once the issue has been resolved.

3. resolved Apr 28, 2026, 05:15 PM UTC

   Issue has been mitigated and all vans have been created.

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

   # Overview On 27 April 2026, we identified an issue affecting the creation of virtual accounts \(VANs\) via one of our external network partners in the production environment. During this period, requests to create new virtual accounts were not completing successfully due to an authentication failure when communicating with the network partner. Service was fully restored once the underlying cause was addressed and normal processing resumed. # Client Impact Clients attempting to create Canadian Dollar virtual accounts backed by our network partners experienced delays, as new virtual accounts could not be created during the incident window. Existing virtual accounts and previously created account details were not impacted, and there was no loss of data or funds. Once the issue was resolved, the system automatically processed the accumulated backlog, and all pending virtual account creation requests were successfully completed. Clients were not required to take any action. # Root Cause The root cause of the incident was an expired authentication token used by our virtual accounts service when making API requests to our network partners. As a result, the network partners rejected virtual account creation requests with authorization errors, preventing new virtual accounts from being generated. The token expiry was not detected in advance due to insufficient monitoring and alerting around external credential lifecycles. Once the new token was issued, it was securely updated in our systems and the affected services were restarted, restoring successful communication. Additional monitoring and alerting have since been implemented to track token expiry and prevent recurrence of this issue.

Read the full incident report →

Started Apr 07, 2026, 03:53 PM UTC· resolved Apr 08, 2026, 01:58 PM UTC

1. investigating Apr 07, 2026, 03:53 PM UTC

   We are currently investigating an issue affecting the status updates for some RON local payments. Payments are processing as expected, however status confirmations may temporarily appear delayed due to pending acknowledgements from our RON network partner. This may cause some payments to display as incomplete even though they are being processed normally. We are working closely with the network partner to receive the outstanding acknowledgements and update payment statuses accordingly. No action is required from clients at this time.

2. resolved Apr 08, 2026, 01:58 PM UTC

   This incident has been resolved.

3. postmortem Apr 14, 2026, 02:52 PM UTC

   # **Overview** A high volume of RON payments experienced delays in status updates, remaining in a “submitted” state longer than expected. The issue primarily affected larger batch submissions. # **Client Impact** Payments were processed as expected however, status updates were delayed, causing transactions to remain in a “submitted” state longer than usual. # **Root Cause** The delay was caused by processing constraints on the side of our network partner following increased volumes after a bank holiday, which impacted the timely issuance of status updates. # **Remediation** We confirmed that payments were successfully received and processed by our network partner and continued to monitor progress to completion. We are working closely with the partner to improve the timeliness of status updates and reduce the likelihood of similar delays during peak volume periods.

Read the full incident report →

Started Apr 02, 2026, 12:29 PM UTC· resolved Apr 02, 2026, 01:18 PM UTC

1. investigating Apr 02, 2026, 12:29 PM UTC

   We are experiencing a system issue that is impacting direct.currencycloud.com and api.currencycloud.com

2. investigating Apr 02, 2026, 12:32 PM UTC

   We are currently investigating an issue affecting API traffic to api.currencycloud.com, which may cause service disruption, authentication issues, or failed requests for some customers. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. Thank you for your patience, and we apologise for any inconvenience caused.

3. investigating Apr 02, 2026, 01:16 PM UTC

   The issue affecting API traffic to api.currencycloud.com has now been fully resolved. Services have returned to expected behaviour, and all systems are operating normally. Our teams identified the root cause and implemented a fix to restore full functionality. We will continue to monitor the platform to ensure ongoing stability. We sincerely apologise for any disruption this may have caused and appreciate your patience while we worked to resolve the issue.

4. resolved Apr 02, 2026, 01:18 PM UTC

   The issue affecting API traffic to api.currencycloud.com has now been fully resolved. Services have returned to expected behaviour, and all systems are operating normally. Our teams identified the root cause and implemented a fix to restore full functionality. We will continue to monitor the platform to ensure ongoing stability. We sincerely apologise for any disruption this may have caused and appreciate your patience while we worked to resolve the issue.

5. postmortem Apr 14, 2026, 02:53 PM UTC

   # **Overview** On 2 April 2026, the production API experienced a temporary service disruption, resulting in increased request failures and timeouts. The issue was identified and resolved following the rollback of a recent internal change. # **Client Impact** Clients experienced intermittent failures, including authentication issues and timeouts when accessing the production API, leading to temporary service disruption. # **Root Cause** The incident was caused by an internal deployment change that impacted connectivity between the API Gateway and upstream services, affecting request processing. # **Remediation** The impacted change was rolled back, restoring normal service. A full root cause review is underway, with improvements being made to deployment controls and validation processes.

Read the full incident report →

Started Mar 31, 2026, 05:37 PM UTC· resolved Apr 01, 2026, 09:33 AM UTC

1. investigating Mar 31, 2026, 05:37 PM UTC

   We are currently investigating an issue affecting a subset of DKK payments. Customers may experience delays in processing due to an issue with one of our network partners. Our team is actively working with the partner to resolve the issue as quickly as possible. We will provide further updates as soon as more information becomes available.

2. resolved Apr 01, 2026, 09:33 AM UTC

   The issue affecting a subset of DKK payments has been resolved. Payment processing has returned to normal, and any delayed transactions are now being completed. We will continue to monitor closely to ensure ongoing stability. Thank you for your patience.

3. postmortem Apr 14, 2026, 02:54 PM UTC

   # **Overview** An issue impacted the processing of certain DKK payments, where payments did not progress as expected despite funds being successfully received by our DKK network partner. # **Client Impact** Some payments experienced delays in completion. The majority were processed on the same day, with a small number completing the following business day. # **Root Cause** The delay was caused by a processing gap on the side of our DKK network partner, where incoming funds were not promptly applied, preventing payments from completing as expected. # **Remediation** The issue was resolved following intervention with our DKK network partner to apply the funds and complete processing.

Read the full incident report →

Started Mar 13, 2026, 05:33 PM UTC· resolved Mar 18, 2026, 11:12 AM UTC

1. investigating Mar 13, 2026, 05:33 PM UTC

   We are currently investigating delays within the Confirmation of Payee (COP) inbound service. Our engineering team is actively working to identify and resolve the issue as quickly as possible. We will provide further updates as soon as more information becomes available. We appreciate your patience while we work to resolve this.

2. resolved Mar 18, 2026, 11:12 AM UTC

   The issue impacting the Confirmation of Payee (CoP) inbound service has been resolved, and service was fully restored to business as usual from 5:30pm (UK time) yesterday. Our engineering team has implemented a fix and continues to monitor the service to ensure ongoing stability. We apologise for any inconvenience caused and thank you for your patience.

3. postmortem Mar 23, 2026, 11:45 AM UTC

   # Overview The inbound Confirmation of Payee \(COP\) service experienced slower‑than‑expected processing of account updates. While core COP checks continued to operate normally, some newly created accounts took longer to appear in the directory service of an external partner, which could affect matching availability for some customers. Normal processing has since been fully restored, and the backlog of updates has cleared. # Client Impact New accounts took longer than expected to appear in the external partner directory. Some sub‑accounts were also delayed in being registered. Existing accounts were not affected and continued to receive expected COP match responses. Core COP request/response behaviour remained within expected performance levels. # Root Cause The delays occurred because the COP inbound service received a higher‑than‑usual volume of account updates over a short period. These updates are sent to an external partner’s directory service, which applies standard processing limits to ensure stability. The temporary increase in traffic exceeded those limits, leading to a queue of updates waiting to be processed. As a result, some newly created accounts took longer than usual to appear in the directory. Once the update volume naturally returned to normal levels, the queue cleared and processing performance stabilised without further action required.

Read the full incident report →

Started Mar 12, 2026, 09:18 AM UTC· resolved Mar 12, 2026, 12:27 PM UTC

1. investigating Mar 12, 2026, 09:18 AM UTC

   We are currently investigating an issue affecting login and API connectivity within our Demo testing environment. Some clients may experience difficulty accessing the demo platform or making API requests. Our engineering team is actively working to identify and resolve the issue as quickly as possible. Important: This issue only affects the Demo environment used for testing and development. Our live production environment is operating normally and is not impacted. We will provide further updates as soon as more information becomes available. We appreciate your patience while we work to resolve this.

2. resolved Mar 12, 2026, 12:27 PM UTC

   This incident has been resolved.

3. postmortem Mar 13, 2026, 12:02 PM UTC

   # **Multiple issues on API DEMO** ## **Overview** Between 11–12 March 2026, some users of the API Demo environment experienced difficulties signing in and accessing certain test endpoints. This occurred during routine improvements to the demo gateway. ## **Client Impact** Affected users saw messages such as invalid credentials or 429 rate‑limit responses. This only affected testing activity in the demo environment for a limited period. ## **Root Cause** The situation arose when the Demo environment briefly began using a newer gateway that expected a different token format. Since many users were still using the previous format, this created compatibility issues that led to the authentication and rate‑limit behaviour observed. Returning the environment to the earlier gateway immediately restored all expected functionality. Currencycloud Confidential

Read the full incident report →

Started Mar 02, 2026, 10:00 AM UTC· resolved Mar 02, 2026, 12:40 PM UTC

1. investigating Mar 02, 2026, 10:00 AM UTC

   We are investigating an issue that is impacting clients using Payment Tracking for SWIFT Payments.

2. resolved Mar 02, 2026, 12:40 PM UTC

   The incident has now been resolved.

3. postmortem Mar 04, 2026, 05:19 PM UTC

   # Overview A certificate used by the Swift Microgateway service reached its expiry. resulting in a number of requests passing through the gateway returning with “expired certificate” error messages. # Client Impact The Swift payment tracking flow experienced temporary failures. # Root Cause The issue stemmed from the certificate lifecycle reaching its end, which only became visible once the expiration date was reached on live hosts. Once each host was updated, connectivity and authentication validated successfully.

Read the full incident report →

Started Feb 20, 2026, 06:44 PM UTC· resolved Feb 20, 2026, 09:41 PM UTC

1. investigating Feb 20, 2026, 06:44 PM UTC

   We are investigating an issue that is impacting clients attempting to get a rate for KWD, we are working with our FX Partner to resolve the issue as soon as possible

2. resolved Feb 20, 2026, 09:41 PM UTC

   This incident has been resolved.

3. postmortem Mar 04, 2026, 05:18 PM UTC

   # Overview On 2026-02-20 between 15:30 UTC and 18:34 UTC, a number of clients were unable to obtain pricing for KWD currency pairs via our FX Provider Services. All other currency pairs operated normally. The issue was promptly resolved once pricing was restored by our external provider. # Client Impact Impact was limited to KWD currency pairs. Clients requesting KWD spot or forward rates during the affected period received “No Price Available” responses. No further impact on client trades # Root Cause The incident was caused by a temporary outage at our external FX provider, which prevented them from supplying KWD pricing. Connectivity remained intact, and pricing resumed once the provider restored service. Pricing resumed at 18:34 UTC, and services are fully operational.

Read the full incident report →

Started Feb 20, 2026, 09:31 AM UTC· resolved Feb 24, 2026, 03:38 PM UTC

1. identified Feb 20, 2026, 09:31 AM UTC

   We are currently experiencing an issue with the Bulk Upload feature. As a temporary measure, the service has been disabled while our team works on a resolution. All other platform functionality remains operational. We will provide an update as soon as more information becomes available.

2. identified Feb 20, 2026, 09:33 AM UTC

   We are continuing to work on a fix for this issue.

3. resolved Feb 24, 2026, 03:38 PM UTC

   The issue impacting the Bulk Upload feature has now been resolved. We will continue to monitor closely to ensure ongoing stability of this feature.

4. postmortem Mar 03, 2026, 03:50 PM UTC

   # **Overview** During a development rollout for the Bulk Upload feature, the new flow did not consistently retain the “on behalf of” \(OBO\) account behaviour. # **Client Impact** A very small number of records were created under the house account instead of the intended sub‑accounts during Bulk Upload activity. # **Root Cause** A recent update to the bulk‑upload process introduced a change in how account information was passed between internal services. In certain cases, this caused the system to default to the house account instead of the selected sub‑account. The issue was quickly identified and corrected. ‌ ‌ ‌ ‌ ‌ **Currencycloud Confidential**

Read the full incident report →

Started Feb 17, 2026, 05:15 PM UTC· resolved Feb 17, 2026, 05:31 PM UTC

1. investigating Feb 17, 2026, 05:15 PM UTC

   We are currently investigating an issue affecting certain FX transactions involving GBP currency pairs, including GBP/USD and GBP/EUR. Clients may experience failures when submitting trade date amendments for FX deals or when executing trades via BARX in impacted pairs. Our technical teams are actively working to identify the root cause and restore normal service as quickly as possible.

2. resolved Feb 17, 2026, 05:31 PM UTC

   The issue impacting certain GBP currency pairs, including GBP/USD and GBP/EUR, has now been resolved. The root cause was identified as an external network partner issue. The partner has confirmed remediation, and services have been fully restored. Trade date amendments and BARX executions are now processing as expected. We will continue to monitor closely to ensure ongoing stability.

3. postmortem Feb 20, 2026, 10:08 AM UTC

   # Overview Between 17:15 and 17:31 UTC, some FX transactions in select GBP currency pairs experienced intermittent failures affecting trade date amendments and executions. The issue was identified and resolved within 16 minutes. # Client Impact Impact was limited to specific GBP pairs, with no confirmed financial or data integrity impact. All other FX services operated normally. # Root Cause The incident was caused by a temporary disruption involving an external network partner supporting certain FX transaction flows. # Remediation Connectivity was restored following corrective measures by the partner, and services are now fully operational with continued monitoring in place.

Read the full incident report →

Started Feb 12, 2026, 09:20 AM UTC· resolved Feb 12, 2026, 02:26 PM UTC

1. investigating Feb 12, 2026, 09:20 AM UTC

   We are currently investigating an issue impacting the processing of some TRY and CHF payments. A number of payments are currently delayed and not progressing as expected. Our engineering teams are actively working to identify the root cause and restore normal processing as quickly as possible. We will provide a further update once additional information becomes available. We apologise for the inconvenience and appreciate your patience.

2. resolved Feb 12, 2026, 02:26 PM UTC

   The issue impacting the processing of some TRY and CHF payments has now been resolved. Payment processing has been fully restored, and all previously delayed payments have been successfully processed to value date. We apologise for the disruption caused and appreciate your patience while we worked to resolve this matter.

3. postmortem Feb 16, 2026, 05:51 PM UTC

   ## Overview An issue occurred following an external service configuration update, which caused disruption to the processing of some TRY and CHF payments. The incident was identified when a subset of payments failed to progress as expected due to connectivity validation errors. ## Client Impact Clients submitting TRY and CHF payments experienced processing delays during the incident window. Payments remained pending until service connectivity was restored. All affected payments have since been successfully processed to value date, and no payments were lost or duplicated. ## Root Cause The issue originated from a scheduled security certificate rotation performed by an external payment provider. The corresponding certificate updates were not applied within the payment service configuration in time, resulting in validation failures that prevented successful transmission of certain TRY and CHF payments. ## Remediation The issue was resolved by updating the relevant security certificates within the payment service configuration, restoring normal connectivity and processing. Additional measures have been implemented to strengthen certificate lifecycle tracking, improve communication routing for third-party notifications, and enhance monitoring to detect similar validation failures earlier.

Read the full incident report →

Started Jan 29, 2026, 03:41 PM UTC· resolved Jan 29, 2026, 05:13 PM UTC

1. investigating Jan 29, 2026, 03:41 PM UTC

   We are currently investigating an issue impacting EUR payments instructed via DIRECT. Some customers may experience delays or failures when submitting or processing these payments.

2. resolved Jan 29, 2026, 05:13 PM UTC

   The issue impacting EUR payments instructed via DIRECT has now been resolved. All payment submissions and processing are operating normally. We will continue to monitor closely.

3. postmortem Feb 04, 2026, 09:24 AM UTC

   **Overview** An issue occurred after a production release, which caused degraded performance for EUR payments submitted through the DIRECT portal. The incident was detected when payment processing began returning errors inconsistent with expected behaviour. **Client Impact** Clients using the DIRECT portal experienced delays and failed attempts when submitting or processing EUR payments. The disruption persisted until the service was restored and payment processing returned to normal performance. **Root Cause** The issue originated from a logic gap introduced during a production release, where beneficiary verification was incorrectly executed for unsupported currency flows. Null configuration values were incorrectly resolved as enabled, causing unintended verification attempts and resulting in payment failures. **Remediation** The issue was mitigated by rolling back the affected release, which immediately restored expected processing behaviour. Preventative measures were implemented to restrict verification logic to the appropriate currency path, correct configuration handling, and strengthen test coverage to avoid similar regressions. ###### Currencycloud Confidential

Read the full incident report →

Started Jan 26, 2026, 02:06 PM UTC· resolved Jan 27, 2026, 04:17 PM UTC

1. investigating Jan 26, 2026, 02:06 PM UTC

   We’re currently experiencing an issue affecting SEPA (non-instant) credit transfers. As a result, SEPA credit payments submitted today may be processed later than usual. No payments are lost as they shall be completed once the issue is resolved. We’re actively working with our Network Partners to resolve this and will provide updates as soon as more information is available. We apologise for the inconvenience and appreciate your patience.

2. identified Jan 26, 2026, 06:27 PM UTC

   We are currently experiencing an issue affecting SEPA (non-instant) credit transfers. The root cause has been identified, and corrective actions are underway in collaboration with our Network Partner. We expect the service to return to normal operation by tomorrow. Any SEPA credit payments submitted today that are delayed will be manually remediated tomorrow to ensure completion. We apologise for the inconvenience and appreciate your patience as we work to resolve this.

3. resolved Jan 27, 2026, 04:17 PM UTC

   The issue affecting SEPA (non-instant) credit transfers has now been resolved. Processing of impacted payments submitted between 23 and 26 January has resumed and payments are beginning to complete. Full remediation, including completion of all remaining delayed payments, is expected to be finalised by tomorrow. We will continue to closely monitor processing to ensure stability. We apologise for the inconvenience caused and thank you for your patience.

4. postmortem Jan 30, 2026, 05:32 PM UTC

   # Overview An issue had occurred when an external configuration change blocked inbound payment funding flows and prevented normal funds processing. Normal operation was restored after the block was reverted through coordination with the external partner. # Client Impact Clients experienced temporary delays to SEPA credit transfers submitted during the affected period. All impacted payments were later processed once funding had been restored. # Root Cause The incident was caused by an external configuration error in which an inbound payment restriction was applied too broadly to Currencycloud accounts. This misconfiguration prevented funding from being credited and created downstream processing delays. # Remediation The restriction was promptly reverted in collaboration with the network partners, allowing funding flows to resume. Impacted payments were reprocessed and monitored until completion.

Read the full incident report →