Sep <var data-var='date'>24</var>, <var data-var='time'>17:00</var> UTC Resolved - On 24 September 2026, some customers experienced authentication failures when accessing Currencycloud services via our API and platform. The issue was linked to a software release and was resolved by rolling back the change. Service was restored and monitoring has confirmed normal operation since recovery. A detailed root cause analysis is currently being completed and is undergoing internal review. Further information will be shared once that process is complete. We apologise for the disruption and thank our customers for their patience.

API Authentication Errors

Sep <var data-var='date'>22</var>, <var data-var='time'>04:44</var> UTC Resolved - The issue causing intermittent API errors has been resolved, and services are operating normally. A number of API requests experienced transient failures during brief periods of elevated error rates; however, no further issues have been observed since mitigation was completed. Sep <var data-var='date'>21</var>, <var data-var='time'>21:14</var> UTC Monitoring - We have identified the cause of the elevated error rates and implemented mitigation. A platform-wide node replacement event briefly left services without ready endpoints to handle requests. We have rolled back a recent deployment as a precaution and confirmed service stability has been restored. A small subset of requests may have experienced errors during the brief window when endpoints were unavailable. Our teams are actively monitoring the affected services to ensure full stability before returning to standard operations. Sep <var data-var='date'>21</var>, <var data-var='time'>20:39</var> UTC Investigating - An issue is currently affecting multiple API endpoints and is under investigation. A spike in server errors was detected and has since subsided with no further errors observed. We are monitoring the situation closely and will provide updates as the investigation progresses. Some customers may have experienced errors when accessing endpoints during the incident window. We appreciate your patience as we investigate the root cause and work to prevent recurrence.

Errors on multiple API endpoints.

Sep <var data-var='date'>17</var>, <var data-var='time'>10:11</var> UTC Resolved - CAD payment processing has remained stable since 14 September, with no repeat instances of the issue observed. As service has continued to operate as expected throughout the monitoring period, this incident is now considered resolved. We will continue to work with relevant network partners on follow-up actions and preventative measures arising from our review of the incident. Sep <var data-var='date'>16</var>, <var data-var='time'>10:38</var> UTC Monitoring - We have not observed any further instances of the issue affecting CAD payments since 14 September, and payment processing continues to operate as expected. Our teams remain engaged with the banking partner to complete the root cause investigation into the initial subset of payment failures. While service remains stable, we will continue to monitor closely and provide further updates if new information becomes available. Sep <var data-var='date'>14</var>, <var data-var='time'>16:09</var> UTC Investigating - We are currently investigating an issue affecting CAD payments processed through one of our banking partners. As a result, some customers may experience payment failures or delays in processing. Our teams are actively working with the provider to identify the cause and restore normal service as quickly as possible. We will continue to provide updates as more information becomes available.

Subset Customers Experiencing CAD Payment Failures and Processing Delays

Sep <var data-var='date'>14</var>, <var data-var='time'>14:46</var> UTC Resolved - The issue affecting one of our non-production demonstration environments has now been fully resolved, and services have returned to normal operation. The disruption was limited to the demo environment only. There was no impact to Currencycloud production services, client funds, payment processing, or live customer activity at any point during the incident. Following remediation and validation activities, the affected demo services have been restored and are operating as expected. We will continue to monitor the environment as part of normal operational oversight. Sep <var data-var='date'>14</var>, <var data-var='time'>13:29</var> UTC Investigating - We are currently investigating an issue affecting one of our non-production demonstration environments. The issue is impacting access to and functionality within the demo environment only. There is no impact to Currencycloud production services, client funds, payment processing, or live customer activity. All production systems remain fully operational. Our teams are actively working to restore the affected demo environment, and we will continue to monitor progress until service has been fully recovered.

Demo Environment Service Disruption

