1. Home
  2. ❯
  3. Companies
  4. ❯
  5. Paytm
  6. ❯
  7. Krishnarajanagara Taluk
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 Krishnarajanagara Taluk, 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 Krishnarajanagara Taluk, Karnataka

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

Latest outage, problems and issue reports in Krishnarajanagara Taluk and nearby locations:

Paytm Issues Reports

Latest outage, problems and issue reports in social media:

  • wasim_sayy
    Wasim (@wasim_sayy) reported

    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 close repeatedly without actually processing the closure. 1/3

  • Sharath85852559
    Sharath B (@Sharath85852559) reported

    @Paytmcare Any update still the issue is same @Paytm

  • asksurjeet
    Surjeet Singh (@asksurjeet) reported

    1/5 @Paytmcare What is happening in your system? I’ve been trying to complete device verification for the last 3 days but keep getting “Verification couldn’t be completed – We didn’t receive the verification SMS”. I already have an unlimited recharge pack + extra top-up balance on my number. Still not able to login. Please resolve this urgently.

  • kushal8609
    kushal das (@kushal8609) reported

    @Paytmcare Still problem not resolved.

  • ShrishtiRaii
    Shrishti Rai (@ShrishtiRaii) reported

    @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

  • 1gautambhatia
    Gautam Bhatia (@1gautambhatia) reported

    @Paytmcare help

  • asksurjeet
    Surjeet Singh (@asksurjeet) reported

    1/1 @Paytmcare I’m unable to log in because the OTP is not being received on my registered mobile number. The number is active and working properly on my phone, yet I’ve been facing this issue since yesterday. I’m also seeing a “Daily verification limit reached” message, even though the OTP itself isn’t arriving. Please look into this urgently and help me regain access to my account. #Paytm #OTPIssue

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

  • iSachinJha
    Sachin Kumar Jha - सचिन कुमार झा (@iSachinJha) reported

    @PaytmBusiness @Paytmcare I’ve already provided all requested details via DM, but there’s still no resolution. These FY 2022-23 GST invoices are urgently required for my GST notice response. “We are working on it” is not enough anymore.

  • EmbedLearner
    Embed Learner (@EmbedLearner) reported

    @vijayshekhar Are you working on any LLM at @paytm