Oct <var data-var='date'> 2</var>, <var data-var='time'>17:48</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'> 2</var>, <var data-var='time'>16:35</var> UTC Monitoring - We have mitigated the 403 errors in the API. We are continuing to monitor. Oct <var data-var='date'> 2</var>, <var data-var='time'>11:23</var> UTC Investigating - Beginning at approximately 11:23 UTC, requests to the Embedded Card UI endpoint (/v1/embed/card) are returning 403 errors.

Elevated 403 Responses in Cards API

Sep <var data-var='date'>19</var>, <var data-var='time'>12:50</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>18</var>, <var data-var='time'>21:16</var> UTC Identified - 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.

Visa clearing delay

Sep <var data-var='date'>16</var>, <var data-var='time'>01:44</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>14</var>, <var data-var='time'>18:34</var> UTC Monitoring - A fix has been implemented and we are monitoring the situation. Sep <var data-var='date'>14</var>, <var data-var='time'>16:22</var> UTC Update - We are continuing to work on a fix for this issue. Sep <var data-var='date'>14</var>, <var data-var='time'>07:05</var> UTC Identified - 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.

Intermittent timeouts on Tokenization and Card Creation API endpoints

Sep <var data-var='date'>11</var>, <var data-var='time'>14:14</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>10</var>, <var data-var='time'>21:50</var> UTC Identified - 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.

Mastercard chargeback settlement data delay

Sep <var data-var='date'> 3</var>, <var data-var='time'>22:08</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'> 3</var>, <var data-var='time'>20:13</var> UTC Identified - 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.

Elevated errors and latency on tokenization deactivation

Aug <var data-var='date'>26</var>, <var data-var='time'>12:26</var> UTC Resolved - Card authorization processing was partially degraded between 11:53 and 11:59 UTC. The issue has been resolved.

Card authorization processing partially degraded

Aug <var data-var='date'>23</var>, <var data-var='time'>07:19</var> UTC Resolved - 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. Aug <var data-var='date'>23</var>, <var data-var='time'>03:05</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>23</var>, <var data-var='time'>03:04</var> UTC Monitoring - - 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 Aug <var data-var='date'>22</var>, <var data-var='time'>19:31</var> UTC Identified - 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

Visa Recon Delay

Jul <var data-var='date'> 3</var>, <var data-var='time'>23:43</var> UTC Resolved - Mastercard processing issues have been identified, resolved, and backlog processing is complete. This incident is resolved. Jul <var data-var='date'> 3</var>, <var data-var='time'>22:10</var> UTC Investigating - Some customers are experiencing delays in receiving a subset of Mastercard clearing and dispute data. We are investigating the issue.

Delays in Mastercard clearing and dispute data

Jun <var data-var='date'>15</var>, <var data-var='time'>20:34</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>15</var>, <var data-var='time'>19:13</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>15</var>, <var data-var='time'>18:38</var> UTC Update - We are currently implementing a fix. Please note, this will cause 1-5 minutes of downtime. Jun <var data-var='date'>15</var>, <var data-var='time'>16:15</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>15</var>, <var data-var='time'>15:15</var> UTC Investigating - 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.

Intermittent API Timeouts

Jun <var data-var='date'> 6</var>, <var data-var='time'>04:00</var> UTC Resolved - Api partially degraded and timing out 9:55-10:10 UTC. Customers may have experienced elevated intermittent timeouts and errors.

API Partial Degredation

Jun <var data-var='date'> 2</var>, <var data-var='time'>19:30</var> UTC Resolved - 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. Jun <var data-var='date'> 2</var>, <var data-var='time'>17:49</var> UTC Monitoring - We are investigating an issue that is causing a delay in clearing events from Mastercard.

Delays in clearing events

May <var data-var='date'>14</var>, <var data-var='time'>02:00</var> UTC Resolved - 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.

Card Network Connectivity Disruption

May <var data-var='date'> 1</var>, <var data-var='time'>23:41</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 1</var>, <var data-var='time'>21:23</var> UTC Identified - 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.

Delay in Settlement Reporting

Apr <var data-var='date'>22</var>, <var data-var='time'>17:54</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>22</var>, <var data-var='time'>16:52</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>22</var>, <var data-var='time'>16:45</var> UTC Investigating - We are currently investigating an issue causing increased latency in delivery of transaction webhooks for some customers. Authorization processing is unaffected.

Transaction webhooks delayed for a subset of customers

Apr <var data-var='date'>22</var>, <var data-var='time'>15:58</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>22</var>, <var data-var='time'>15:34</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>22</var>, <var data-var='time'>15:30</var> UTC Identified - The issue has been identified and a fix is being implemented. Apr <var data-var='date'>22</var>, <var data-var='time'>14:11</var> UTC Investigating - We are investigating an issue that is preventing cards from being added to digital wallets.

Digital Wallet Tokenization

Apr <var data-var='date'> 7</var>, <var data-var='time'>12:00</var> UTC 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.

Sandbox Environment Degradation

