Paytm status: access issues and outage reports

Problems in the last 24 hours in Solan, Himachal Pradesh

The chart below shows the number of Paytm reports we have received in the last 24 hours from users in Solan, Himachal Pradesh 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

Latest outage, problems and issue reports in social media:

• 
  Sharath B (@Sharath85852559) reported 2 minutes ago

  @Paytmcare I wanted to know what is the issue. Why I am facing this issue

• 
  Sanju Bai Bairwa (@SANJUBAIBAIRWA) reported 6 minutes ago

  Hey @PaytmCare,your team refused my refund for ticket 200012349631.I lost ₹2,281 from my flight voucher due to missing single-use warnings on the app screen.Since internal support denied it, I am escalating this matter to the National Consumer Helpline (NCH).Please resolve this.

• 
  Subhransu Sekhar Dutta 🇮🇳 (@The_Subhransu) reported 7 minutes ago

  @Paytm @Paytmcare @PaytmBusiness I will not activate or accept any rental/subscription charges for a device I cannot use. Clarify immediately why it was dispatched and confirm that no charges will be imposed without my consent. Resolve my account limit issue or take the Soundbox back at no cost.

• 
  Sharath B (@Sharath85852559) reported 9 minutes ago

  @Paytmcare Still showing the errors

• 
  Manik Nayyar🇮🇳 (@maniknayyar1) reported 10 minutes ago

  🚨IMP! Pls don't book train tickets from @Paytm as the app debits linked accounts without even entering a UPI PIN. I was just checking train ticket on paytm app and it asked me to login to IRCTC, which I didn't but my account was debited without login & UPI PIN @Paytmcare

• 
  Jai BOB (@MB_One8) reported 10 minutes ago

  @Paytmcare Is any help I'm get? R u gng to compensate for the very very bad experience caused by u r app? @Paytmcare

• 
  Chinmaya (@ChinmayaSaxena) reported 11 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. 🙏

• 
  Suresh Kumar Kurapaty (@kurafatygyan) reported 12 minutes ago

  @Paytmcare Can you help me with Paytm wallet ??

• 
  Wasim (@wasim_sayy) reported 14 minutes ago

  @Paytmcare @PaytmBusiness A ticket should not be marked “resolved” when the customer's issue is still pending. Please reopen and escalate my complaint to the senior grievance team and permanently close my merchant account as requested. Ticket ID: [500011909287] 2/3

• 
  VoiceOfChange_Anu (@Sainianu22) reported 15 minutes ago

  @Paytmcare No data found of health insurance on Adiya Birla Website.