Paytm status: access issues and outage reports

Problems in the last 24 hours in Vizianagaram, Andhra Pradesh

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

Latest outage, problems and issue reports in social media:

• 
  Parth Chaturvedi (@_mrchaturvedi) reported 5 minutes ago

  It was primary app for me for everything until few years ago.. unfortunately.. now I don’t open it in months.. For UPI - I have shifted to Super Money | PhonePe For everything else like bill payments, recharges, gas, electricity- I have shifted to Amazon Pay. The biggest issue for me is not the absence of rewards on PayTM, which I understand in a long run no one can sustain but charging extra on every payment method for everything except UPI doesn’t sit right with me. On Amazon Pay, at least I can use their gift cards to pay and mostly they don’t charge anything if we are choosing Amazon pay through some other app and use credit card. Though, my best wishes to @vijayshekhar sir and @Paytm but maybe make payments with no extra fee for using Credit cards.

• 
  Subhransu Sekhar Dutta 🇮🇳 (@The_Subhransu) reported 5 minutes ago

  @Paytm @Paytmcare @PaytmBusiness I submitted my PAN, Udyam certificate and 6 months’ bank statements for verification, yet after 15+ days my limit remains ₹1 with no proper resolution. You can dispatch a Soundbox to my address, but you cannot resolve the basic issue preventing me from accepting payments?

• 
  shajad ali (@shajada65894051) reported 10 minutes ago

  @PaytmCare @Paytm @vijayshekhar Terrible service! • 22 Jun: ₹2400 debited from settlement • 28 Jun: Submitted invoice as requested • Customer withdrew dispute at their bank Still waiting for my refund after 2+ months of endless delays. Please credit my amount immediately!

• 
  Reddy (@iam_Rah12627) reported 11 minutes ago

  @Paytmcare I'm stuck in other country and booked a flight from your platform when I got a ticket and checked with the airline , they have informed the reference number is invalid and I cannot even contact you what a pathetic support you have given..

• 
  Ankit Barnwal🇮🇳 (@MrAnkit26599) reported 12 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.

• 
  Farvez Ali (@FarvezAli30140) reported 12 minutes ago

  Please close the peermently paytm payment bank account Please do needful Please help me @PaytmBank @paytmbankcare @Paytm

• 
  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. 🙏

• 
  dume.ai (@Dumeai_) reported 13 minutes ago

  @Paytmcare booked @flyspicejet flight with you. But flight is delayed by 6 hrs. no communication provided for delay and no alternate option provided. And no option to cancel also. Please help me cancel the flight with full refund booking id 27326090561

• 
  Lokii (@lokesh_navale) reported 18 minutes ago

  🚀 For Build for India, I would develop an AI Merchant Copilot for Paytm that transforms payment data into useful information about sales, customers, offers, fraud, and cash flow in Indian languages. AI to help SMBs grow. 🇮🇳 @Paytm @SarvamAI @Hack_Culture #BuildForIndia

• 
  ShivaM Bakshi ✍️ {Journo} (@shivambakshi007) reported 21 minutes ago

  Worst service by @Paytm, they even don't have perfect customer support system.