Lithic outage history

We’re seeing higher latency and intermittent errors on API requests.

A Visa network issue has delayed reconciliation for processing date 2026-10-11 - Some VISA clearings for settlement date 2026-10-11 are delayed - All Settlement API records are available and totals are accurate, however not all settlement records have a transaction token and event tokens - Affected transactions will not be present in the transactions API yet

The issue has been identified and a fix is being implemented.

Resolved. Delayed clearings have all been received and processed.

Beginning at approximately 11:23 UTC, requests to the Embedded Card UI endpoint (/v1/embed/card) are returning 403 errors.

We have mitigated the 403 errors in the API. We are continuing to monitor.

This incident has been resolved.

A Visa network issue has resulted in a subset of Visa clearings being delayed, which results in the Settlement API data not yet being complete for all customers. We are working with Visa on the delay.

This incident has been resolved.

Beginning at approximately 07:05 UTC on September 14, some API requests have experienced intermittent elevated latency and timeouts, returning HTTP 504 errors. Affected endpoints: • GET /v1/tokenizations • POST /v1/cards where a digital card art token is specified • POST /v1/cards/{card_token}/provision Impact occurs in short windows of roughly 10 to 20 minutes, recurring periodically. Requests outside these windows are completing normally. We have increased service capacity and connection limits, and we are continuing to monitor closely as volume fluctuates. Card authorizations and all other API endpoints are unaffected.

We are continuing to work on a fix for this issue.

A fix has been implemented and we are monitoring the situation.

This incident has been resolved.

Mastercard has declared an incident affecting the delivery of a subset of chargeback records. Settlement API summaries are not yet marked "complete", but all data is present except for a small subset of missing chargeback records. Partners who have delayed chargeback records have been notified.

This incident has been resolved.

We are seeing elevated 500 responses and increased latency on POST /v1/tokenizations/{tokenization_token}/deactivate for Mastercard tokenizations, beginning around 13:00 UTC. This is caused by a degradation in Mastercard's MDES Customer Service API. Mastercard has acknowledged the issue and is working on it.

This incident has been resolved.

Card authorization processing was partially degraded between 11:53 and 11:59 UTC. The issue has been resolved.

A Visa network issue has delayed reconciliation. - Settlement API data will be delayed - The issue is caused by the network - Customers who need settlement totals should use the network totals endpoint

- We've added all missing records to the Settlement API - The settlement API is still not complete because it is missing transaction tokens and event tokens because we have not yet received all clearings from Visa - The total amounts on the summary endpoint are correct and complete. - We'll add the missing data when its available

We are continuing to monitor for any further issues.

Resolved — Delayed Visa BASE II Clearings Aug 22, 19:03 UTC – Aug 23, 07:19 UTC We identified a delay in receiving Visa clearing messages, caused by an issue on Visa's network. This delayed processing of Visa settlement data in the Settlement API (SAPI) for transactions reported on Aug 22. Who was affected: Customers relying on SAPI for Visa recon on Aug 22 transactions. Other networks were not affected, and aggregate settlement totals (via the network totals endpoint) remained accurate throughout. What we did: We monitored as Visa worked through their backlog, and once it became clear the delay would extend past the normal processing window, we released available settlement data. Summary totals were correct and complete at all times. Individual settlement record details, however, were incomplete: they were missing transaction and event token references, since those references can only be attached once the corresponding clearing has been received from Visa and processed through the transaction API. As Visa's clearings continued to arrive, we backfilled the missing references until every record was complete. Resolution: As of 07:19 UTC on Aug 23, all missing Visa BASE II clearings have been received and processed. Settlement API data for Aug 22 is now complete and accurate.

Some customers are experiencing delays in receiving a subset of Mastercard clearing and dispute data. We are investigating the issue.

Mastercard processing issues have been identified, resolved, and backlog processing is complete. This incident is resolved.

Customers may experience elevated error rates and timeouts, including intermittent failures when provisioning cards and creating cards with dynamic card art or a qr code.

The issue has been identified and a fix is being implemented.

We are currently implementing a fix. Please note, this will cause 1-5 minutes of downtime.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Api partially degraded and timing out 9:55-10:10 UTC. Customers may have experienced elevated intermittent timeouts and errors.

We are investigating an issue that is causing a delay in clearing events from Mastercard.

Mastercard clearing files containing errors resulted in delayed processing of Mastercard clearings for 2026-06-02. As of 18:00 UTC all clearing events and associated Settlement API records were complete. Network Totals data was marked as complete at 19:25 UTZ.

Between 22:02–22:07 ET on May 13, authorization decisions were handled by card network stand-in processing rather than Lithic. Customers may have seen approvals or declines that differed from normal Lithic behavior during this window.

Visa is experiencing an incident affecting VisaNet Clearing and Settlement file delivery. This is causing delays in our Settlement Summary completion and Settlement API data. We are actively monitoring the situation and will update this page as we learn more.

This incident has been resolved.

We are currently investigating an issue causing increased latency in delivery of transaction webhooks for some customers. Authorization processing is unaffected.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are investigating an issue that is preventing cards from being added to digital wallets.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We experienced an issue with our sandbox environment where card authorizations were failing and API requests were returning unexpected errors. Our engineering team identified the root cause and restored service.

We are investigating an issue that may cause unexpected declines in cards that were created in the last 30 minutes.

We've identified the issue and are seeing improvements in behavior across the network.

This incident has been resolved.

Between 16:12 UTC and 16:21 UTC, some ACH transactions were unexpectedly declined. We are working to identify the root cause and scope of impact.

We have identified an issue that is causing unexpected declines on some programs and are currently investigating.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.