Paytm status: access issues and outage reports

Problems in the last 24 hours in Krishnarajanagara Taluk, Karnataka

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

Latest outage, problems and issue reports in Krishnarajanagara Taluk and nearby locations:

• 
  ADXB (@ADXB019049345) reported 17 minutes ago from Krishnarajanagara Taluk, Karnataka

  @Paytmcare Help me Contact me

• 
  ADXB (@ADXB019049345) reported 27 minutes ago from Krishnarajanagara Taluk, Karnataka

  @Paytm Help me mera dm chak karlo please

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Sunil (@jhansi_pandu) reported 5 minutes ago

  Beware of @Paytm! Agents push you to take Paytm machines, but later hold merchant funds. When we submit requested docs, they reject them and won't even provide sample formats. Don't use Paytm! DM me if you're facing the same issue. @vijayshekhar @Paytmcare

• 
  Viki (@vikis550) reported 5 minutes ago

  @PaytmBusiness @Paytmcare @vijayshekhar Kuch option sirf dikhawe k liye de rkhe h . Jese ki SPECIFIC QR ACCESS TO CASHIER ye function work nhi krta . App main MERCHANT CARE se baat ki to usne bhi mera bhut time waste kiya kbhi kuch kbhi kuch btaya jo working nhi tha.

• 
  Suresh Kumar Kurapaty (@kurafatygyan) reported 6 minutes ago

  @Paytmcare Can you help me with Paytm wallet ??

• 
  Rohit Singh (@Singhrohit9956) reported 6 minutes ago

  @Paytmcare @vijayshekhar it's very wrost service I raised issue couple of days didn't respond properly i paid assurance amount 580 somthing where is my travel voucher it's really disgusting service no one respond properly

• 
  Patel Purple (@patelnn286) reported 6 minutes ago

  @flipkartsupport @Paytmcare @RBI need your attention, they both cheat the customer on the name of scheme

• 
  Cyril Johnson (@CyrilJohns96815) reported 7 minutes ago

  @Paytm @Paytmcare There is no way to reach out to paytm for emegency support. I have raised a ticket 200012533997 but no one seems to be responding. Is there a way to call and speak to an agent??

• 
  Subodh (@Subz2014) reported 9 minutes ago

  @Paytm looks like your App’s not working, no payments happening.. @FinMinIndia

• 
  Jagdeep Singh (@MLAJagdeepSingh) reported 9 minutes ago

  I have booked air ticket but wrongly I have press wrong date due to which I want to call you for refund but none of your customer care number is working it is very pathetic condition with Paytm with which I was doing lot of payments one of their number say you are not registered with us. I have just lost 6000 rupees but future I will not use Paytm and I'll suggest other also @Paytmcare

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

• 
  Hemant Rajbhar (@HR8528) reported 14 minutes ago

  @Paytm At worst, if Paytm integrates with the cloud, Paytm will say Claude Paytm Payment Gateway charges payment-gateway charges Hosting/server cost ↓ Cloud MCP Connector Paytm Payment Gateway Authentication + Permissions Verification Payment Data Cloud Later Paytm will charge you.