Paytm status: access issues and outage reports

Problems in the last 24 hours in Achhola, Uttar Pradesh

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

Latest outage, problems and issue reports in Achhola and nearby locations:

• 
  अंकित मिश्रा (पिपरा) (@smartypipara) reported 49 minutes ago from Meja, Uttar Pradesh

  @Paytmcare Unable to talk with your customer representatives regarding payment banks.

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Sharath B (@Sharath85852559) reported 4 minutes ago

  @Paytmcare I am unable login paytm from last 10 days no solution from your end. What is the error. Pls rectify immediately @vijayshekhar

• 
  Sanju Bai Bairwa (@SANJUBAIBAIRWA) reported 6 minutes ago

  Hey @PaytmCare, your service is shameful! You hide 'single-use' terms on flight vouchers to rob users. You stole my ₹2,281 and your agents shamelessly closed my ticket (200012349631) without resolution. This is outright fraud! Stop scamming and refund my money! #PaytmFraud

• 
  Jitendra Kumar (@Jitendrbmp) reported 7 minutes ago

  @Paytm @Paytmcare @PaytmMerchants My paytm merchant account nd sound box not working properly, i tried many times but still not closed my account, very poor service provide by paytm

• 
  Vikas Sharma (@Vikass_BJP) reported 8 minutes ago

  @Paytmcare Getting no response for refund from last 12 days bloody mother ****** paytm team Bloody **** on you

• 
  ShivaM Bakshi ✍️ {Journo} (@shivambakshi007) reported 8 minutes ago

  Worst service by @Paytm, they even don't have perfect customer support system.

• 
  Sanju Bai Bairwa (@SANJUBAIBAIRWA) reported 9 minutes ago

  @PaytmCare You are running a loot shop in the name of service! You hide rules on purpose, give zero warnings, swallow user money, and then act blind. This is a total scam. Give my ₹2,281 back or own the tag of digital thieves! #PaytmScam

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

• 
  Danish Gupta (@DanishG33582187) reported 11 minutes ago

  @Paytmcare @Yendrapati1991 Hey paytm why you not replying me what's your issue I messaging you from 7 days continuously but you even not giving s single response to me what's this behaviour paytm? @Paytmcare please check your dm and respond me

• 
  Mirza Anwaarullah Baig (@m14z4) reported 11 minutes ago

  Thinking about what to build at @Paytm’s #BuildForIndia AI Hackathon. What if you didn’t give an AI agent access to your bank account—you gave it a controlled financial identity? Voice + agentic payments + dynamic UI, with spending rules and human approval built in. Exploring.

• 
  Mohammed Aakif Ulla (@AakifUlla) reported 15 minutes ago

  @Paytmcare @Paytm Have some shame and do reply u know only to tell not to resolve issues is it ? @vijayshekhar your team is useless so only ur company is drowning