53 Lithic incidents · Temmuz 2024 — official updates, affected components, duration and resolution details.
500 yanıt görüyoruz ve POST /v1/tokenizations/{tokenization token}/deactivate for the tokenizations, beginning around 13:00 UTC. Bu, Mastercard'ın MDES Müşteri Hizmetleri API'sinde bir bozulmadan kaynaklanıyor. Mastercard sorunu kabul etti ve üzerinde çalışıyor.
Bu olay çözüldü.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Kart yetkilendirme işlemi 11:53 ve 11:59 UTC arasında kısmen bozuldu. Sorun çözüldü.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Vize ağı konusu uzlaşmayı geciktirdi. - Çözüm API verileri gecikecek - Sorun ağ tarafından kaynaklanır - Toplam yerleşmeye ihtiyaç duyan müşteriler ağı toplam uç noktası kullanmalıdır
- Tüm eksik kayıtları Çözüm API'sine ekledik - Yerleşim API'si hala tamamlanmamıştır çünkü eksik işlem jetonları ve etkinlik jetleri çünkü henüz Visa'dan gelen tüm netlemeleri almadık - Özet uç noktadaki toplam miktarlar doğru ve tamamlanmış. - Mevcut olduğunda eksik verileri ekleyeceğiz
Daha fazla sorun için izlemeye devam ediyoruz.
Çözüldü - Vize BASE II Gümrüklemeleri Ağustos 22, 19:03 UTC - 23 Ağustos 07:19 UTC Vize net mesajları almada gecikme tespit ettik, Visa'nın ağı üzerinde bir sorun nedeniyle. Bu, 22 Ağustos'ta yayınlanan işlemler için Çözüm API'sinde vize yerleşim verilerini geciktirdi. Kim etkilendi: SAPI'ya güvenen müşteriler 22 Ağustos'ta yeniden rezervasyon yaptılar. Diğer ağlar etkilenmedi ve toplam yerleşim toplamları (tüm ağ toplam uç noktası) sürekli kaldı. Ne yaptık: Vize gerilogları aracılığıyla çalışırken izlendik ve bir kez gecikmenin normal işlem penceresini uzatacağını açıkladık, mevcut yerleşim verilerini serbest bıraktık. Özet toplamlar doğruydu ve her zaman tamamlandı. Bununla birlikte, bireysel yerleşim kayıt ayrıntıları eksikti: eksik işlem ve etkinlik token referansları vardı, çünkü bu referanslar sadece vizeden alındı ve işlem API aracılığıyla işlendi. Visa'nın netlemeleri gelmeye devam ettikçe, her kayıt tamamlanmış olana kadar eksik referansları geri aldık. Karar: 23 Ağustos'ta 07:19 UTC olarak, tüm eksik Visa BASE II netlemeler alındı ve işlendi. 22 Ağustos için çözüm API verileri şimdi tamamen ve doğru.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
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.
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.
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.
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.
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.
This incident has been resolved.
Cards created between 2025-12-16 20:05 and 20:25 were unable to transact until this was resolved at 20:25 UTC.
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.
We are currently investigating an issue that may be causing unexpected declines on MasterCard authorizations.
We are continuing to investigate unexpected declines and are working with our network partners on a resolution.
We have identified the issue causing unexpected declines on authorizations and are actively working with our network partners to implement a resolution.
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.
A fix has been deployed and we are seeing improvement in authorizations across the network.
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