<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.taxtmi.com/rss_sitemap/rss_feed_blog.xsl?v=1750492856"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>People face trouble making online payments using UPI; NPCI blames it on banks</title>
    <link>https://www.taxtmi.com/news?id=51888</link>
    <description>The NPCI reported intermittent UPI connectivity failures caused by internal technical problems at several banks while its own systems remained functional; it coordinated with lenders to restore service. The outage, which generated widespread user complaints, highlights operational dependence of the central platform on participant banks and raises questions about allocation of responsibility and costs given the platform is government-subsidised to promote digital payments.</description>
    <language>en-us</language>
    <pubDate>Thu, 07 Aug 2025 22:16:03 +0530</pubDate>
    <lastBuildDate>Thu, 07 Aug 2025 22:16:03 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=841728" rel="self" type="application/rss+xml"/>
    <item>
      <title>People face trouble making online payments using UPI; NPCI blames it on banks</title>
      <link>https://www.taxtmi.com/news?id=51888</link>
      <description>The NPCI reported intermittent UPI connectivity failures caused by internal technical problems at several banks while its own systems remained functional; it coordinated with lenders to restore service. The outage, which generated widespread user complaints, highlights operational dependence of the central platform on participant banks and raises questions about allocation of responsibility and costs given the platform is government-subsidised to promote digital payments.</description>
      <category>News</category>
      <law>-</law>
      <pubDate>Thu, 07 Aug 2025 22:16:03 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/news?id=51888</guid>
    </item>
  </channel>
</rss>