Paytm status: access issues and outage reports

Problems in the last 24 hours in Tiruvalla, Kerala

The chart below shows the number of Paytm reports we have received in the last 24 hours from users in Tiruvalla, Kerala 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 20 seconds ago

  @Paytmcare I is really frustrated even after one week couldn't solve my problem

• 
  nik (@rhysnik) reported 27 seconds ago

  @Paytmcare My issue is purely technical: why did your app override my saved default bank account settings? I have shared all necessary transaction details previously.

• 
  Shailja Nandan Mishra (@mishra_sn1) reported 45 seconds ago

  @Paytmcare Your support is same as your application , still I have not getting any update

• 
  Kaustubha Kubal (@Kaustubha45) reported 6 minutes ago

  @creditcardwalah @Paytm @Visa Got it i think it's an glitch in app

• 
  divas dwivedi (@divas_dwivedi) reported 6 minutes ago

  @Paytmcare @PhonePe please help here.

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

  Since 1 month I have fcking uploaded pan, udhyam, 6 months statement, still ko account upgrade, then why the fk you agent came and installed the soundbox, that also with a limit of Rs 1? Are joking idiots @Paytm @Paytmcare @PaytmBusiness . If I can't accept payment why ********,

• 
  Urstrulysanni 🩷 (@urstrulysanni) reported 11 minutes ago

  Worst service @Paytm

• 
  Naresh Tiwari (@NareshTiwai) reported 13 minutes ago

  @Paytm @Paytmcare @PaytmCheckin I’m trying to book a bus ticket, but there’s no option to apply a coupon code during the booking process. I’m also facing an issue with the payment. Please look into this and help me resolve it so I can complete my booking. #Paytm

• 
  Jayveer Rajput (@JayveerUss80620) reported 19 minutes ago

  Hello sir @Paytm Pop up coming for Paytm postpaid limit increase but when I go to account section there is no update @Paytmcare help me

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