Paytm status: access issues and outage reports

Problems in the last 24 hours in Sīkar, Rajasthan

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

Latest outage, problems and issue reports in Sīkar and nearby locations:

• 
  SJC tanwar singh (@tanwarsingh90) reported 45 minutes ago from Sīkar, Rajasthan

  @Paytmcare Paytm customer care are not help me. Call center are not connecting with me

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Siddu (@peaksiddharth) reported 4 minutes ago

  UPI is instant. Resolving a broken payment isn't For #BuildForIndia, I'd build @Paytm Resolve an AI agent that traces failed/pending payments across the transaction lifecycle, finds where money is stuck, takes the next safe action, tracks it until resolved @SarvamAI @Hack_Culture

• 
  Saumya Sharma (@pseud039) reported 5 minutes ago

  Small businesses still spend way too much time on things that could probably be handled quietly in the background. I’ve been wanting to explore that problem for a while. Now seems like a good time to build around it. Paytm × Sarvam AI hackathon. #BuildForIndiaAI @Paytm @SarvamAI

• 
  Sahil Kalyani (@sahilkalyani_in) reported 5 minutes ago

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

• 
  Giri Sai (@noxiousgiri) reported 6 minutes ago

  @saaaanjjjuuu Same with @Swiggy @Paytm .. they will ask us to mail them, or wait for 72 hrs for the resolution that’s it they will think we will forget the issue…

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

  Hey @PaytmCare, my support ticket (200012349631) was closed by your team without a refund. I accidentally redeemed just ₹100 from my ₹2,381 flight voucher due to a lack of single-use warnings. As a regular user, I request a goodwill refund of my remaining balance. Please help🙏

• 
  Tanmay Dixit 🧢 (@tanna_dxt) reported 8 minutes ago

  @Paytm @Paytmcare @PaytmBusiness I had already deactivated/cancelled my Paytm Soundbox, but I was still charged ₹693 for the period from 25 July till now. Since the Soundbox was already deactivated and I am not using the service, Please look into this issue, refund the ₹693.

• 
  BASTAGANAHAINA (@iloveeeeeeeuu) reported 13 minutes ago

  @divyanshifr @Paytm how it's working fine in my mobile cross cheked how in you it not working and in hour working fine. it will not work like that

• 
  Parth Patel (@parthpatel080) reported 14 minutes ago

  In 2023, VSS acquired a 10.3% Paytm stake from Chinese investor Antfin at ₹796.60/share via OCDs. Today, his vehicle Resilient is offloading up to 4.98% through a block deal at a floor price of ₹1,535.10/share. That's nearly a 2X return #paytm @vijayshekhar @paytm

• 
  Wasim (@wasim_sayy) reported 17 minutes ago

  @PaytmBusiness @PaytmCare @PaytmBusiness Why are my support tickets being closed without resolving my request? I have clearly requested the closure of my Paytm Business Merchant Account, yet the ticket is being closed repeatedly without actually processing the closure. A ticket should not be

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