Looking for an update now? Check the current status, or follow Pliant for future changes.
98.8%of 83 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
October 2026
96.8%
31
1
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Aug 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
Incorrect Transaction Data in API and Payment Callbacks
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.
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.
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.
Legacy Incident Archive
4 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
Documentation currently not available
Source not attested
Last archived state: resolved
View archived record details
identified
API documentation is currently not available, our third-party provider is working on a fix.
April 2026
Investigating issues in Sandbox Environment
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently experiencing issues with our sandbox environment that began yesterday. Our team is actively working on identifying and resolving the root cause.
We’ll provide further updates as soon as we have more information. Thank you for your patience.
API Authentication Issues
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A third-party provider has deployed a fix for the issue affecting API authentication and is currently monitoring the situation.
API consumers should now be able to generate bearer tokens again. We are continuing to monitor closely to ensure the issue is fully resolved.
We will provide a final update once stability has been confirmed.
investigating
We are currently investigating an issue affecting API authentication.
API consumers may be unable to generate bearer tokens via Auth0, which can result in failed or unauthorized API requests.
Our team is actively investigating the root cause and monitoring the situation closely.
We will share further updates as soon as more information is available.
Card Issuance is not possible
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
Monitoring: The latest fix has resolved the issue with card issuance.
We are continuing to monitor the system to ensure stability and will provide a final update once we confirm everything is fully operational.
Please note that the sandbox environment is currently still experiencing issues, and our team is actively working to fix the issues there as well.
identified
Update: The previously deployed fix did not resolve the issue with card issuance.
Our team is actively working on an alternative solution and continuing to investigate. We will provide further updates as progress is made.
identified
A hotfix is currently being deployed to resolve the problem. We will share another update once the fix has been fully rolled out.
