Currencycloud experienced a major incident on October 24, 2025 affecting Payments, lasting 4d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 24, 2025, 10:03 AM UTC
We're aware of an issue affecting local GBP funding and transactions. The root cause has been identified, and a fix has been implemented to prevent this from recurring. We're currently working on fully resolving the impact. During this remediation period, some local GBP payment statuses may display incorrectly, and local GBP funding may experience delays. Thank you for your patience as we complete the recovery process.
- identified Oct 24, 2025, 06:05 PM UTC
We’re aware of an ongoing impact related to the local GBP issue that occurred between 4:00 PM on Thursday 23rd and was fixed forward from 10:40 AM on Friday 24th. As a result, some payment statuses may still be displaying incorrectly, and GBP funding may be experiencing delays. We expect these remaining issues to be fully resolved early next week. We understand the inconvenience this may cause and want to assure you that resolving this is our top priority. Our teams are working diligently to restore full accuracy and normal service as quickly as possible. Thank you for your patience and understanding.
- identified Oct 27, 2025, 03:39 PM UTC
A remediation plan to address the impact related to the local GBP issue that occurred between 4:00 PM on Thursday 23rd and was fixed forward from 10:40 AM on Friday 24th is in progress. We are aware as a result, some payment statuses may still be displaying incorrectly, and GBP funding may be experiencing delays. Working with our local GBP network partner we have successfully tested resubmission of the impacted webhooks. We are proceeding with our release process to enable bulk remediation. We understand the inconvenience this may cause and want to assure you that resolving this is our top priority. Our teams are working diligently to restore full accuracy and normal service as quickly as possible. Thank you for your patience and understanding.
- identified Oct 27, 2025, 06:20 PM UTC
We can confirm that remediation action has commenced and the impact related to the local GBP issue that occurred between 4:00 PM on Thursday 23rd and was fixed forward from 10:40 AM on Friday 24th is starting to be resolved. Our teams, in collaboration with our local GBP network partner, have validated the remediation process and are now preparing a bulk resubmission solution, scheduled for implementation tomorrow (28 October). This will ensure that all remaining impacted items are fully resolved. We understand the inconvenience this issue has caused and appreciate your continued patience and understanding as we complete this final phase of recovery. Restoring full accuracy and normal service remains our top priority, and we will provide a further update once the bulk remediation has been completed.
- resolved Oct 28, 2025, 11:30 AM UTC
We can confirm that all remediation activities have now been completed. All impacted GBP payments have been successfully reconciled, with webhooks reissued, payment status updates corrected, and funding moved in line with the original instructions. We sincerely apologise for the delays and inconvenience this incident has caused. Our teams have conducted a full review in collaboration with our local GBP network partner to ensure that this issue is fully resolved. In addition, we will be undertaking a comprehensive review of the end-to-end process to strengthen controls and minimise the risk of similar disruptions in the future. We appreciate your continued patience and understanding as we worked to restore full service. Normal operations have now resumed.
- postmortem Nov 06, 2025, 04:46 PM UTC
# Overview A disruption to local GBP funding and transactions was experienced after banking partner \(webhook\) notifications were blocked. Service was restored and normal operations were confirmed following coordinated remediation with the local network partner. # Client Impact Payment statuses for transactions initiated between 4:00 PM on Thursday 23rd and 10:40 AM Friday 24th October were inaccurately displayed, and funds received during this period experienced delays. Customers remained affected until posting and status updates were corrected on 28 October. # Root Cause A custom content-scanning rule in Cloudflare’s Web Application Firewall blocked inbound partner webhooks, resulting in collection credits not being applied despite receipt of funds and payment statuses not being updated. The rule remained active until it was disabled, allowing webhook notifications to resume. # Remediation WAF content‑scanning rules were disabled, failed notifications were resent, webhooks were reissued, statuses were corrected, and funding was moved in line with instructions. Monitoring was increased and an end‑to‑end process review was initiated with the network partner to strengthen controls and prevent recurrence.