Pliant API Incident History

1. resolvedOct 7 · 11:30 UTC

   The issue has been resolved. The fix is live in production, and the affected API endpoints are returning the correct data. We have also completed the resend of affected PAYMENT_READY and PAYMENT_STATUS_CHANGED callbacks with the corrected data.

   The underlying transactions and payments themselves were not affected.

   Recommended actions:

   • Real-time API usage without storing data: No action is required. New API requests return the correct data.
   • Stored, cached, or periodically imported transaction data: We recommend re-fetching the transaction data to replace any potentially affected data.
   • Payment callbacks: No action is required. The affected callbacks have been re-sent with the corrected data.
   • Data already processed downstream: We recommend re-fetching the data from Pliant and reconciling downstream records against the corrected data.

   Please contact us if you need assistance with re-syncing or reconciliation.

   We apologize for the inconvenience caused.

Reported by Pliant API on their status page.

1. resolvedSep 5 · 06:30 UTC

   On September 5, between approximately 08:30 and 13:30 CEST, some CaaS/Pro API requests intermittently returned HTTP 403 responses across several endpoints, including transaction fetching. The issue was caused by a third-party provider supporting our permission layer. Requests failed closed: no unauthorized access was granted and no data was changed as a result of the incident. The provider deployed a fix on the same day, and the issue has not recurred. We have since added dedicated monitoring for this failure mode and significantly reduced load on the permission layer. Customers who experienced gaps in data retrieval during the affected period can re-fetch the affected data to bring their systems back in sync.

Reported by Pliant API on their status page.