Paytm status: access issues and outage reports

Problems in the last 24 hours in Batāla, Punjab

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

Latest outage, problems and issue reports in Batāla and nearby locations:

• 
  zomato amritsar (@AmritsarZomato) reported 35 minutes ago from Mahniān Brāhmanān, Punjab

  @deepigoyal @vijayshekhar @Paytm Plz help

• 
  Nayeem wani (@Nayeemwani19) reported 38 minutes ago from Batāla, Punjab

  My Paytm is not working properly I can make transaction but when u try to pay Paytm postpaid bill or helpline it's not working even I can't click on pay due if my dues get more then what I have to pay I will be not responsible for that plz fix it @Paytm @Paytmcare

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  nik (@rhysnik) reported 5 minutes ago

  @Paytm @Paytmcare I demand an explanation from your technical team immediately. Fix your app bugs and address this account security lapse now! RMN: 8828286369

• 
  Gautam Bhatia (@1gautambhatia) reported 7 minutes ago

  @Paytm I am not been able to log into my account as it shows app not supported,I have recently switched my phone .Help on priority

• 
  Harshu✨ (@HarshwardhanOP) reported 9 minutes ago

  Hey @Paytm @Paytmcare @SuryodayBank payed my paytm postpaid bill still not updated and tried to raise ticket it shows there temporary service issue Help with this asap

• 
  Arjun (@TheDesiBoyy) reported 9 minutes ago

  @Paytmcare @Paytm my Paytm scanner works slow, kindly help me. I have uninstall it and install it again but still same issue.

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

• 
  Gautam Bhatia (@1gautambhatia) reported 13 minutes ago

  @Paytmcare help

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

• 
  Urstrulysanni 🩷 (@urstrulysanni) reported 17 minutes ago

  Worst service @Paytm

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

  @Paytm @Paytmcare @PaytmBusiness I will not activate or accept any rental/subscription charges for a device I cannot use. Clarify immediately why it was dispatched and confirm that no charges will be imposed without my consent. Resolve my account limit issue or take the Soundbox back at no cost.

• 
  Ram Narra (@ram_07Narra) reported 22 minutes ago

  UPI made payments effortless. I’d build Paytm an AI agent that understands your money, remembers context, explains charges, fixes failed payments, and acts on your intent. From “Where did my money go?” to “Fix it for me.” One agent, not a dashboard. @Paytm @SarvamAI @Hack_Culture