Paytm status: access issues and outage reports

Problems in the last 24 hours in Madanapalle, Andhra Pradesh

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

Latest outage, problems and issue reports in Madanapalle and nearby locations:

• 
  Surya prakash (@trulysurya17) reported 29 minutes ago from Madanapalle, Andhra Pradesh

  Money is deducted from my bank account and the payment is failed and it is not refund into my account please help me @UnionBankTweets @Paytm @Paytmcare

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Mohan Bhog (@winner_platinum) reported 6 minutes ago

  @Paytm @Paytmcare @PaytmBank I have money in my Paytm Wallet , what is the claim procedure now since your bank is closing down ? Please explain to me the claim procedure.

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

  @Paytm @PaytmCare Stop repeating your policy! If the voucher must be redeemed in one go, why was there NO warning or alert on the screen before I used only ₹100? You hid the terms, trapped my money, and now you're escaping responsibility. Fix this UI flaw and refund my ₹2,281!

• 
  Jayveer Rajput (@JayveerUss80620) reported 10 minutes ago

  Hello sir @Paytm Pop up coming for Paytm postpaid limit increase but when I go to account section there is no update @Paytmcare help me

• 
  Syed Muzaffar (@SyedMuz31229099) reported 11 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.👎

• 
  tushar (@emailtj) reported 12 minutes ago

  @Paytm totally pathetic from paytm instead of solving issue with my merchant account they simply chose to deactivate it cant trust paytm anymore beware

• 
  Vinayak Naik (@vinayaksn) reported 13 minutes ago

  @Paytmcare You are losing customers because of this mistake in the code. People are earning money by posting fake videos of how to solve the malicious app error. Hire better developers!

• 
  Jai BOB (@MB_One8) reported 13 minutes ago

  @Paytmcare Is any help I'm get? R u gng to compensate for the very very bad experience caused by u r app? @Paytmcare

• 
  Arpit (@Arpit0310) reported 15 minutes ago

  @Paytmcare Hello Paytm, Please explain why do you want to look into the issue only when someone has already made the booking, why don't you rectify the errors wherein your potential customers will get duped due to misleading Promotions. I've already DMed you and no response yet.

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

• 
  Sachin Kumar Jha - सचिन कुमार झा (@iSachinJha) reported 16 minutes ago

  @PaytmBusiness @Paytmcare I’ve already provided all requested details via DM, but there’s still no resolution. These FY 2022-23 GST invoices are urgently required for my GST notice response. “We are working on it” is not enough anymore.