Paytm status: access issues and outage reports

Problems in the last 24 hours in Bhadohi, Uttar Pradesh

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

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

• 
  Zia Malik (@zialeavgalld) reported 21 minutes ago from Bhadohi, Uttar Pradesh

  Hello @Paytmcare, @Paytm, @paytmbankcare what should I do to get you respond? Your customer care is also not working, please help.

• 
  Tazeem Sheikh (@TazeemSheikh3) reported 37 minutes ago from Mādhosingh, Uttar Pradesh

  @paytmbankcare i m not able to create any FD of any amount in my account. It's always show insufficient balance while creating FD. Please help @PaytmBank @Paytm

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  sidharthdhev (@sidhtweeets) reported 6 minutes ago

  @Paytmcare Got logged out without any reason and unable to login since 3 days? What is going on?

• 
  Aniruddha Borpuzari (@AniruddhaBig) reported 14 minutes ago

  @IndiGo6E @Paytmcare @Paytm please help me do the correction of Name spelling

• 
  Golu Nagar (@GoluNagarFVK) reported 14 minutes ago

  Hello paytm, I'm unable for paytm for business merchant account because of location error but many shopkeepers using paytm for business in my pin code area but why this service not available for me ? @Paytmcare @PaytmBusiness

• 
  Chintan (@ChintanSisyphus) reported 16 minutes ago

  @Paytmcare Are you doing anything or not to solve the bloody problem?? Bloody frauds!!! Atleast acknowledge the problem first and have some professional communication!!! Noone should ever use paytm!! I will file a police complaint if my issue is not resolved right now!!

• 
  Sahil Mansuri (@SahilMa15555552) reported 21 minutes ago

  @Paytmcare i my self sahil my paytm is not working from more than 2 months it is showing rooted device

• 
  Sunil (@jhansi_pandu) reported 24 minutes ago

  Beware of @Paytm! Agents push you to take Paytm machines, but later hold merchant funds. When we submit requested docs, they reject them and won't even provide sample formats. Don't use Paytm! DM me if you're facing the same issue. @vijayshekhar @Paytmcare

• 
  Sameer Goyal 🇮🇳 (@sameergoyal) reported 25 minutes ago

  @cassbdb @Paytm Actually AWS was down and hence a lot of services went down globally …

• 
  dharmpal garhwal (@dpalgarhwal) reported 29 minutes ago

  Not able to talk with @Paytmcare from last 3 days regarding the payment of my loan emi . There is not a single option to connect with customer support there Bot replies that i’ll connect you shortly ,no email no number worst service i ever faced

• 
  Dinesh🇮🇳 (@Redd63184Reddy) reported 32 minutes ago

  **** the paytm .no coutemer support .i have raised complaint 3 days ago still you didn’t solved that.dont ever use this ****** app @Paytm @Paytmcare #paytm

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