Paytm status: access issues and outage reports

Problems in the last 24 hours in Manchar, Maharashtra

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

• 
  nik (@rhysnik) reported 3 minutes ago

  @Paytm @Paytmcare Your in-app support team is giving robotic, copy-pasted replies without explaining how my default setting was overridden. This is a severe software routing failure and a breach of user payment security.

• 
  Happiefy (@happiefy) reported 3 minutes ago

  @Paytm @Paytmcare booked bus from Delhi to prayagraj today bus driver phone was off operator Didnt pick up costumer care didn’t respond my family was waiting there for hours no response pathetic service need urgent action and compensation Paytm Booking ID*: 27456038637 File case

• 
  Guru_K (@GuruyuganK) reported 4 minutes ago

  Building Tab for #BuildForIndia — AI for India's small shop owners. It scores customer trust for informal credit from real UPI payment history (unlike existing khata apps), plus cash-flow safety checks — spoken in the owner's language. @Paytm @SarvamAI @Hack_Culture

• 
  BSES Delhi (@bsesdelhi) reported 5 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.

• 
  Ankit Barnwal🇮🇳 (@MrAnkit26599) reported 13 minutes ago

  What's your new excuse despite providing all the details @Paytmcare Accept your negligence, Your technician is not willing to work, your team is not willing to work. Why you guys don't shut down your services.

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

• 
  Anusha (अनुशा) (@anushabansal14) reported 14 minutes ago

  @Paytmcare Waited 5 days already, when can I expect you to contact me? Kindly HELP

• 
  Justin Army (@JustnbieberIND) reported 14 minutes ago

  @Paytmcare The customer has left shop after he showed us that the payment has been completed. What should I do? Did I lose the amount?

• 
  Vispy Ichhaporia (@vispyi) reported 18 minutes ago

  What a useless company @Paytm is. Their @Paytmcare customer support is worst. Will take all the details and won’t respond till 36 hours. Bhai company band kardo agar chala nahi sakte to.

• 
  Prudvi_Bob ©️ (@PrudviVysyaraj) reported 19 minutes ago

  @Paytm @Paytmcare @SuryodayBank Paid ₹9,000 in full on 30 July & requested closure. Yet ₹180 Convenience Fee + ₹32.40 IGST was charged,and ₹212.40 was auto-debited on 3 Aug. Multiple emails to Suryoday Bank,but no acknowledgment or response.Why is customer grievance ignored?