Apr <var data-var='date'> 2</var>, <var data-var='time'>02:08</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'> 2</var>, <var data-var='time'>01:49</var> UTC Identified - We've identified the issue and are seeing improvements in behavior across the network. Apr <var data-var='date'> 2</var>, <var data-var='time'>01:33</var> UTC Investigating - We are investigating an issue that may cause unexpected declines in cards that were created in the last 30 minutes.

Delays with newly created cards

Feb <var data-var='date'>25</var>, <var data-var='time'>12:00</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>25</var>, <var data-var='time'>11:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>24</var>, <var data-var='time'>01:46</var> UTC Scheduled - We will be performing infrastructure updates to improve the performance and reliability of our tokenization and digital wallet services. This work will require a brief maintenance window of approximately 25 minutes between 6:00AM – 7:00 AM ET. What to expect during this time: - Cardholders will not be able to add cards to digital wallets - Merchant tokenization requests will be declined - Card create requests that include a digital_card_art_token will be rejected We've scheduled this during an early-morning, low-traffic window to minimize any impact to your operations. Our team will be actively monitoring throughout and will confirm once maintenance is complete.

Tokenization & Digital Wallet Services Maintenance — Feb 25

Feb <var data-var='date'>24</var>, <var data-var='time'>18:59</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>24</var>, <var data-var='time'>17:17</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'>24</var>, <var data-var='time'>17:06</var> UTC Investigating - We have identified an issue that is causing unexpected declines on some programs and are currently investigating. Feb <var data-var='date'>24</var>, <var data-var='time'>16:30</var> UTC Monitoring - 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.

Unexpected declines

Feb <var data-var='date'>22</var>, <var data-var='time'>18:11</var> UTC Resolved - We observed elevated response errors from our public API between 16:18 UTC and 16:38 UTC. The issue has since been resolved. Transaction processing was not affected.

Elevated errors from API

Feb <var data-var='date'>17</var>, <var data-var='time'>17:58</var> UTC Resolved - We detected an issue that caused unexpected declines on cards that were created between 2026-02-17 17:05 UTC and 2026-02-17 17:53 UTC. The issue has been since resolved, and cards created during that time can now transact as expected. Feb <var data-var='date'>17</var>, <var data-var='time'>17:49</var> UTC Investigating - We are currently experiencing an issue causing unexpected declines on some newly created cards. Our team is actively investigating. We will provide updates as more information becomes available.

Unexpected declines for newly created cards

Feb <var data-var='date'> 4</var>, <var data-var='time'>19:04</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'> 4</var>, <var data-var='time'>19:02</var> UTC Investigating - We detected an issue that caused unexpected declines on cards that were created between 2026-02-04 17:48 UTC and 2026-02-04 18:37 UTC. The issue has been since resolved, and cards created during that time can now transact as expected.

Dec <var data-var='date'>16</var>, <var data-var='time'>20:42</var> UTC Resolved - Cards created between 2025-12-16 20:05 and 20:25 were unable to transact until this was resolved at 20:25 UTC.

Cards created between 20:05 and 20:25 UTC lag in processing

Nov <var data-var='date'>25</var>, <var data-var='time'>00:00</var> UTC Resolved - A change deployed on our end caused tokenizations to be declined between 2025-11-25 00:15:00 and 2025-11-25 02:19:00 UTC. The issue has since been fully resolved, and tokenization behavior has returned to normal.

Notice: Tokenization Declines Occurred Nov 25 -Issue Resolved

Nov <var data-var='date'>11</var>, <var data-var='time'>06:38</var> UTC Resolved - Working with our network partners, we have resolved an issue that was affecting a portion of MasterCard authorizations for one specific issuer. Normal processing has resumed Nov <var data-var='date'>11</var>, <var data-var='time'>06:28</var> UTC Monitoring - A fix has been deployed and we are seeing improvement in authorizations across the network. Nov <var data-var='date'>11</var>, <var data-var='time'>04:03</var> UTC Update - We apologize for the delay. We can confirm that a fix will be implemented soon and will provide an ETA once we receive confirmation from our network partners. Nov <var data-var='date'>11</var>, <var data-var='time'>01:57</var> UTC Identified - We have identified the issue causing unexpected declines on authorizations and are actively working with our network partners to implement a resolution. Nov <var data-var='date'>11</var>, <var data-var='time'>01:09</var> UTC Update - We are continuing to investigate unexpected declines and are working with our network partners on a resolution. Nov <var data-var='date'>11</var>, <var data-var='time'>00:47</var> UTC Investigating - We are currently investigating an issue that may be causing unexpected declines on MasterCard authorizations.

Is Lithic down?

Lithic status is UP

Lastest published events

Elevated 403 Responses in Cards API

Visa clearing delay

Intermittent timeouts on Tokenization and Card Creation API endpoints

Lithic Services, Components and Regions

Recent Lithic events

Elevated 403 Responses in Cards API

Visa clearing delay

Intermittent timeouts on Tokenization and Card Creation API endpoints

Mastercard chargeback settlement data delay

Elevated errors and latency on tokenization deactivation

Card authorization processing partially degraded