Paytm status: access issues and outage reports

Problems in the last 24 hours in Dharapuram, Tamil Nadu

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

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

  Hey @PaytmCare, my support ticket (200012349631) was closed by your team without a refund. I accidentally redeemed just ₹100 from my ₹2,381 flight voucher due to a lack of single-use warnings. As a regular user, I request a goodwill refund of my remaining balance. Please help🙏

• 
  BSES Delhi (@bsesdelhi) reported 10 minutes ago

  @lunnac758576 @Paytm @Paytmcare Dear Consumer, We've been updated that the online payment made takes 3-5 working days to reflect in our records. Kindly check after the given time.

• 
  Surjeet Singh (@asksurjeet) reported 13 minutes ago

  1/1 @Paytmcare I’m unable to log in because the OTP is not being received on my registered mobile number. The number is active and working properly on my phone, yet I’ve been facing this issue since yesterday. I’m also seeing a “Daily verification limit reached” message, even though the OTP itself isn’t arriving. Please look into this urgently and help me regain access to my account. #Paytm #OTPIssue

• 
  Surjeet Singh (@asksurjeet) reported 15 minutes ago

  @Paytmcare 1/5 @Paytmcare What is happening in your system? I’ve been trying to complete device verification for the last 3 days but keep getting “Verification couldn’t be completed – We didn’t receive the verification SMS”. I already have an unlimited recharge pack + extra top-up balance on my number. Still not able to login. Please resolve this urgently. You can also attach the screenshot of the error when you post it.

• 
  Surjeet Singh (@asksurjeet) reported 17 minutes ago

  1/5 @Paytmcare What is happening in your system? I’ve been trying to complete device verification for the last 3 days but keep getting “Verification couldn’t be completed – We didn’t receive the verification SMS”. I already have an unlimited recharge pack + extra top-up balance on my number. Still not able to login. Please resolve this urgently.

• 
  srijan singh tomer (@1989Srijan) reported 18 minutes ago

  @HeroFinCorpLtd @Paytm I amnot getting my loan amount still showing proceeding every thing is ok no customer care no response.

• 
  nik (@rhysnik) reported 18 minutes ago

  @Paytmcare Please stop asking for callbacks and provide a formal, technical explanation regarding this routing glitch in writing here. I am looking for a definitive, positive resolution and compensation for the mental harassment caused by this service deficiency, not more calls.

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

• 
  Arjun (@TheDesiBoyy) reported 24 minutes ago

  @Paytmcare @Paytm my Paytm scanner works slow, kindly help me. I have uninstall it and install it again but still same issue.

• 
  nik (@rhysnik) reported 26 minutes ago

  @Paytm @Paytmcare I demand an explanation from your technical team immediately. Fix your app bugs and address this account security lapse now! RMN: 8828286369