Current answer
Pliant experienced a major incident: Incorrect Transaction Data in API and Payment Callbacks. ServiceAlert observed recovery on Oct 7, 2026.
Looking for an update now? Check the current status, or follow Pliant for future changes.
Incident Lifecycle
Affected Components
Pliant CaaS API
Pliant Pro API
Incident Timeline
Monitoring
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 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.
Oct 7, 2026 at 10:59 AM UTC
Identified
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.
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.
Oct 7, 2026 at 10:12 AM UTC
Identified
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.
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.
Oct 7, 2026 at 8:45 AM UTC
Was your business affected by this Pliant outage?
Follow Pliant and route available status alerts to email or a team channel.