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 Bela, 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 Bela, Uttar Pradesh
The chart below shows the number of Paytm reports we have received in the last 24 hours from users in Bela, Uttar Pradesh 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 Near Bela, Uttar Pradesh
Latest outage, problems and issue reports in Bela and nearby locations:
-
Durgesh Kumar Ojha (@dkrajan777) reported from Bela, Uttar PradeshHello @Paytm I have fully paid my dues within due date but i am unable to use my postpaid for payments. Already tried to contact customer support but no response,may I know why? @Paytmcare
-
Durgesh Kumar Ojha (@dkrajan777) reported from Bela, Uttar Pradesh@Ashyamsham @Paytm @Paytmcare Exactly Paytm customer support is very frustrating.
Paytm Issues Reports
Latest outage, problems and issue reports in social media:
-
Abhishek (@Abhis2309) reported@Paytm @Paytmcare ur silence is testimony to the alleged wrongdoing & fraud by charging extra to small biz in name of QR code. U hv been silent since 2months on-if QR code for receivng paymnts is free service why club it with soundbox? @RBI pls take action against PAYTM.
-
Hemanta Meher (@MeherHemantt) reportedGuys don't trust @Paytm @PaytmBusiness @Paytmcare Your internal mismanagement should not become a customer's problem. My Soundbox return EO887528444IN was successfully delivered via India Post, but your team still claims its not received and asks me for POD. Very Bad experience😭
-
kushal das (@kushal8609) reported@Paytmcare Still problem not resolved.
-
Bébé Crow (@delphspet) reported@Paytm @Paytmcare could you please look in to this 'phone not supported' error? I have been trying to login from many dayss!!! I have tried reinstalling it. I have raised ticket twice, nada. They all are giving same repeated ans, try another device. I ain't gonna buy new phone!
-
Gyanendra Singh (@GSC1971) reported@Paytmcare I am unable to login in paytm. Paytm unable to send OTP on my registered number. I am in 5G network area.
-
nik (@rhysnik) reported@Paytmcare I am not interested in a phone conversation regarding this matter anymore, as your customer care agents only give standard, unhelpful replies. I require a clear, technical response in writing here regarding why my default preference was overridden.
-
CA Sridhar (@SRIDHAR00772301) reported@Paytmcare @Paytm pls help
-
Shubh (@shubhagrawal205) reported@PaytmTravelCare @Paytm This is a follow-up regarding my refund for Booking IDs 22574209687 and 22487522684, which has been pending for over 2 years. Your team acknowledged the issue and confirmed that the refund details were being investigated (1/3)
-
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. 🙏
-
Abhishek Bakshi (@asolitudeseeker) reported@Paytmcare trying to connect to your customer care since a while without any luck. Kindly get in touch. Thank you.