Sep <var data-var='date'>14</var>, <var data-var='time'>09:34</var> UTC Resolved - We have resolved the issue affecting foreign exchange quote and trade processing. Following investigation and recovery activities, services have been fully restored and traffic has been returned to the standard provider configuration. Quote and trade processing are operating normally, and monitoring has confirmed stable performance across affected currency pairs. We will continue routine monitoring, but no further customer impact is expected. Sep <var data-var='date'>11</var>, <var data-var='time'>16:17</var> UTC Monitoring - We have identified the cause of the issue affecting foreign exchange quote and trade processing and have implemented mitigation measures to restore service availability. Trading functionality has been restored and quote requests have been rerouted through an alternative provider while we continue to monitor platform stability. Customers may continue to experience differences in quote availability for a small subset of currency pairs while traffic remains routed through the alternative provider. Our teams are actively monitoring the service and validating performance before returning to the standard provider configuration. Sep <var data-var='date'>11</var>, <var data-var='time'>13:57</var> UTC Investigating - We are currently experiencing an issue affecting foreign exchange quote and trade processing for a subset of currency pairs. To minimise customer impact, traffic has been rerouted to an alternative provider while our teams investigate the underlying issue. Customers may experience reduced quote availability or delays for some non-major currency pairs. We are actively monitoring the service and will provide further updates as more information becomes available.

Issue affecting foreign exchange quote and trade processing

Sep <var data-var='date'>13</var>, <var data-var='time'>02:00</var> UTC Completed - The scheduled maintenance has been completed. Sep <var data-var='date'>13</var>, <var data-var='time'>00:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'> 6</var>, <var data-var='time'>08:17</var> UTC Scheduled - The Currencycloud Production environment will be undergoing scheduled maintenance on Sunday September 13th at 00:00 UTC

Production Environment - Planned Outage

Sep <var data-var='date'> 8</var>, <var data-var='time'>16:12</var> UTC Resolved - Webhook notifications are being processed and delivered normally. The backlog of delayed notifications has been fully cleared and service continued to operate throughout the incident. Engineering has implemented remediation measures and no further delays are expected. We will continue to monitor the service as part of normal operations. No client action is required. Sep <var data-var='date'> 8</var>, <var data-var='time'>15:21</var> UTC Monitoring - Webhook notifications continue to be processed and delivered, although some clients may still experience delays while recovery activities remain in progress. Engineering has deployed an additional change designed to reduce database load and improve processing throughput. This update is currently being rolled out and early indicators show backlog volumes continuing to reduce. In parallel, a further corrective change addressing the underlying cause has been identified and is undergoing final review prior to deployment. We are actively monitoring service performance and backlog reduction as processing returns to normal levels. No client action is required at this time. Sep <var data-var='date'> 8</var>, <var data-var='time'>14:15</var> UTC Identified - We have identified the cause of delays affecting webhook notification delivery and are implementing a phased remediation plan. Our immediate priority is to restore normal processing rates and reduce the backlog of delayed notifications. In parallel, Engineering is implementing a corrective change to address the underlying issue and prevent recurrence. Clients may experience delays in receiving webhook notifications while recovery activities are ongoing. We are actively monitoring progress and will continue to provide updates as service recovers. No client action is required at this time. Sep <var data-var='date'> 8</var>, <var data-var='time'>13:51</var> UTC Investigating - We are currently investigating delays affecting the delivery of webhook notifications. Our teams are actively reviewing the issue and working to restore normal service. We will provide further updates as more information becomes available. No client action is required at this time.

Webhook Notification Delays

Sep <var data-var='date'> 5</var>, <var data-var='time'>05:13</var> UTC Resolved - The incident has been resolved. A connector within our service had failed and did not re-establish connectivity. The connector is now running and further investigation to prevent re-occurrence will be carried out. Sep <var data-var='date'> 5</var>, <var data-var='time'>02:15</var> UTC Investigating - We are currently investigating an issue affecting the functionality to create EUR virtual accounts.

EUR virtual account creation.

