Salt Edge Status Page

May 21, 2026 · resolved May 21

## Executive summary **Incident Summary** On 19 May 2026, Salt Edge identified an operational issue affecting one of the backend components supporting the Open Banking Gateway platform. Given the potential impact on platform stability, our Infrastructure team initiated immediate infrastructure stabilisation work. Before issuing this report, Salt Edge completed a detailed internal review covering the incident timeline, customer impact, technical behaviour, remediation measures, and follow-up actions. The infrastructure adjustment had been validated prior to production rollout. However, under live production workload and component synchronization conditions, the affected service behaved differently than expected following restart. This resulted in temporary processing errors and several short periods of service degradation. Salt Edge’s monitoring tools supported early identification of the issue and enabled the Infrastructure team to track the affected component closely throughout the remediation period. This helped contain the impact, avoid broader platform degradation, and minimise the effect on Open Banking Gateway processing. During the remediation window, parts of the Open Banking Gateway processing flow experienced intermittent interruptions. The most material impact occurred on **21 May 2026, between 12:23 UTC and 13:32 UTC**. The incident was fully resolved on **22 May 2026**. Salt Edge confirms that: * No data loss was identified. * No financial inconsistencies were detected. * The issue was not caused by any client-side integration, configuration, or API change. * No client-side action is required. The incident has been reviewed by the relevant technical teams, and additional preventive measures are being applied to further strengthen platform resilience under comparable production workload conditions. ## Incident overview |   |   | | --- | --- | | **Incident period** | 19 May 2026 - 21 May 2026 | | **Main impact window** | 21 May 2026, 12:23 - 13:32 UTC | | **Impact** | Temporary degradation of some Open Banking Gateway flows | | **Affected services** | Account Information API Payments API Partners API | | **Current Status** | Fully resolved | ## What Happened On 19 May 2026, Salt Edge identified an operational issue affecting one of the backend components supporting Open Banking Gateway services. Given the potential impact on service stability, our engineering team initiated immediate infrastructure stabilisation measures to contain the risk and preserve platform continuity. This was not a standard scheduled maintenance activity. The intervention was required to reduce the risk of broader service instability and to maintain controlled operation of the affected environment. The infrastructure change had been validated before being applied to production. However, under live production workload and component synchronisation conditions, the affected service required more time than expected to return to full availability following restart. Salt Edge’s monitoring tools supported early detection of the issue and enabled the engineering team to track the affected component closely throughout the remediation period. This helped contain the impact, prevent broader platform degradation, and minimise the effect on Open Banking Gateway processing. During the remediation period, certain Open Banking Gateway processing flows experienced temporary degradation. As a result, some requests were not processed successfully on the first attempt, while some background processing was delayed or retried automatically. Following further technical assessment, Salt Edge paused the remaining rollout activities and prepared an additional stabilisation package. To minimise customer impact, the final package was applied during an early morning low-traffic maintenance window on 22 May 2026. Once the maintenance window was completed, Open Banking Gateway services returned to stable operation. The incident was not related to any client-side integration, API change, request format, credentials, or client-side configuration. Timeline \(UTC\): | **Time** | **Event** | | --- | --- | | 19 May 2026 | An operational issue was identified in one of the backend components used by Open Banking Gateway services. | | 19 May 2026 | Due to the potential impact on service stability, stabilisation infrastructure work was started | | 19 May 2026 11:46 UTC | Infrastructure changes were applied to part of the Open Banking Gateway infrastructure. | | 19 May 2026 11:48 UTC | First application errors were observed. Short service degradation was observed. | | 19 May 2026 11:57 UTC | Affected application processing services were fixed. | | 19 May 2026 12:24 UTC | A second iteration was performed. The team fixed affected processing services immediately to avoid a longer unstable state | | 21 May 2026 12:23 - 13:32 UTC | Main impact window. Open Banking Gateway services experienced temporary processing errors. The services: Account Information and Payment Initiation-related flows were affected. | | 21 May 2026 | Following technical assessment, Salt Edge determined that the updated component should not remain in production without additional stabilisation. The team therefore prepared and applied a final stabilisation package to restore normal service behaviour and ensure continued platform reliability. | | 22 May 2026 02:36 - 02:57 UTC | The fixing package has been applied during the maintenance window. | ## Root Cause The root cause was a variance between the component’s expected behaviour in pre-production validation and its behaviour under live production workload during restart and synchronisation. While the change had been validated before rollout, production-specific workload conditions exposed an availability delay in the affected backend component. As a result, the component required additional time to become fully operational, temporarily impacting dependent Open Banking Gateway processing flows. This led to intermittent processing errors until the component was stabilised and normal service behaviour was restored. ## Resolution The immediate priority was to stabilise the affected services, contain the impact, and prevent broader platform degradation. Salt Edge paused any further rollout of the updated component, completed an additional technical assessment, and prepared a stabilised version for production deployment. The stabilisation package was completed on 21 May 2026. To minimise customer impact, it was applied during an early morning low-traffic maintenance window on 22 May 2026. Following the deployment, the affected services returned to stable operation. ## Detection The issue was detected through internal monitoring, application error tracking, and engineering checks during the corrective work. After the first signs of instability were identified, our team started investigation and mitigation immediately. ## Corrective & Preventive Measures We have initiated the following actions to prevent recurrence: 1. **Safer rollout procedure for backend infrastructure components**. We will improve the rollout process for backend components used by critical services, including clearer checkpoints before continuing from one stage to another. 2. **Additional validation before production rollout**. We will add stricter validation checks before applying package-level changes to critical production components. 3. **Long-term platform improvement.** We will continue reviewing long-term improvements for the backend processing layer used by our services. ## Contact If you have any questions about this incident or need assistance with affected transactions, please contact your account manager or reach out to our support team. We remain committed to providing reliable payment services and appreciate your continued partnership. _This report is intended for authorized partners only. Please do not distribute externally._

