Paytm status: access issues and outage reports

Problems in the last 24 hours in Akhāra, Punjab

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

Latest outage, problems and issue reports in Akhāra and nearby locations:

• 
  Adv Raman Garg (@ramangarg01) reported 13 minutes ago from Rāikot, Punjab

  @Mswipe my card swipe machine is not working from last 15 days Numberless complaints have been raised But no resolution from your side @Paytm can you provide card swipe machine to me

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Yash Sharma (@ys_2800) reported 2 minutes ago

  @Paytmcare Issue resolved but this mis happening taken by merchant.

• 
  Hemant Rajbhar (@HR8528) reported 3 minutes ago

  @Paytm At worst, if Paytm integrates with the cloud, Paytm will say Claude Paytm Payment Gateway charges payment-gateway charges Hosting/server cost ↓ Cloud MCP Connector Paytm Payment Gateway Authentication + Permissions Verification Payment Data Cloud Later Paytm will charge you.

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

  Hey @PaytmCare, your service is shameful! You hide 'single-use' terms on flight vouchers to rob users. You stole my ₹2,281 and your agents shamelessly closed my ticket (200012349631) without resolution. This is outright fraud! Stop scamming and refund my money! #PaytmFraud

• 
  Shrishti Rai (@ShrishtiRaii) reported 4 minutes ago

  @Paytmcare It’s been almost 10 days now. Please connect me with one of your customer support executives. You have a terrible chat support. @Paytm @Paytmcare

• 
  Sharath B (@Sharath85852559) reported 5 minutes ago

  @Paytmcare I am not understanding what is the issue here. Why it is taking so long after highlighting 5 days. Really frustrated

• 
  Harshu✨ (@HarshwardhanOP) reported 10 minutes ago

  Hey @Paytm @Paytmcare @SuryodayBank payed my paytm postpaid bill still not updated and tried to raise ticket it shows there temporary service issue Help with this asap

• 
  Divyanshi (@divyanshifr) reported 11 minutes ago

  @fadaknahipadtaa @Paytm I have spotted spelling errors in national newspapers also 😭

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

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

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