Sep <var data-var='date'> 4</var>, <var data-var='time'>19:44</var> UTC Resolved - The issue affecting webhook notification delivery has now been resolved. All queued webhook notifications, including the backlog accumulated during the incident, have been successfully processed and delivered. Throughout the recovery period, Engineering investigated intermittent processing behaviour that caused backlog processing to pause and subsequently resume. Recovery actions were completed successfully, processing stability was restored, and queue volumes returned to normal operating levels. Underlying transactions continued to process normally throughout the incident and no data loss has been identified. Recovery validation has been completed and the service is operating as expected. Sep <var data-var='date'> 4</var>, <var data-var='time'>19:11</var> UTC Update - Webhook processing remains active and delayed notifications continue to be delivered. Overall queue volumes have reduced by approximately 85%, including both the original backlog and newly generated webhook events. Engineering continues to investigate the intermittent behaviour causing backlog processing to pause and subsequently resume. Whilst recovery is progressing and queue volumes continue to reduce, processing rates have varied during the recovery period and investigation remains ongoing to identify the underlying cause and restore consistently stable processing. Underlying transactions continue to process normally and no data loss has currently been identified. Sep <var data-var='date'> 4</var>, <var data-var='time'>18:23</var> UTC Update - Webhook processing remains active and delayed notifications continue to be delivered. Overall queue volumes have reduced by approximately 70%, including both the original backlog and newly generated webhook events. Engineering continues to investigate the intermittent behaviour causing backlog processing to pause and subsequently resume. Whilst recovery is progressing and queue volumes continue to reduce, processing rates have varied during the recovery period and investigation remains ongoing to identify the underlying cause and restore consistently stable processing. Underlying transactions continue to process normally and no data loss has currently been identified. Sep <var data-var='date'> 4</var>, <var data-var='time'>16:32</var> UTC Monitoring - Webhook processing has resumed and delayed notifications are being delivered. Engineering is continuing to investigate an intermittent issue that is causing backlog processing to pause and restart, with recovery efforts focused on maintaining stable processing until all queued notifications have been delivered. Sep <var data-var='date'> 4</var>, <var data-var='time'>15:23</var> UTC Update - The production fix remains deployed and has addressed the original issue that caused webhook notifications to accumulate. However, processing of the retained backlog has stopped again, and delayed notifications are not currently progressing through the queue. Engineering Teams are actively investigating a secondary issue affecting backlog processing and is working to restore delivery while preserving all queued webhook events. Underlying transactions continue to process normally, but clients will continue to experience delayed webhook notifications until backlog processing resumes. No data loss has currently been identified. We will provide a further update once sustained processing and queue reduction have been restored. Sep <var data-var='date'> 4</var>, <var data-var='time'>14:43</var> UTC Identified - The production fix remains deployed and addressed the original issue that caused webhook notifications to accumulate. However, processing of the existing backlog stopped at approximately 14:40 BST, and delayed notifications are not currently progressing through the queue. Engineering is actively investigating the cause and assessing the safest recovery action while preserving all queued webhook events. Current evidence suggests this remains related to processing the unusually high backlog volume rather than a new issue affecting underlying transactions. Transactions continue to process normally, but clients will continue to experience delayed webhook notifications until backlog processing resumes. We will provide a further update once sustained processing and queue reduction have been restored. Sep <var data-var='date'> 4</var>, <var data-var='time'>14:10</var> UTC Update - The production fix remains in place and has addressed the original issue that caused webhook notifications to accumulate. During recovery, processing of the existing backlog has slowed due to database load, and Engineering is investigating the safest way to resume and accelerate clearance without placing additional pressure on the service. This is not currently considered a recurrence of the original incident. It relates to processing the unusually high volume of notifications already queued. Underlying transactions continue to process normally, but clients may continue to experience delays in receiving webhook notifications while backlog recovery is completed. Sep <var data-var='date'> 4</var>, <var data-var='time'>13:36</var> UTC Monitoring - We have mitigated the issue affecting webhook notification delivery. A targeted fix has been successfully deployed to production, and webhook notifications are now being processed and delivered. The queue of delayed notifications is reducing, and current recovery indicators show the service is operating as expected. Underlying transactions, funding events and bank transfers continued to process successfully throughout the incident. Current evidence indicates that webhook notifications were delayed and retained for delivery rather than lost, although delivery validation remains ongoing. No client action is required at this time. Sep <var data-var='date'> 4</var>, <var data-var='time'>07:10</var> UTC Investigating - We are currently investigating an issue affecting webhook notification delivery for some Currencycloud customers. Customers may experience delayed or missing webhook notifications for transactions, funding events, and bank transfers. We have received reports from multiple customers and are actively working to determine the scope and cause of the issue. Our teams are investigating with the highest priority and will provide updates as they become available. We apologize for any inconvenience and appreciate your patience while we work to resolve this issue.

Webhook Notification Delivery Delays and Missing Notifications

