Paytm status: access issues and outage reports

Problems in the last 24 hours in Pālampur, Himachal Pradesh

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

Latest outage, problems and issue reports in social media:

• 
  Abhishek Bakshi (@asolitudeseeker) reported 10 seconds ago

  @Paytmcare trying to connect to your customer care since a while without any luck. Kindly get in touch. Thank you.

• 
  CA Sridhar (@SRIDHAR00772301) reported 10 seconds ago

  @Paytmcare @Paytm pls help

• 
  Rikdev Ghosh (@RikdevG) reported 37 seconds ago

  @akashkalyan01 @Paytmcare @Paytm Same issue, any clue how to solve

• 
  shajad ali (@shajada65894051) reported 4 minutes ago

  @vijayshekhar @Paytm @PaytmBusiness fraud service by paytm deduct my amount without my consent and after 40 days not customer care anything response. Please do not ay one trust with paytm when any days he debited your amount without your consent then you will frustrated fraud Pay

• 
  Golu Nagar (@GoluNagarFVK) reported 8 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

• 
  nitin pandey (@thenitinpandey_) reported 9 minutes ago

  @Paytm @Paytmcare (Ref No: 311916579976), but the beneficiary has still not received the amount and the amount has not been reversed to my account. Please resolve this issue urgently. #UPI #PaytmSupport

• 
  hameed (@ammidubai) reported 10 minutes ago

  @Paytm #Your #Scanner has some #Bugs Kindly Fix it

• 
  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. 🙏

• 
  Vidyut Pal (@the_viddy) reported 12 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....

• 
  Eastern Power Distribution Company of AP Limited (@ap_epdcl) reported 20 minutes ago

  @jsurendra26 @Paytmcare @Paytm Thankyou for reaching us! kindly note that broken transaction will be updated within 3 working days. If the issue persists, a full refund will be processed to your account within seven bank working days. For further assistance call us at 1912. We appreciate your understanding.