Paytm status: access issues and outage reports

Problems in the last 24 hours in Hosakote, Karnataka

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

Latest outage, problems and issue reports in Hosakote and nearby locations:

• 
  Mohd Aasim (@mohdaasim736) reported 11 minutes ago from Kolar Taluk, Karnataka

  @Paytm @Paytmcare Dear sir, I have Paytm rupay debit card. Can I access the airport lounge?

• 
  Mithun Kumar Sharma (@mks9636) reported 51 minutes ago from Hosakote, Karnataka

  @Paytm @PaytmMoneyCare The day by day your service quality is getting reduced. My rent payment got stuck suggested to wait why should i wait for 3 days. If you can't settled then initiate my refund. Even though the most of fraud txn happening using Paytm only. money is not safe

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

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

• 
  girish nagpal (@girishnagpal) reported 5 minutes ago

  I have booked a flight ticket from Paytm of indigo and there Is a minor correction required in name so nither paytm supports nither indigo supports and paytm never gets call connected to customer care and indigo airline says please contact to paytm @IndiGo6E @Paytm

• 
  Ayush💥 (@_ayushilicious) reported 6 minutes ago

  @Paytmcare @Paytmcare This is not done yet. Please help out

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

  Hey @PaytmCare,your team refused my refund for ticket 200012349631.I lost ₹2,281 from my flight voucher due to missing single-use warnings on the app screen.Since internal support denied it, I am escalating this matter to the National Consumer Helpline (NCH).Please resolve this.

• 
  Rebel (@TheRebelRain) reported 14 minutes ago

  @PaytmBank @Paytmcare Ticket Number 3391154250. Mother's CKYCC Number has DOB error. Kindly rectify it within this week or else I would have to go to higher authority for Redressal.

• 
  Surjeet Singh (@asksurjeet) reported 15 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.

• 
  minaz fruitwala (@FruitwalaMinaz) reported 15 minutes ago

  @Paytmcare i now realised why prople has stopped using paytm , paytm is the new scam , booked a flight tix on paytm , its been one more its still pending . Money has already been deducted , no confirmation yet , no customer cate service #fraudalert #paytm #scam

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

• 
  nik (@rhysnik) reported 17 minutes ago

  @Paytmcare Stop sending automated bot replies claiming a completed transaction is 'pending'! Read my issue: I am pointing out your app’s technical routing glitch, not asking for transaction status. Stop deflecting and provide a manual response from a human representative!

• 
  Shrishti Rai (@ShrishtiRaii) reported 17 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