Sep <var data-var='date'> 4</var>, <var data-var='time'>09:23</var> UTC Resolved - Our investigation confirmed the issue was caused by external telecommunications and regulatory restrictions impacting SMS delivery, and not by a fault within the Currencycloud platform. We apologise for any inconvenience caused. Sep <var data-var='date'> 1</var>, <var data-var='time'>11:55</var> UTC Update - We have identified that some customers using mainland China (+86) phone numbers may experience issues receiving SMS verification codes required to access the Currencycloud platform. Our investigation has determined that SMS delivery to mainland China is currently being impacted by regulatory restrictions and controls imposed by Chinese authorities. As a result, verification messages may be delayed or not delivered, preventing some users from completing authentication. We are actively working with our messaging providers and partners to understand the scope of these restrictions, explore available mitigations, and identify potential long-term solutions. At this time, we do not have a confirmed resolution timeline. We apologise for the inconvenience and will continue to provide updates as more information becomes available. Sep <var data-var='date'> 1</var>, <var data-var='time'>11:16</var> UTC Monitoring - We are aware of an issue affecting SMS-based multi-factor authentication (MFA) for users with +86 China phone numbers, which may prevent some customers from receiving verification codes and accessing the Currencycloud platform. Our SMS provider has advised that message delivery to China are currently subject to regulatory restrictions imposed by local authorities. As a result, SMS delivery cannot be guaranteed and may be impacted by factors outside of our provider's control. Customers are encouraged to utilise email-based MFA, where available, as an alternative authentication method while we continue to work with our provider to address the SMS delivery challenges. Sep <var data-var='date'> 1</var>, <var data-var='time'>06:53</var> UTC Investigating - We are currently investigating an issue affecting SMS authentication for users with +86 China phone numbers, which may prevent some customers from receiving verification codes and accessing the Currencycloud platform. Our teams are actively investigating the issue and working on restoring normal authentication service as quickly as possible. Thank you for your patience, and we apologise for any inconvenience caused.

SMS Authentication Issues Affecting +86 Phone Numbers

Sep <var data-var='date'> 3</var>, <var data-var='time'>22:00</var> UTC Completed - The scheduled maintenance has been completed. Sep <var data-var='date'> 3</var>, <var data-var='time'>20:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>20</var>, <var data-var='time'>12:19</var> UTC Scheduled - We will be carrying out work on the Demo Environment that could cause clients to see errors during the work This change is expected to cause HTTP/503s during the rollout time. The change rollout is expected to be one minute with safe margin to apply changes if needed or to rollback in case of sustained errors.

DEMO Environment - Planned Maintenance

Sep <var data-var='date'> 2</var>, <var data-var='time'>08:41</var> UTC Resolved - The issue impacting payment processing was related to payment status updates only. All payments continued to be processed and executed as instructed. Due to an internal technical issue, we identified a delay in payment status updates being reflected within the platform. As a result, a subset of customers across multiple currencies and payment routes may have seen payments remain in an intermediate status for longer than expected, despite the payments being processed successfully. The issue was successfully resolved on 1 September 2026. All payment statuses have since been updated correctly, and no delays were experienced in the underlying processing or execution of payments. The service is operating normally. We apologise for any inconvenience caused. Sep <var data-var='date'> 1</var>, <var data-var='time'>15:34</var> UTC Investigating - We have identified an issue impacting payment processing. As a result, some payments may experience delays. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. Further updates will be provided as more information becomes available.

Issue Affecting Payment Processing

Sep <var data-var='date'> 1</var>, <var data-var='time'>16:15</var> UTC Resolved - The issue affecting the ability to view beneficiary information has now been resolved. Beneficiary details are loading normally and service stability has been confirmed through monitoring. We apologize for the inconvenience caused and appreciate your patience while teams investigated and restored the service. Sep <var data-var='date'> 1</var>, <var data-var='time'>14:33</var> UTC Monitoring - We have implemented recovery actions and service functionality has been restored. Customers should once again be able to view beneficiary details and access records that were previously returning errors. We are continuing to monitor the service to ensure stability while our teams complete their investigation into the underlying cause. We will provide a further update once issue is fully resolved. Sep <var data-var='date'> 1</var>, <var data-var='time'>13:36</var> UTC Investigating - We are investigating an issue affecting beneficiary details within Direct. As a result, some customers may be unable to view existing beneficiary information and may receive an error message when attempting to access beneficiary details. Our teams are actively investigating and working to restore normal service. We will provide further updates as more information becomes available.