May 19, 2026 · resolved May 19

The incident has been fully resolved. Incident duration: From May 19th, 11:51 in UTC Until May 19th, 11:57 in UTC All services are now operating normally. Our team continues to monitor the system to ensure stability. We appreciate your patience and understanding. A detailed postmortem will be published shortly.

Mar 26, 2026 · resolved Mar 26

## Executive Summary On March 26, 2026, between **11:28 and 14:09 UTC**, our Payments API experienced a temporary disruption that prevented successful processing of payment initiation from Partners. The incident has been fully resolved. **We sincerely apologize for the interruption and any impact this may have caused to your operations.** ## **Incident Overview** |   |   | | --- | --- | | **Incident Date** | 26 Mar 2026 | | **Duration** | 151 minutes \(11:28-14:09 UTC\) | | **Impact** | Temporary inability to process payment initiation and account information requests. | | **Current Status** | ✅ **Resolved**. Infrastructure restored and operating normally | ## What Happened The disruption was caused by issues with transport certificates, which affected our payment initiation service for partners. This was not related to any client-side integration or API change. ## Timeline \(UTC\) | Time | Event | | --- | --- | | 11:28 | Service disruption detected via email alerts | | 11:30 | Engineering team engaged | | 12:22 | The root cause was detected | | 14:09 | Services fully restored | ## Root Cause The disruption was caused by issues with transport certificates. This was not related to any client-side integration or API change. ## Resolution The issue was resolved by reissuing new certificates. Normal payment processing resumed at **14:09 UTC**. ## Detection The incident was detected automatically via our service availability monitoring system \(emails\), which triggered alerts indicating degradation of services. The engineering team responded immediately upon alert notification. ## Contact If you have any questions about this incident or need assistance with affected transactions, please contact your account manager or reach out to our support team. We remain committed to providing reliable payment services and appreciate your continued partnership. _This report is intended for authorized partners only. Please do not distribute externally._

Mar 10, 2026 · resolved Mar 10

