Unavailability of the Payments API for Partners

Update timeline

1. investigating Mar 26, 2026, 12:09 PM UTC

   We are currently investigating an issue affecting Payments API for Partners. Customers may experience failed requests. The issue started at approximately 11:28 UTC, March 26th. Our engineering team is actively investigating the cause and working to restore normal operation as quickly as possible. Next update will be provided as soon as more information becomes available.

2. identified Mar 26, 2026, 01:42 PM UTC

   We have identified the cause of the issue affecting Payments API for Partners. At this time, customers may still experience failed requests. Our team is implementing mitigation measures to restore full functionality. We will continue to provide updates as progress is made.

3. resolved Mar 26, 2026, 02:14 PM UTC

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

4. postmortem Mar 30, 2026, 01:09 PM UTC

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