Some Customers Unable to View Beneficiary Information

Sep <var data-var='date'> 1</var>, <var data-var='time'>11:06</var> UTC Resolved - The issue affecting payment processing has been resolved and normal service has been restored. During the incident, some customers experienced CAD payment failures. While services are now operating normally, a subset of CAD payments with a value date of 31 August 2026 did not complete successfully and were returned as failed. Customers with affected payments may need to resubmit those transactions. We apologise for the inconvenience caused and thank our customers for their patience while we worked to restore service. Aug <var data-var='date'>31</var>, <var data-var='time'>17:20</var> UTC Investigating - We are investigating an issue affecting payments processed through one of our banking partners. As a result, some customers may experience payment failures or delays in processing. Our teams are actively investigating and working with the provider to determine the cause and restore normal service as quickly as possible. We will provide further updates as more information becomes available.

Some Customers Experiencing Payment Failures and Processing Delays for CAD

Aug <var data-var='date'>25</var>, <var data-var='time'>15:13</var> UTC Resolved - We have implemented a fix for the issue affecting the processing of some SEK, NOK and DKK payments. The fix has been successfully deployed and processing has now resumed. All affected payments have been processed in line with their instructed value dates, and no further customer impact is expected. Our teams have completed validation activities and continue to monitor the service to ensure ongoing stability. Aug <var data-var='date'>25</var>, <var data-var='time'>11:37</var> UTC Monitoring - We have implemented a fix for the issue that affected the processing of SEK, NOK and DKK payments. The fix has resulted in the successful processing of the majority of previously impacted payments, which have now been processed with today's value date. A smaller subset of affected payments may still be delayed until the next available processing day. Our teams are continuing to review and validate. Further updates will be provided as they become available. Aug <var data-var='date'>25</var>, <var data-var='time'>10:49</var> UTC Identified - We have identified the cause of an issue affecting the processing of some payments and are currently implementing a fix. Customers may experience delays to some SEK, NOK and DKK payments submitted since 08:51 BST. Delayed payments are expected to be processed on the next available processing day. Other payment routes continue to operate as expected. Our engineering teams are completing the production rollout of the fix, restarting processing services, and validating recovery of the affected payment backlog. We continue to monitor the situation closely and will provide further updates as progress is confirmed. Aug <var data-var='date'>25</var>, <var data-var='time'>09:07</var> UTC Investigating - We are currently investigating an issue affecting the processing of some payments. Customers may experience delays in the processing of SEK, NOK and DKK payments while our engineers work to restore normal service. Other payment routes are operating as expected. Our teams have identified the issue and are implementing a fix. We are monitoring the situation closely and will provide further updates as they become available.

Potential delays to SEK, NOK & DKK

Aug <var data-var='date'>13</var>, <var data-var='time'>07:46</var> UTC Resolved - The issue affecting a number of SEK payments has been fully resolved. All delayed payments have now been processed successfully, and payment processing is operating as expected. Our teams have continued to monitor the service following the correction and have confirmed normal processing has been restored. We apologise for any inconvenience caused and thank you for your patience while we worked to resolve the issue. Aug <var data-var='date'>12</var>, <var data-var='time'>13:18</var> UTC Monitoring - The issue affecting a number of SEK payments has been corrected and payment processing has resumed. We are continuing to monitor the service to ensure all delayed payments are processed successfully and that normal operations are maintained. We apologise for any inconvenience caused. Aug <var data-var='date'>11</var>, <var data-var='time'>15:55</var> UTC Investigating - We are currently investigating a delay affecting a number of SEK payments being processed via our banking partners. As a result, some payments may take longer than expected to complete. Our teams are actively engaged with the partners to resolve the issue and restore normal processing as quickly as possible. We will provide further updates as more information becomes available. We apologise for any inconvenience caused.

Delays to SEK Local Payments

