Paytm status: access issues and outage reports

Problems in the last 24 hours in Mohana, Odisha

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

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

• 
  SUNIL KUMAR PATTANAIK (@SUNILKU74204938) reported 58 minutes ago from Mohana, Odisha

  @Paytmcare Your personal loan offer is not available for Sr citizens but lakhs number of Sr citizens are paytm's regular customer.

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Abhi$hek Hindustani (@BrownBoi07) reported 6 minutes ago

  @Paytmcare No further assistance required and I'll make sure to not use your service anymore thanks

• 
  Parth Chaturvedi (@_mrchaturvedi) reported 10 minutes ago

  It was primary app for me for everything until few years ago.. unfortunately.. now I don’t open it in months.. For UPI - I have shifted to Super Money | PhonePe For everything else like bill payments, recharges, gas, electricity- I have shifted to Amazon Pay. The biggest issue for me is not the absence of rewards on PayTM, which I understand in a long run no one can sustain but charging extra on every payment method for everything except UPI doesn’t sit right with me. On Amazon Pay, at least I can use their gift cards to pay and mostly they don’t charge anything if we are choosing Amazon pay through some other app and use credit card. Though, my best wishes to @vijayshekhar sir and @Paytm but maybe make payments with no extra fee for using Credit cards.

• 
  Patel Purple (@patelnn286) reported 14 minutes ago

  @flipkartsupport @Paytmcare @RBI need your attention, they both cheat the customer on the name of scheme

• 
  Syed Muzaffar (@SyedMuz31229099) reported 14 minutes ago

  @Paytmcare @vijayshekhar Now u will take another week to review my account and that too without notifying me. U please first assist me with the ongoing issue.

• 
  Suresh Kumar Kurapaty (@kurafatygyan) reported 15 minutes ago

  @Paytmcare Can you help me with Paytm wallet ??

• 
  rajan ahuja (@rajanahuja9) reported 16 minutes ago

  @RamMNK @paytm @paytmcare Really mentall harssament by paytm team for not procesing of refund. Airline team confirmed they will process the refund but paytm team not ready. Sir, please help on this my Paytm Booking ID : 27345517995

• 
  Chiranjivi Raj (@Techie_Leaf) reported 17 minutes ago

  Due to this issue, I switched from @PhonePe to @Paytm .

• 
  Neeraj Sanwal (@NeerajSanwal999) reported 18 minutes ago

  @PaytmBusiness @Paytm Worst platforms. Unable to connect, No customer support available. Unable to upload documents as requested. It has been 3 days. No help option available. My 5000 is stuck in their business app.

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

• 
  sachin bansode (@sachin_6600) reported 23 minutes ago

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