Paytm status: access issues and outage reports

Problems in the last 24 hours in Dharmanagar, Tripura

The chart below shows the number of Paytm reports we have received in the last 24 hours from users in Dharmanagar, Tripura and surrounding areas. An outage is declared when the number of reports exceeds the baseline, represented by the red line.

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Paytm Issues Reports Near Dharmanagar, Tripura

Latest outage, problems and issue reports in Dharmanagar and nearby locations:

• 
  sanjib paul (@06Sanjibpaul) reported 50 minutes ago from Dharmanagar, Tripura

  Spicemoney instant load money to wallet byyesbank not working. Qr code payment acept problem. They R ignore Adikari Feedback. @SonuSood @SonuSoodSena @Paytm

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Sachin Kumar Jha - सचिन कुमार झा (@iSachinJha) reported 5 minutes ago

  @PaytmBusiness @Paytmcare I’ve already provided all requested details via DM, but there’s still no resolution. These FY 2022-23 GST invoices are urgently required for my GST notice response. “We are working on it” is not enough anymore.

• 
  jay agrawal (@jayagra19648773) reported 7 minutes ago

  I want to know about my paytm soud box I want to close permanently but there is a problem with customer support they are charging me lots of charges to activate plz help me @Paytmcare

• 
  Reddy (@iam_Rah12627) reported 11 minutes ago

  @Paytmcare @Paytm @PaytmTravelCare I'm stuck in other country and booked a flight from your platform when I got a ticket and checked with the airline , they have informed the reference number is invalid and I cannot even contact you what a pathetic support you have given..

• 
  dharmpal garhwal (@dpalgarhwal) reported 14 minutes ago

  @Paytmcare No body is replying after reminding the suggestion given by customer support and today is last date of paying my emi @Paytmcare @Paytm

• 
  I C johari (@IJohari46498) reported 16 minutes ago

  @Paytmcare Really So poor service please check your Inbox I'm sending private message sending all detail final option I'm going on police or Coust

• 
  Sharath B (@Sharath85852559) reported 23 minutes ago

  @Paytmcare It is been three days. But no solution. What is issue could you pls confirm

• 
  kushal das (@kushal8609) reported 24 minutes ago

  @Paytmcare Still problem not resolved.

• 
  Abhi$hek Hindustani (@BrownBoi07) reported 24 minutes ago

  @Paytmcare No further assistance required and I'll make sure to not use your service anymore thanks

• 
  Chinmaya (@ChinmayaSaxena) reported 25 minutes ago

  @Paytm Data leak risks worth considering if not considered and addressed already. Maybe good for the @Paytm team to share how these are addressed. This is again in our long term interest as a nation. Quoted directly from Claude response (disclaimer- Not my personal views, please validate) 1. Prompt injection via tool outputs. Transaction descriptions, customer names, order notes — any field an end-customer can populate — becomes untrusted text once it flows through the MCP tool result into Claude's context. A malicious "customer" could put an injection payload in a payment note field, hoping it gets executed when a merchant later asks Claude to "summarize today's transactions." 2. Over-broad OAuth scopes. If the merchant's connected token grants read access to all transactions rather than scoped by team/role, any employee with Claude access effectively gets visibility into full settlement and customer data, bypassing whatever RBAC existed on the Paytm dashboard. 3. Context leakage across conversations/sessions. If the same Claude account is used for other tasks, payment data pulled into context in one thread could plausibly resurface via memory/summarization features if not carefully scoped — worth checking how PPSL scopes token lifetime and whether Claude retains tool outputs beyond the session. 4. Third-party model exposure. Payment data (PII: names, phone numbers, partial card/bank details, amounts) now transits through Anthropic's infrastructure as tool-call payloads, even if not used for training. That's a new data-residency and compliance surface — relevant for RBI data localization rules and PCI-DSS scope creep. 5. Credential/session hijacking. MCP connector auth tokens, if long-lived, become a single high-value target — compromise of the Claude account (weak password, no 2FA, shared device) could give an attacker read access to a merchant's entire payment history. 6. No mention of masking. The post doesn't say whether sensitive fields (card BINs, UPI VPAs, customer PII) are redacted/tokenized before reaching the LLM context — a real gap for a blog post about a payments integration. 🙏

• 
  CA Sridhar (@SRIDHAR00772301) reported 28 minutes ago

  @Paytmcare @Paytm pls help