Paytm status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
- Paytm generated 0 outage signals in the last 24 hours around Buxar, including 0 direct reports.
Paytm is an Indian e-commerce payment system and digital wallet company that lets consumers pay for services including prepaid mobile and data services, direct-to-home tv service and toll services.
Problems in the last 24 hours in Buxar, Bihar
The chart below shows the number of Paytm reports we have received in the last 24 hours from users in Buxar, Bihar and surrounding areas. An outage is declared when the number of reports exceeds the baseline, represented by the red line.
At the moment, we haven't detected any problems at Paytm. Are you experiencing issues or an outage? Leave a message in the comments section!
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:
-
Surjeet Singh (@asksurjeet) reported1/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
-
SY (@might_offend) reported@Paytm @Paytmcare - WHERE THE HELL IS YOUR CUSTOMER SUPPORT?! My elderly mother is struggling to close her account for past 10 DAYS but is unable to because she cannot cancel an active mandate as she changed her mobile number at the bank. (1/2)
-
Ravi Mangnani (@sanjuravi) reported@Paytmcare Morning me update aaya tha kia but same problem continue hain
-
Gyanendra Singh (@GSC1971) reportedWhy Paytm down in delhi. I can't log in. @Paytm
-
Surjeet Singh (@asksurjeet) reported1/5 @Paytmcare What is happening in your system? I’ve been trying to complete device verification for the last 3 days but keep getting “Verification couldn’t be completed – We didn’t receive the verification SMS”. I already have an unlimited recharge pack + extra top-up balance on my number. Still not able to login. Please resolve this urgently.
-
rajan ahuja (@rajanahuja9) reported@RamMNK @Paytm @narendramodi Sir, how you allowing paytm to sell the airline ticket without having any customer suppourt team. I am struggling with last 10 days with them to get call back and resolution. Paytm travel desk should be ban immediately
-
Viki (@vikis550) reported@PaytmBusiness @Paytmcare There are some options in the paytm for business app that don't work; I lodged a complaint about them, but there hasn't been a solution yet. Wait more than 7 days . Still not solved What is the issue ?
-
prince garg (@princegargg) reported@Paytm @Paytm is down since yesterday? Technical issue error everytime
-
Chinmaya (@ChinmayaSaxena) reported@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. 🙏
-
GenuineGuy (@GenuineguyKs) reported@Paytm i need urgent help. Can you telo me how to contact your customer service on phone as emails are not helping at all ??