标志性停用误差和延迟性
Issues轻微事件
受影响的组件
API
- identified
在协调世界时11:00左右开始,我们看到500个答复得到提升,POST/v1/tokenizations/{tokenization token}/取消Mastercard标志化的功能。 这是由于Mastercard的MDES客户服务API的退化造成的. Mastercard承认了这个问题,并正在研究这个问题.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
53 Lithic incidents · 2024年7月 — official updates, affected components, duration and resolution details.
在协调世界时11:00左右开始,我们看到500个答复得到提升,POST/v1/tokenizations/{tokenization token}/取消Mastercard标志化的功能。 这是由于Mastercard的MDES客户服务API的退化造成的. Mastercard承认了这个问题,并正在研究这个问题.
这一事件已经得到解决.
自动翻译自官方事件更新。
卡片授权处理在协调世界时11:53至11:59之间被部分降解. 这个问题已经得到解决.
自动翻译自官方事件更新。
签证网络问题拖延了核对。 - 结算 API 数据将延迟 - 问题是网络造成的 - 需要结算的客户总数应使用网络总数
- 我们把所有缺失的记录都加进了API - API仍未完成结算,因为它是缺少交易符和事件符,因为我们尚未收到Visa的所有结算 - 总终点的总额正确而完整。 - 如果有数据的话,我们会添加缺失的数据
我们正在继续监测任何其他问题.
解决——延迟签证 BASE II 8月22日, 19:03 UTC – Aug 23, 07:19 UTC 我们发现,由于签证网络上出现一个问题,签证审批信息被延迟。 这延误了对8月22日报告的交易的结算API(SAPI)中签证结算数据的处理。 受影响者:客户依靠SAPI对8月22日的交易进行签证侦察。 其他网络没有受到影响,总定居总数(通过网络总终点)在整个过程中仍然准确。 我们所做的:我们监测Visa的积压工作,一旦发现拖延会延续到正常的处理窗口,我们就公布了现有的结算数据。 汇总总数始终正确而完整。 然而,个别结算记录细节不完整:它们缺少交易和事件符号参考,因为只有在从Visa收到相应的结算并通过交易API处理后才能附上这些参考。 随着Visa的许可继续到来,我们回填了缺失的参考文献,直到所有记录完成. 决议:截至协调世界时8月23日07:19起,所有缺失的Visa BASE II许可均已收到并处理完毕. Aug 22的结算API数据现已完整而准确.
自动翻译自官方事件更新。
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