1. Home
  2. ❯
  3. Companies
  4. ❯
  5. Paytm
  6. ❯
  7. Mānsa
Paytm

Paytm status: access issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map
  • Paytm generated 0 outage signals in the last 24 hours around Mānsa, including 0 direct reports.

Paytm is an Indian e-commerce payment system and digital wallet company that lets consumers pay for services including prepaid mobile and data services, direct-to-home tv service and toll services.

Problems in the last 24 hours in Mānsa, Gujarat

The chart below shows the number of Paytm reports we have received in the last 24 hours from users in Mānsa, Gujarat and surrounding areas. An outage is declared when the number of reports exceeds the baseline, represented by the red line.

At the moment, we haven't detected any problems at Paytm. Are you experiencing issues or an outage? Leave a message in the comments section!

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 Mānsa, Gujarat

Latest outage, problems and issue reports in Mānsa and nearby locations:

  • gopji13
    ગોપાલ રાઠોડ (@gopji13) reported from Mānsa, Gujarat

    @Paytm Poor service by #paytm.Not satisfied with you.

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

  • sachin_6600
    sachin bansode (@sachin_6600) reported

    @vijayshekhar it will be @Paytm if you were to work harder @vijayshekhar and solve higher problems..

  • urstrulysanni
    Urstrulysanni 🩷 (@urstrulysanni) reported

    Worst service @Paytm

  • Kamaljain9351
    Kamal Jain (@Kamaljain9351) reported

    @PaytmBusiness @Paytm @paytmbankcare I am sending the details with you please check & solve the problem

  • MalviyaNeet
    Busy Customization (@MalviyaNeet) reported

    Very Poor Service Paytm Please Do Not Use @Paytm My Ticket Id : 500011535171 @PhonePe @UPI My contact : 7000039010

  • prafullilani123
    prafullilani (@prafullilani123) reported

    @Paytm @Paytmcare I have yet not recieved any response from u guys apart from 'pls share your numbr'. Kindly dont do anything till I make a video viral on Insta of providing poor service and looting people of hard earned money, and it gets circulated on whole social media #Shame!

  • livingfree60
    Mehul Desai (@livingfree60) reported

    @Paytmcare @vijayshekhar transferred money to upi lite last night,tried to make a payment last night and tgis morning thru upi lite get a message error getting balance. The upi lite icon shows as amount credited. Pl help remedy the situation. The bot in help and customer care doesnt care.

  • rhysnik
    nik (@rhysnik) reported

    @Paytm @Paytmcare This software failure disrupted my finances and caused heavy stress. I demand a proper technical root-cause explanation and compensation for this app security lapse and mental harassment. Fix your broken system and address this accountability now!

  • harleyfoote_
    Harley Lewis Foote (@harleyfoote_) reported

    @Paytm Curious how the refund path is gated here — payment descriptions and customer notes are free text a merchant's customers control, so the model reading them to reconcile is reading strings someone else wrote. Read-only lookups I'd worry less about, but the moment refunds are trigg

  • Techie_Leaf
    Chiranjivi Raj (@Techie_Leaf) reported

    Due to this issue, I switched from @PhonePe to @Paytm .

  • ChinmayaSaxena
    Chinmaya (@ChinmayaSaxena) reported

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