Paytm status: access issues and outage reports

Problems in the last 24 hours in Pathanāmthitta, Kerala

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

• 
  Hemant Rajbhar (@HR8528) reported 17 seconds 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.

• 
  🇮🇳Rao Sharukh🇮🇳 (@BeingRaoSharukh) reported 1 minute ago

  Worst experience with Paytm. ₹6,225 was debited from account 3 days ago, yet the payment is still pending despite multiple complaints. Two tickets raised already but nobody contacted yet.   Call me now and resolve this issue now.       Con no - 9690773800 @Paytmcare @Paytm

• 
  Sahil Mansuri (@SahilMa15555552) reported 3 minutes ago

  @Paytmcare i my self sahil my paytm is not working from more than 2 months it is showing rooted device

• 
  Abhishek Bakshi (@asolitudeseeker) reported 6 minutes ago

  @Paytmcare trying to connect to your customer care since a while without any luck. Kindly get in touch. Thank you.

• 
  Jayveer Rajput (@JayveerUss80620) reported 8 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

• 
  Rikdev Ghosh (@RikdevG) reported 8 minutes ago

  @akashkalyan01 @Paytmcare @Paytm Same issue, any clue how to solve

• 
  Happiefy (@happiefy) reported 9 minutes ago

  @Paytm @Paytmcare booked bus from Delhi to prayagraj today bus driver phone was off operator Didnt pick up costumer care didn’t respond my family was waiting there for hours no response pathetic service need urgent action and compensation Paytm Booking ID*: 27456038637 File case

• 
  Bill_o_ta😼 (@Bill_o_ta) reported 14 minutes ago

  If it's my phone, my information, my bank details, I should be able to take screenshot of what ever ******** is on my screen. Annoying as hell. 😐😐 Why can't I SS my own transaction details? @PhonePe @Paytm

• 
  Divyam (@DivyamMittal5) reported 16 minutes ago

  @flyspicejet My Delhi–Mumbai flight TODAY has been pushed to tomorrow due to “operational reasons”. I have an important meeting tomorrow morning and NEED to reach Mumbai today Customer care isn't answering and your portal won't help. @Paytm says contact SpiceJet FIX THIS NOW!

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