Paytm status: access issues and outage reports

Problems in the last 24 hours in Lāmba Jātān, Rajasthan

The chart below shows the number of Paytm reports we have received in the last 24 hours from users in Lāmba Jātān, Rajasthan 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 Lāmba Jātān, Rajasthan

Latest outage, problems and issue reports in Lāmba Jātān and nearby locations:

• 
  UDAY SINGH MEENA (@udaymeena99) reported 39 minutes ago from Lāmba Jātān, Rajasthan

  @Paytmcare @Paytm My kyc Is upgrad , but not upgraded, please help me My kyc upgrade

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Abhishek Bakshi (@asolitudeseeker) reported 4 minutes ago

  @Paytmcare trying to connect to your customer care since a while without any luck. Kindly get in touch. Thank you.

• 
  Rajat Agrawal (@MoneyElevat) reported 6 minutes ago

  @Paytm @Paytmcare is a total scam I cancelled gold SIP on PayTM but it is not cancelling it Their customer care doesn't exist, and chatbot is designed to never solve a query They don't let you even delete your bank account; never doing business with them again #scam #fraud

• 
  Syed Muzaffar (@SyedMuz31229099) reported 8 minutes ago

  @Paytmcare @vijayshekhar please don't waste ur time if u're really tracing the error. I accidentally reinstalled the app and it worked. Once again, thanks for taking soooooo long for doing nothing.👎

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

  Hey @PaytmCare, your service is shameful! You hide 'single-use' terms on flight vouchers to rob users. You stole my ₹2,281 and your agents shamelessly closed my ticket (200012349631) without resolution. This is outright fraud! Stop scamming and refund my money! #PaytmFraud

• 
  Reddy (@iam_Rah12627) reported 12 minutes ago

  @Paytmcare 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..

• 
  Rohit Singh (@Singhrohit9956) reported 15 minutes ago

  @Paytmcare @vijayshekhar it's very wrost service I raised issue couple of days didn't respond properly i paid assurance amount 580 somthing where is my travel voucher it's really disgusting service no one respond properly

• 
  kajal jain (@kajaljain77) reported 23 minutes ago

  Is there a problem or technical glitch happening today for all ?? @Paytm @Paytmcare

• 
  Sumit Bahadur 🇮🇳 (@sumit316bahadur) reported 26 minutes ago

  @Paytm my paytm not working since yesterday.. 9798587330

• 
  Ravi Mangnani (@sanjuravi) reported 27 minutes ago

  @Paytmcare Finally I m uninstalling paytm and switch to next options unhappy from service

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