## Executive Summary On March 10, 2026, between **12:33 and 13:00 UTC**, our Payment Initiation Service and Account Information Service experienced a temporary disruption that prevented successful processing of payment initiation and account information requests from clients and partners. The incident has been fully resolved. **We sincerely apologize for the interruption and any impact this may have caused to your operations.**  ## Incident Overview |   |   | | --- | --- | | **Incident Date** | 10 Mar 2026 | | **Duration** | ~27 minutes \(12:30-13:00 UTC\) | | **Impact** | Temporary inability to process payment initiation and account information requests. | | **Current Status** | ✅ **Resolved**. Infrastructure restored and operating normally | ## What Happened The disruption was caused by an infrastructure-level configuration change required due to hardware-related issues affecting one of our network components. As a result of this change, the application layer temporarily lost the ability to establish database connections. This was not related to any client-side integration or API change.  ## Timeline \(UTC\) | Time | Event | | --- | --- | | 12:33 | Service disruption detected via monitoring alerts | | 12:34 | Engineering team engaged | | 12:45 | Corrective action applied | | 12:46 | First successful payment processed | | 13:00 | Services fully restored. | ## Root Cause The disruption was caused by an infrastructure-level configuration change required due to hardware-related issues affecting one of our network components. As a result of this change, the application layer temporarily lost the ability to establish database connections, leading to payment processing failures. This was not related to any client-side integration or API change. ## Resolution The issue was resolved by restarting affected application processes to ensure proper re-establishment of database connections following the infrastructure update. Normal payment processing resumed at **12:45 UTC**. The first successful payment after recovery was processed at **12:46 UTC**. ## Corrective & Preventive Measures We have initiated the following actions to prevent recurrence: 1. **Application-level resilience improvements** Enhancing database connection handling to better tolerate infrastructure changes. 2. **Additional validation checks** Implementing safeguards to ensure application awareness of infrastructure-level changes in real time. ## Contact If you have any questions about this incident or need assistance with affected transactions, please contact your account manager or reach out to our support team. We remain committed to providing reliable payment services and appreciate your continued partnership. _This report is intended for authorized partners only. Please do not distribute externally._

Feb 23, 2026 · resolved Feb 23

## Executive Summary On February 23, 2026, several OBG APIs experienced temporary unavailability due to infrastructure-level connection saturation. The incident lasted 24 minutes, during which API requests returned HTTP 500 errors. We sincerely apologize for any disruption this may have caused to your operations. The issue has been fully resolved, and preventive measures have been implemented. **We sincerely apologize for the interruption and any impact this may have caused to your operations.** ## Incident Overview | | | | --- | --- | | **Incident Date** | 23 Feb 2026 | | **Duration** | 24 minutes \(12:31-12:55 UTC\) | | **Impact** | Temporary API errors \(HTTP 500\) | | **Current Status** | ✅ Fully Resolved | ## What Happened Following a configuration change related to backend service connectivity, infrastructure connection limits were reached under production load. As a result: * New API requests could not establish required backend connections * Applications returned HTTP 500 responses * Service availability was temporarily degraded The issue was isolated to infrastructure connection handling and did not involve data corruption or data loss. ## Timeline \(UTC\) | Time | Event | | --- | --- | | 12:33 | Elevated API error rate detected | | 12:34 | Incident declared following monitoring alerts | | 12:50 | Root cause identified | | 12:54 | Immediate mitigation actions applied | | 12:55 | Services fully restored | ## Root Cause The incident was caused by connection saturation at the infrastructure layer following a backend configuration change. The existing connection handling limits were insufficient for the increased connection load introduced by the new architecture. This resulted in temporary rejection of new backend connections and API errors. ## Resolution To restore service, our engineering team: * Reverted the recent backend configuration change * Cleared saturated connection state * Increased infrastructure connection limits * Verified service stability under load Service was fully restored within 24 minutes. ## **Preventive Measures** We are implementing the following improvements: ✅ Increased infrastructure connection limits across relevant components 🔄 Implementing proactive monitoring and alerting for connection utilization 🔄 Reviewing connection handling configuration across services 📋 Introducing mandatory infrastructure capacity review prior to architectural changes ## Contact If you have any questions about this incident or need assistance with affected transactions, please contact your account manager or reach out to our support team. We remain committed to providing reliable payment services and appreciate your continued partnership. _This report is intended for authorized partners only. Please do not distribute externally._