Paytm status: access issues and outage reports

Problems in the last 24 hours in Akhāra, Punjab

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

Latest outage, problems and issue reports in Akhāra and nearby locations:

• 
  Adv Raman Garg (@ramangarg01) reported 14 minutes ago from Rāikot, Punjab

  @Mswipe my card swipe machine is not working from last 15 days Numberless complaints have been raised But no resolution from your side @Paytm can you provide card swipe machine to me

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Vikas Sharma (@Vikass_BJP) reported 49 seconds ago

  Tkts cancellation is there but not getting refund as per policy of 24 hours if payment done by UPI very bad Service @Paytm

• 
  Pankaj Kumar Mishra (@Pankaj_Mishra86) reported 2 minutes ago

  @Paytm @Paytmcare In morning i have completed my payment for insurance and payment is deducted but I didn't get any confirmation confirmation also you support only saying apologies @irdaindia my insurance policy is expire today night, I am trying since morning for confirmation

• 
  Yash Sharma (@ys_2800) reported 7 minutes ago

  @Paytmcare Issue resolved but this mis happening taken by merchant.

• 
  Rishebh Anupam Chaturvvedi (@RishebhC) reported 7 minutes ago

  @Paytmcare highly disappointed with the customer care, no response since so long on a refund. Ticket ID: 200012412121. Have requested for a call multiple times but no response. Flight from Bombay to Delhi (27326371910 ) was cancelled and refunded by airline. HELP.

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

• 
  Arpit (@Arpit0310) reported 9 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.

• 
  Ujjwal Khanna (@Ujjwalkhannaa) reported 9 minutes ago

  @Paytmcare Utterly disappointed with your customer care @Paytm Absolutely pathetic #paytm #pathetic

• 
  शिवम् शाही (@itz_shivam18) reported 12 minutes ago

  @PaytmCheckin @PaytmTravelCare @Paytmcare I had interviewed for executive role in paytm travel for flightsinterview and all was good howvr I have been rjctd by saying thatsince I was working at a higher position in previous company so they cant take me despite me being qualified.

• 
  Urstrulysanni 🩷 (@urstrulysanni) reported 22 minutes ago

  Worst service @Paytm

• 
  Vicky (@bishtvicky2005) reported 23 minutes ago

  Purchased a Google Play Redeem Code worth Rs 427 when I tried to redeem it it came out to be already redeemed. I contacted your support through chat which promised me a replacement after this, a refund was promised but I received nothing. Order ID: 27413684132 @Paytm @Paytmcare