Jul <var data-var='date'>23</var>, <var data-var='time'>16:07</var> UTC Resolved - The issue affecting EUR payment services through one of our banking partners has been fully resolved. Services were restored on the day the issue was identified, and all payment processing functionality has been operating as expected since resolution. Following service restoration, all impacted transactions were reviewed and remediated. Any remaining delayed items have now been addressed, and normal processing has resumed. We apologise for any inconvenience caused and appreciate your patience while we worked with our banking partner to resolve the issue. Jul <var data-var='date'>21</var>, <var data-var='time'>12:28</var> UTC Monitoring - The issue affecting local EUR payment services through our banking partners has been resolved and services have been restored. Payment processing and virtual account services are operating normally once again. Our teams are completing recovery activities for a small number of transactions impacted during the outage and are monitoring the service closely to ensure a full return to normal operations. Customer funds remain secure. We will continue to monitor the service and provide a further update once all recovery activities have been completed. Jul <var data-var='date'>21</var>, <var data-var='time'>11:54</var> UTC Identified - We have identified an issue affecting local EUR payment services through our banking partners. As a result, some EUR payments may experience delays, and the creation of new EUR virtual accounts may be temporarily unavailable. Our banking partner has identified the underlying cause and is actively implementing a fix. We are working closely with them and continue to monitor progress while taking steps to minimise customer impact. Customer funds remain secure, and we will provide further updates as more information becomes available Jul <var data-var='date'>21</var>, <var data-var='time'>11:41</var> UTC Investigating - We are currently investigating an issue affecting local EUR payment services through our banking partners. As a result, some payments may experience delays while we work to restore normal service. Our teams are actively engaged with the provider and are taking steps to minimise customer impact. Customer funds remain secure, and we will provide further updates as more information becomes available.

Local EUR Payment Processing Delays

Jul <var data-var='date'>20</var>, <var data-var='time'>12:04</var> UTC Resolved - The issue has been identified and resolved, and services are operating normally. Our teams have validated recovery and continue to monitor the environment to ensure ongoing stability. At this time, we do not expect any impact or delays. Thank you for your patience while we investigated and resolved the issue. Jul <var data-var='date'>20</var>, <var data-var='time'>09:32</var> UTC Investigating - We are currently investigating an issue affecting internal access systems used by operational teams. Whilst payment processing services remain available, some manually processed activities, including funds allocation, sender verification and investigation-related requests, may experience delays. Our teams are actively working to restore full service and we will continue to provide updates as available.

Operational Delays to Manual Processing Activities

Jul <var data-var='date'>14</var>, <var data-var='time'>10:26</var> UTC Resolved - The previously delayed DKK payments related to this incident have now been successfully processed. The underlying issue was resolved last week, and all affected SEK, NOK and DKK payments have now completed. Payment processing has been operating normally, and no further customer impact remains. We apologise for any inconvenience caused and thank you for your patience while we worked with our network partner to fully remediate the issue. Jul <var data-var='date'>10</var>, <var data-var='time'>14:51</var> UTC Monitoring - While we previously communicated that the issue had been resolved, we have since identified a small subset of DKK payments that remain impacted by this incident. The underlying issue has been successfully resolved, and remediation activities have been completed for all affected SEK and NOK payments, which have now been processed successfully. While payment processing has returned to normal, a small number of DKK payments remain delayed. We continue to work closely with our network partner to recover these payments and complete full remediation. We apologise for the continued disruption and will provide a further update once all remaining impacted payments have been processed.

Delays to a subset of local DKK Payments

Jul <var data-var='date'>12</var>, <var data-var='time'>02:00</var> UTC Completed - The scheduled maintenance has been completed. Jul <var data-var='date'>12</var>, <var data-var='time'>00:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul <var data-var='date'> 6</var>, <var data-var='time'>07:20</var> UTC Scheduled - The Currencycloud Production environment will be undergoing emergency maintenance on Sunday July 12th at 00:00 UTC

Production Environment - Emergency Maintenance

Jul <var data-var='date'>10</var>, <var data-var='time'>13:32</var> UTC Resolved - The issue affecting a subset of local SEK, NOK and DKK payments has now been resolved, and payment processing has returned to normal. A small number of payments experienced delays of up to one business day while our teams worked with a network partner to address the issue. All impacted payments have now been processed or are progressing as expected. We apologise for any inconvenience caused and thank you for your patience. Jul <var data-var='date'> 9</var>, <var data-var='time'>21:18</var> UTC Monitoring - We have identified the cause of the issue affecting local SEK payment processing and have implemented a fix to prevent further delays. Some previously impacted SEK payments may remain delayed while affected funding is being recovered and payments are released for processing. We are monitoring recovery with our network partner and will provide a further update once payment processing has returned to normal. Jul <var data-var='date'> 9</var>, <var data-var='time'>14:56</var> UTC Investigating - We are investigating an issue affecting our SEK network partners which may result in delays to local SEK payment processing. Our teams are working with the network partner to restore normal service as quickly as possible. We will provide a further update as soon as more information becomes available.

