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.

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.

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.

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.

# Overview On Tuesday 8 September 2026, some customers experienced two periods of delay in receiving webhook notifications from Currencycloud. The first period occurred between 07:23 and 10:05 UK time, and the second between 14:01 and 17:10 UK time. During these periods, webhook events continued to be generated but accumulated temporarily within the notification processing queue and were delivered later than expected. Processing recovered and the queue returned to normal after corrective changes were deployed and recovery was validated. # Client Impact Customers using webhook notifications experienced delays in receiving transaction, funding and bank transfer updates during the two affected periods. This reduced real-time visibility and may have delayed automated workflows that depend on webhook receipt. Underlying transactions, funding activities and bank transfers continued to process successfully, and the Currencycloud platform remained available. Most delayed notifications were delivered as processing recovered. Subsequent validation identified notifications requiring targeted replay or recreation, and these were taken forward through controlled post-incident remediation. If you believe a specific notification remains missing, please contact your Currencycloud representative or Support with the relevant transaction reference so it can be investigated. No customer action was required to restore service. The incident affected the timing of notification delivery rather than the accuracy of the underlying transaction or payment records. No customer fund impact, security concern or financial loss was identified. # Root Cause The repeat delays were caused by retry-related processing within the webhook notification service. When an expected event record could not be found during retry validation, the same notification could be retried repeatedly, increasing database activity and temporarily reducing processing throughput. A further inefficient database lookup contributed to the load. This caused webhook events to build up in the queue until processing capacity recovered. Currencycloud deployed corrective changes to reduce database load, address the retry amplification behaviour and improve processing stability. The service was monitored until the queue returned to normal and webhook delivery resumed at expected levels. Further work includes completing the permanent indexed lookup, strengthening dependency-readiness controls, improving retry and dead-letter handling, and enhancing monitoring and controlled notification replay capabilities. ‌ ##### Currencycloud Confidential