Is Pliant API down?

We have identified an issue affecting our transaction endpoint and payment callbacks, which may cause incorrect transaction data to be returned and could impact reconciliation. We are treating this issue with high priority and are actively working on a fix. We will provide an update as soon as the issue has been resolved and the endpoint is returning the correct data. Once resolved, we will also re-send affected callbacks to ensure that the correct transaction data is received. We apologize for the inconvenience and will keep you informed of our progress.

Update: We have identified the affected endpoints and callbacks and are deploying a fix as soon as possible. The following are currently impacted: * GET /api/transactions * May return duplicate transactions * GET /api/transactions/{transactionId} * POST /api/transactions/details * May return incorrect paymentReference and paymentDate * GET /api/payments/{paymentId} * May return incorrect relatedTransactions * PAYMENT_STATUS_CHANGED and PAYOUT_* callbacks * May contain incorrect relatedTransactions * Manual callback resends are affected as well We are treating this with high priority and will provide another update once the fix has been deployed and we have confirmed that the affected endpoints and callbacks are returning the correct data.

A fix has been deployed and the affected API endpoints and callbacks are now returning the correct data. The issue affected the association between transactions and payments in organizations with multiple card accounts. This could result in duplicate transactions being returned, incorrect paymentReference or paymentDate values, or incorrect relatedTransactions in payment data and callbacks. The underlying transactions and payments themselves were not affected. We will share guidance on recommended actions and ways to mitigate the impact in an upcoming update within the next few minutes. We continue to monitor the fix and will provide a final update once the callback resends have been completed.

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.

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.