Delays to local SEK Payments

Jul <var data-var='date'> 7</var>, <var data-var='time'>15:35</var> UTC Resolved - A fix has been implemented and Bulk Upload payment processing is operating normally. We have seen no further reports of the issue since the remediation was applied and are continuing to monitor the service closely. We apologise for the disruption caused and thank you for your patience while we investigated and resolved the issue. Jul <var data-var='date'> 7</var>, <var data-var='time'>10:59</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 6</var>, <var data-var='time'>12:59</var> UTC Investigating - We are aware of a small number of continued reports relating to Bulk Upload payment processing following the implementation of our initial fix. While the majority of Bulk Upload requests are processing successfully, we are investigating whether a subset of requests may still be affected under certain conditions. Our engineering teams are actively reviewing the recent reports and monitoring platform performance to determine whether any further corrective action is required. We apologise for the continued disruption and will provide further updates as soon as additional information becomes available.

Issues Affecting Bulk Upload Payment Processing

Jul <var data-var='date'> 7</var>, <var data-var='time'>14:51</var> UTC Resolved - The issue affecting payment validation services has now been resolved. Our teams implemented a fix and monitored the service to confirm stability, with no further issues observed. We apologise for any inconvenience caused and thank you for your patience. Jul <var data-var='date'> 6</var>, <var data-var='time'>19:13</var> UTC Monitoring - The issue has been mitigated and is being monitored. Jul <var data-var='date'> 6</var>, <var data-var='time'>12:30</var> UTC Investigating - We are currently investigating an issue affecting payment validation services. Some customers may experience errors when validating payments via the platform or API. Our engineering teams have identified the issue and are actively working to restore normal service as quickly as possible. We apologise for any inconvenience this may cause and will provide further updates as more information becomes available.

Issue Affecting Payment Validation Services

Jul <var data-var='date'> 3</var>, <var data-var='time'>12:06</var> UTC Resolved - The issue affecting Bulk Upload payment processing has now been resolved. We apologise for the inconvenience caused and appreciate your patience while our teams investigated and restored the service. Jul <var data-var='date'> 3</var>, <var data-var='time'>08:33</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'> 3</var>, <var data-var='time'>08:32</var> UTC Investigating - We are currently investigating an issue affecting Bulk Upload payment processing. Some users may experience uploaded files successfully validating or completing processing, but the associated payments may not be created as expected. Our engineering teams are actively working to identify the cause and restore normal service. We apologise for any inconvenience and will provide further updates as more information becomes available.

Jul <var data-var='date'> 3</var>, <var data-var='time'>10:51</var> UTC Resolved - We have implemented a fix for the issue affecting payment validation services, and service has been restored. Customers should now be able to validate payments normally via the platform and API. Our engineering teams are continuing a root cause investigation and are working on permanent improvements to prevent this issue from recurring. We apologise for any inconvenience caused. Jul <var data-var='date'> 3</var>, <var data-var='time'>10:03</var> UTC Investigating - We are currently investigating an issue affecting payment validation services. Some customers may experience errors when validating payments via the platform or API. Our engineering teams have identified the issue and are actively working to restore normal service as quickly as possible. We apologise for any inconvenience this may cause and will provide further updates as more information becomes available.

Is Currencycloud down?

Currencycloud status is UP

Lastest published events

API Authentication Errors

Errors on multiple API endpoints.

Subset Customers Experiencing CAD Payment Failures and Processing Delays

Currencycloud Services, Components and Regions

Recent Currencycloud events

API Authentication Errors

Errors on multiple API endpoints.

Subset Customers Experiencing CAD Payment Failures and Processing Delays

Demo Environment Service Disruption

Issue affecting foreign exchange quote and trade processing

Production Environment - Planned Outage