Paytm Outage Map
The map below depicts the most recent cities worldwide where Paytm users have reported problems and outages. If you are having an issue with Paytm, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Paytm users affected:
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.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Chhindwāra, MP | 6 |
| Noida, UP | 1 |
| Pānīpat, HR | 1 |
| New Delhi, NCT | 7 |
| Bengaluru, KA | 2 |
| Sūrat, GJ | 1 |
| Indore, MP | 1 |
| Kanpur, UP | 1 |
| Jaipur, RJ | 2 |
| Chennai, TN | 1 |
| Shimla, HP | 1 |
| Port Blair, AN | 1 |
| Lucknow, UP | 1 |
| Kolkata, WB | 3 |
| Varanasi, UP | 1 |
| Dehra Dūn, UT | 1 |
| Delhi, NCT | 1 |
Check Current Status
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:
-
Mehul Desai (@livingfree60) reported650.19 re credited to upi lite. Now for the balance either let me use it to make pmts or help get it credited back into my bank acct @vijayshekhar @Paytmcare
-
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
-
UPSRTC Lucknow Region (@upsrtc_lko) reported@Devshhh @UPSRTCHQ @Paytm please share ticket or pnr number as this Ticket no: 0000003546BA is not of upsrtc website
-
infodypiuacin (@infodypiua31001) reported@Paytmcare you guys are bunch of crooks , bunch of scounderals , i purchased a eatsure gift voucher from paytm app its missing security pin and from code its missing 4 digits too , this isssue is too comman none of your ai or mail is solving the issue #scamawareness #paytmisscam
-
Shrishti Rai (@ShrishtiRaii) reported@Paytmcare It’s been almost 10 days now. Please connect me with one of your customer support executives. You have a terrible chat support. @Paytm @Paytmcare
-
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. 🙏
-
sidharthdhev (@sidhtweeets) reported@Paytmcare Got logged out without any reason and unable to login since 3 days? What is going on?
-
Gautam Bhatia (@1gautambhatia) reported@Paytmcare help
-
Ajay K Saini (@sainiajay16) reported@Paytm @PaytmCheckin need help to get the details correction in flight booking as well as for partial cancellation for ticket. Unable to contact with Paytm support and neither getting response on email and chat.
-
VoiceOfChange_Anu (@Sainianu22) reported@Paytmcare No data found of health insurance on Adiya Birla Website.
-
hameed (@ammidubai) reported@Paytm #Your #Scanner has some #Bugs Kindly Fix it
-
Abhishek Bakshi (@asolitudeseeker) reported@Paytmcare trying to connect to your customer care since a while without any luck. Kindly get in touch. Thank you.
-
Yash Sharma (@ys_2800) reported@Paytmcare Issue resolved but this mis happening taken by merchant.
-
Ravi Mangnani (@sanjuravi) reported@Paytmcare Finally I m uninstalling paytm and switch to next options unhappy from service
-
Prudvi_Bob ©️ (@PrudviVysyaraj) reported@Paytm @Paytmcare @SuryodayBank Paid ₹9,000 in full on 30 July & requested closure. Yet ₹180 Convenience Fee + ₹32.40 IGST was charged,and ₹212.40 was auto-debited on 3 Aug. Multiple emails to Suryoday Bank,but no acknowledgment or response.Why is customer grievance ignored?
Check Current Status