Paytm status: access issues and outage reports

Problems in the last 24 hours in Shikohābād, Uttar Pradesh

The chart below shows the number of Paytm reports we have received in the last 24 hours from users in Shikohābād, Uttar Pradesh 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 Shikohābād, Uttar Pradesh

Latest outage, problems and issue reports in Shikohābād and nearby locations:

• 
  MANISH BAGHEL (@BghelManish) reported 52 minutes ago from Shikohābād, Uttar Pradesh

  Is paytm down? I am not able to do transaction ? @Paytm @Paytmcare @PaytmBank

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  nik (@rhysnik) reported 7 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.

• 
  Wasim (@wasim_sayy) reported 9 minutes ago

  @Paytmcare @PaytmBusiness A ticket should not be marked “resolved” when the customer's issue is still pending. Please reopen and escalate my complaint to the senior grievance team and permanently close my merchant account as requested. Ticket ID: [500011909287] 2/3

• 
  Wasim (@wasim_sayy) reported 11 minutes ago

  @PaytmBusiness @Paytmcare @PaytmBusiness marked “resolved” when the customer's issue is still pending. Please reopen and escalate my complaint to the senior grievance team and permanently close my merchant account as requested.

• 
  Sahil Kalyani (@sahilkalyani_in) reported 11 minutes ago

  Hello @Paytmcare maybe change your username to @paytmdoesnotcare cause that is how your customer service is.

• 
  Kabilasudhan (@Kabilasudhan) reported 14 minutes ago

  @Paytmcare @Paytm I would like to request a feature to have a dedicated statement download option for Pocket Money either via filter or directly in the Pocket Money Payment History section. It will help people to see the spend summary on monthly basis to compare.

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

• 
  Guru_K (@GuruyuganK) reported 16 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

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

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

• 
  Urstrulysanni 🩷 (@urstrulysanni) reported 17 minutes ago

  Worst service @Paytm

• 
  Rebel (@TheRebelRain) reported 18 minutes ago

  @PaytmBank Hey @Paytmcare I have sent an email to the Nodal Officer regarding CKYC number issue in my mother's account. Kindly respond to it ASAP. @PaytmBank