Paytm status: access issues and outage reports

Problems in the last 24 hours in Etah, Uttar Pradesh

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

Latest outage, problems and issue reports in Etah and nearby locations:

• 
  Naveen Kr Singh (@NaveenKrSingh19) reported 54 minutes ago from Etah, Uttar Pradesh

  @Paytm kindly update your toll-free no for resolve problems .

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Abhishek Bakshi (@asolitudeseeker) reported 5 minutes ago

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

• 
  Surjeet Singh (@asksurjeet) reported 10 minutes ago

  1/1 @Paytmcare I’m unable to log in because the OTP is not being received on my registered mobile number. The number is active and working properly on my phone, yet I’ve been facing this issue since yesterday. I’m also seeing a “Daily verification limit reached” message, even though the OTP itself isn’t arriving. Please look into this urgently and help me regain access to my account. #Paytm #OTPIssue

• 
  Naresh Tiwari (@NareshTiwai) reported 10 minutes ago

  @Paytm @Paytmcare @PaytmCheckin I’m trying to book a bus ticket, but there’s no option to apply a coupon code during the booking process. I’m also facing an issue with the payment. Please look into this and help me resolve it so I can complete my booking. #Paytm #BusBooking

• 
  Abhishek Verma (@FastLanerCF) reported 13 minutes ago

  @Paytmcare issue with Indane Gas booking I booked order from Paytm on 16th August which is still shown pending on paytm app. But the delivery guy is saying my booking has been cancelled by Indane , im not understanding since i cannot book again before 25 days, what should i do

• 
  Lalit Ramchandani (@lalit1717) reported 14 minutes ago

  @Paytmcare @PaytmBusiness Soundbox nit getting charged, unable to use services, if for a business owner you can’t resolve the problem in 2 days then what is the use of the service? Kindly tell me process to surrender the soundbox

• 
  Shailja Nandan Mishra (@mishra_sn1) reported 17 minutes ago

  @PaytmCheckin @Paytmcare URGENT! Booking ID: 27498426894 - Payment processed at 10:50 AM but confirmation STILL PENDING. My flight departs TODAY at 7 PM (GOP→DEL). I don't have my ticket yet! This needs immediate resolution NOW. Please help! 🆘 #PayTMTravel

• 
  yt star yash (@yt_star_yash) reported 19 minutes ago

  @Paytmcare I didn't get REFFERAL cashback amount . I reffred person completed his 1st payment through using paytm app. Kindly request to paytm slove my problem .

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

• 
  Virinder K Kandhari (@kandharivk) reported 23 minutes ago

  Hi @Paytmcare @Paytm It’s been a week since I am unable to access my UPI on PayTM app and despite chasing your customer care, no resolution has been provided. Can you please arrange a call based assistance for a senior citizen like me? Please help!!!! Complaint no 200012492254

• 
  Mohammed Aakif Ulla (@AakifUlla) reported 27 minutes ago

  @Paytmcare @Paytm Have some shame and do reply u know only to tell not to resolve issues is it ? @vijayshekhar your team is useless so only ur company is drowning