Paytm status: access issues and outage reports

Problems in the last 24 hours in West Tripura, Tripura

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

Latest outage, problems and issue reports in social media:

• 
  Gautam Bhatia (@1gautambhatia) reported 6 minutes ago

  @Paytmcare help

• 
  Vinod Radheshyam Singh (@VinodRadheshyam) reported 9 minutes ago

  @Paytmcare Hopeless paytm service My self unable 2 login desktop cheating 2 Customers

• 
  Illustrated Daily News (@I_DailyNews) reported 9 minutes ago

  @PaytmCheckin has simply abandoned no customer care number only non responsive bots. NEVER BOOK A FLIGHT TICKET VIA @Paytm

• 
  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. 🙏

• 
  Chintan (@ChintanSisyphus) reported 11 minutes ago

  @Paytmcare You guys should get a award for the horrible customer care and harassment you guys do !!! I booked a flight ticket yesterday from the app and since then I am not able to do web check-in..there is customer care number, no response to 5 complaints I made on the app

• 
  tushar (@emailtj) reported 15 minutes ago

  @Paytm totally pathetic from paytm instead of solving issue with my merchant account they simply chose to deactivate it cant trust paytm anymore beware

• 
  Vidyut Pal (@the_viddy) reported 16 minutes ago

  @Paytm @BSNLCorporate I recharged a BSNL number with PAYTM, it's a BSNL number. It got into pending... Now it's almost 5th day no information and no refund and nothing. Disgusting service....

• 
  Rohit Kumar (@RohitKu73338260) reported 17 minutes ago

  @Paytmcare Hey Paytm I already connect with you previously with the same issue but still I am not getting any kind of resolution so can you please do something faster

• 
  Anisha 🏳️‍🌈 (@shutupanisha) reported 19 minutes ago

  @Paytmcare Okay I will check back in 48 hours. This is really horrible customer service I must say.

• 
  tenminutes (@TenMinuteSW) reported 19 minutes ago

  Hi @Paytm can you pls help me resolve this" device environment is not correct " bug?