Paytm status: access issues and outage reports

Problems in the last 24 hours in Warangal, Telangana

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

• 
  Sahil (@sahilhaiderlive) reported 4 minutes ago

  @Paytmcare I had ordered a #VakuLuxos phone cover redeeming a voucher from your @Paytm app. Received wrong product, but since then they are not responding neither on email nor over call. Please help in this regard!

• 
  Ravi Chandar (@ravikchandar) reported 6 minutes ago

  @karaikude @Paytm It is. Tried to make payment then checked app. It is down for a while seeing tweets here.

• 
  shajad ali (@shajada65894051) reported 7 minutes ago

  @vijayshekhar @Paytm @PaytmBusiness fraud service by paytm deduct my amount without my consent and after 40 days not customer care anything response. Please do not ay one trust with paytm when any days he debited your amount without your consent then you will frustrated fraud Pay

• 
  rajan ahuja (@rajanahuja9) reported 7 minutes ago

  @Paytmcare Can you please help

• 
  kadam Soni (@KadamSoni3) reported 14 minutes ago

  @Paytmcare The problem is still not resolved. One issue has been fixed, but another is still pending. What’s going on? I’ve been using Paytm since 2021 and have never experienced this kind of problem before. Please resolve it as soon as possible.

• 
  Santosh Rai (@santoshraig) reported 14 minutes ago

  @sunilp3007 @Paytm Right said all upi down

• 
  Justin Army (@JustnbieberIND) reported 15 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?

• 
  சிகை கொற்றன் 🖤❤️ (@karaikude) reported 17 minutes ago

  Is @Paytm down for last two hours? #PayTM

• 
  Rikdev Ghosh (@RikdevG) reported 20 minutes ago

  @SohidulBiswas @Paytmcare I am facing the same issue, how to solve it

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