Paytm status: access issues and outage reports

Problems in the last 24 hours in Ambikāpur, Chhattisgarh

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

Latest outage, problems and issue reports in Ambikāpur and nearby locations:

• 
  अंकित श्रीवास्तव (@official_ankits) reported 38 minutes ago from Ambikāpur, Chhattisgarh

  Dear @Paytm I am not happy with your fastag service. #fastag @Paytmcare

• 
  अंकित श्रीवास्तव (@official_ankits) reported 53 minutes ago from Ambikāpur, Chhattisgarh

  Dear @Paytm I am not happy with you fastag service. #fastag @Paytmcare

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

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

• 
  Sharath B (@Sharath85852559) reported 10 minutes ago

  @Paytm I am facing constant error in my mobile device environment is not correct. I tried everything . But not working. Pls resolve. My number is 9844268858

• 
  Mukesh (@imMukeshK) reported 11 minutes ago

  Dear @Paytm team, I booked flight ticket from Darbhanga to bangalore with booking id 27407277757, Still ticket not confirmed, could you please help me asap.

• 
  CA Sridhar (@SRIDHAR00772301) reported 13 minutes ago

  Hi @Paytmcare @Paytm My order id 27406395348 Purchased a gift card of Decathlon but store people saying invalid requesting you to pls issue refund for the same. Its saying invalid code or PIN. Their gift card saying its start with 10 not 60 requesting you to pls issue refund.

• 
  shajad ali (@shajada65894051) reported 16 minutes ago

  @PaytmBusiness @vijayshekhar @Paytm when I last tweet to paytm then I have received call from escalation department to delete the tweet instead of solving the problem this is your service fraud paytm fraud company

• 
  Moumita Biswas (@solo_motivator) reported 20 minutes ago

  As @Paytm business slowly going down; @UPI_NPCI transactions are going up. In July 2026, they did a transactions of 23.66B INR. #DigitalPayments #digitalpay #bhimupi

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

• 
  Shubh (@shubhagrawal205) reported 20 minutes ago

  @PaytmTravelCare @Paytm This is a follow-up regarding my refund for Booking IDs 22574209687 and 22487522684, which has been pending for over 2 years. Your team acknowledged the issue and confirmed that the refund details were being investigated (1/3)

• 
  CJ (@acjose93) reported 22 minutes ago

  @PaytmBusiness @Paytm @PhonePe_Support I’m facing an issue with a UPI payment that shows as successful, but the underlying transaction/payment issue remains unresolved. I’ve already tried to get this resolved but haven’t received a satisfactory solution. Please look into the matter.

• 
  Ayanjit Chattopadhyay (@ayangooner) reported 22 minutes ago

  @Paytmcare How ridiculous is your service?Trying since one week to get the tickets cancelled and no help.Also why have you replaced your whole customer care to automated bots?