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 Kūmher, 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 Kūmher, Rajasthan
The chart below shows the number of Paytm reports we have received in the last 24 hours from users in Kūmher, Rajasthan 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 Kūmher, Rajasthan
Latest outage, problems and issue reports in Kūmher and nearby locations:
-
Er Praveen Sharma (@npraveen01) reported from Bharatpur, Rajasthan@Paytm @Paytmcare My paytm account was hacked and am connected more and more your customer care but call not connecting
-
Er Praveen Sharma (@npraveen01) reported from Bharatpur, Rajasthan@Paytm your customer care support team not connecting am connected more than more My business account transaction show fraud transaction
-
milind deepankar (@MilindDeepankar) reported from Bharatpur, Rajasthan@Paytmcare @PaytmMoney please resolve the problem.
-
Er Praveen Sharma (@npraveen01) reported from Bharatpur, Rajasthan@Paytmcare your call centre call not connecting and my paytm for business is created a big problem Any solution
-
Vikas Sharma Bharatpur (@vikassharma94) reported from Kūmher, Rajasthan@Paytm - hi some one tring login from my number.I receiving OTP again and again.
Paytm Issues Reports
Latest outage, problems and issue reports in social media:
-
Sharath B (@Sharath85852559) reported@Paytmcare I am not understanding what is the issue here. Why it is taking so long after highlighting 5 days. Really frustrated
-
Satish Kumar (@SatishK11468) reported@Paytmcare Hi Iam unable to login to Paytm When try to login after logout its not working in my iphone Its showing like Phone not supported error msg Please help me in this @Paytm #paytm
-
nik (@rhysnik) reported@Paytmcare Your response shifting responsibility to the PSP/bank is completely unacceptable. The default preference issue and routing failure happened within the app integration. Furthermore, to avoid any further confusion, I have already removed all bank accounts from WhatsApp Pay.
-
Akash Kumar roy (@akashkroy12) reported@Paytmcare @Paytm @MyIndusIndBank I hv ~₹2.77 lakh in IndusInd FDs created via PPBL. An IndusInd branch LOCATED & confirmed my FDs, yet IndusInd grievance team tells me to contact Paytm. PPBL is under windingup& its channel is unavailable. How am I supposed to access MY money?
-
Pradyuman Ojha (@pradyuman_ojha) reportedHey @Paytm @PaytmCare, please fix/update the gold jackpot offer! If the tasks can't even be completed, don't run offers just to fool your loyal customers. People spend time on these—at least make them work properly.
-
Subhransu Sekhar Dutta 🇮🇳 (@The_Subhransu) reported@Paytm @Paytmcare @PaytmBusiness I submitted my PAN, Udyam certificate and 6 months’ bank statements for verification, yet after 15+ days my limit remains ₹1 with no proper resolution. You can dispatch a Soundbox to my address, but you cannot resolve the basic issue preventing me from accepting payments?
-
Kaustubha Kubal (@Kaustubha45) reported@creditcardwalah @Paytm @Visa Got it i think it's an glitch in app
-
Wasim (@wasim_sayy) reportedPaytmCare @PaytmBusiness Why are my support tickets being closed without resolving my request? I have clearly requested the closure of my Paytm Business Merchant Account yet the ticket is being close repeatedly without actually processing the closure. 1/3
-
Ankit Barnwal🇮🇳 (@MrAnkit26599) reportedWhat's your new excuse despite providing all the details @Paytmcare Accept your negligence, Your technician is not willing to work, your team is not willing to work. Why you guys don't shut down your services.
-
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. 🙏