Paytm status: access issues and outage reports

Problems in the last 24 hours in Dhāmpur, Uttar Pradesh

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

Latest outage, problems and issue reports in Dhāmpur and nearby locations:

• 
  Ashok Kam (@3500801e0f49418) reported 3 minutes ago from Dhāmpur, Uttar Pradesh

  @Paytmcare Paytm fastag does not have temporary activate/Deactivate option at customer end. Kindly provide this option at customer end to safe guard money kept in Paytm fastag.

• 
  Amit singh saini (@Amitsaini88690) reported 52 minutes ago from Seohāra, Uttar Pradesh

  close my paytm box and take it back please solve my problem @Paytm @Paytmcare @TheOfficialSBI

• 
  Imran press reporter (@Imran03168451) reported 55 minutes ago from Dhāmpur, Uttar Pradesh

  @Paytmcare my order not delivery but status is delivery my order ID 19000719087 I am wait for delivery sar help MI check this problem or solution

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  nik (@rhysnik) reported 4 minutes ago

  @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.

• 
  Kaustubha Kubal (@Kaustubha45) reported 4 minutes ago

  @creditcardwalah @Paytm @Visa Got it i think it's an glitch in app

• 
  Giri Sai (@noxiousgiri) reported 5 minutes ago

  @saaaanjjjuuu Same with @Swiggy @Paytm .. they will ask us to mail them, or wait for 72 hrs for the resolution that’s it they will think we will forget the issue…

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

• 
  Sharath B (@Sharath85852559) reported 8 minutes ago

  @Paytm I am facing constant error in my mobile device environment is not correct. I tried everything . But not working. Pls resolve. My number is 9844268858

• 
  Rishebh Anupam Chaturvvedi (@RishebhC) reported 8 minutes ago

  @Paytmcare highly disappointed with the customer care, no response since so long on a refund. Ticket ID: 200012412121. Have requested for a call multiple times but no response. Flight from Bombay to Delhi (27326371910 ) was cancelled and refunded by airline. HELP.

• 
  sachin bansode (@sachin_6600) reported 9 minutes ago

  @vijayshekhar it will be @Paytm if you were to work harder @vijayshekhar and solve higher problems..

• 
  Kamal Jain (@Kamaljain9351) reported 18 minutes ago

  @PaytmBusiness @Paytm @paytmbankcare I am sending the details with you please check & solve the problem

• 
  VISIONARY DEV🌟 (@visionaryo75157) reported 18 minutes ago

  @Paytmcare @SwapnilDhwani I am also having same issue with paytm gold

• 
  Sahil Kalyani (@sahilkalyani_in) reported 18 minutes ago

  Hello @Paytmcare maybe change your username to @paytmdoesnotcare cause that is how your customer service is.