Paytm status: access issues and outage reports

Problems in the last 24 hours in Jogan, Gujarat

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

Latest outage, problems and issue reports in social media:

• 
  Vidyut Pal (@the_viddy) reported 4 minutes ago

  @Paytm @BSNLCorporate I recharged a BSNL number with PAYTM, it's a BSNL number. It got into pending... Now it's almost 5th day no information and no refund and nothing. Disgusting service....

• 
  tenminutes (@TenMinuteSW) reported 5 minutes ago

  Hi @Paytm can you pls help me resolve this" device environment is not correct " bug?

• 
  Sahil Kalyani (@sahilkalyani_in) reported 6 minutes ago

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

• 
  Sharath B (@Sharath85852559) reported 7 minutes ago

  @Paytmcare I wanted to know what is the issue. Why I am facing this issue

• 
  Sanju Bai Bairwa (@SANJUBAIBAIRWA) reported 8 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

• 
  Happiefy (@happiefy) reported 11 minutes ago

  @Paytm @Paytmcare most pathetic service ever need to file case in consumer forum because they are fooling people doing fraud took Money and no response will go consumer forum if thy don’t remove that bus from plateform and give me 10x compensation our family still there waiting

• 
  Surjeet Singh (@asksurjeet) reported 12 minutes ago

  @Paytmcare 1/3 Thank you for the update, @Paytmcare.
Appreciate you reviewing the device verification issue on priority. Please keep me posted as soon as there’s any progress.

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

• 
  Syed Muzaffar (@SyedMuz31229099) reported 15 minutes ago

  @Paytmcare @vijayshekhar please don't waste ur time if u're really tracing the error. I accidentally reinstalled the app and it worked. Once again, thanks for taking soooooo long for doing nothing.👎

• 
  Aniruddha Borpuzari (@AniruddhaBig) reported 20 minutes ago

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