Groww app discrepancy: SEBI settlements, complaint steps

Why Groww app “profit” screenshots went viral

Retail investors on Reddit and X have been sharing screenshots of unusual profits and balances on the Groww app. Some posts claim investments appeared as “invested” but could not be withdrawn. Others focused on sudden jumps in portfolio value that looked too large to be real. The conversations also pulled in older regulatory headlines about SEBI settlements involving Groww. Many users connected these threads to question platform controls and reporting accuracy. The discussion intensified because the screenshots were easy to circulate and difficult to verify quickly. Several posts framed the issue as a “settlement discrepancy” and a “profit settlement” problem. The core theme across posts is not pricing alone, but confidence in ledger and transaction reconciliation.

What Groww said about withdrawal and reconciliation issues

In one widely shared case, an investor alleged that money was deducted and investments were stuck. Groww responded on social media that no deduction occurred and the mutual fund transaction did not take place. Groww also stated that no fraudulent activity had taken place in that incident. According to Groww, the account showed an incorrect investment due to a reconciliation issue. The company also asked the user to share registered details or a ticket ID for support follow-up. A support message asked users to DM or email support@groww.in and share the ticket ID publicly. These responses positioned the issue as incorrect display or reconciliation rather than fund loss. The public back-and-forth, however, still fed concerns about how quickly such mismatches are detected and corrected.

The January 2024 price-discrepancy glitch and GTT triggers

A separate incident that resurfaced in these threads relates to a reported technical glitch in stock prices. Groww said some users observed a discrepancy in stock prices and that it was temporary and resolved. Users reported seeing investments like Rs 1,000 displayed as Rs 1,00,000, creating confusion. Reports described profits appearing to rise by more than 10,000 percent for a short period. The same reporting said some users looked like “millionaires” temporarily, while others saw sharply reduced values. Groww stated that if any GTT (good till triggered) orders were triggered due to this, support teams were reaching out with a resolution. The company asked affected users to DM its support handle on X. Social media discussions now treat this episode as an example of how display or pricing glitches can spill into order execution risks.

SEBI settlement 1: Rs 47.85 lakh for broker-rule lapses

Alongside user complaints, posts also highlighted that SEBI settled a case with Groww Invest Tech. The settlement amount cited across reports is Rs 47.85 lakh, with a payment date of February 21, 2025. SEBI’s process referenced a High Powered Advisory Committee recommending the settlement. Reporting also described the case as linked to regulatory violations flagged during a detailed inspection. Allegations and observations cited include faulty ledger entries and issues linked to anti-money laundering (AML) controls. Another cited area was the provision of risky non-broking services. SEBI also alleged violations of stock broker rules, securities contracts regulation provisions, and circulars. One specific observation mentioned retention statements containing incorrect information, including discrepancies in financial ledger balance and margin obligation in 38 instances.

SEBI settlement 2: Rs 34.12 lakh linked to glitch handling

A second SEBI settlement discussed online is for Rs 34.12 lakh. Posts state the revised settlement terms were submitted on February 7, 2025. The settlement payment date cited is March 13, 2025. This case is described in reports as pertaining to alleged failure to handle a technical glitch in January 2024. The advisory committee reviewed the terms and recommended the settlement amount, which was then accepted. Both settlements are described as being concluded without Groww admitting or denying guilt, which is commonly noted in settlement reporting. Social media users often combine the two settlements into a single narrative about product reliability and compliance. The combined total cited for the two settlements is Rs 82,97,500.

Timeline table: key dates, amounts, and what was alleged

The details circulating online mix official settlement reporting with user experience posts. A clear timeline helps separate what is dated from what is anecdotal. Below is a table of the two SEBI settlements and the user-facing glitch episode referenced in those discussions. The table reflects only the dates and descriptions shared in the trending context. It does not establish causality between the user issues and the regulatory matters. It also does not quantify the number of affected users in the app incidents. Readers should treat screenshots as unverified unless backed by statements and documents. The regulatory entries are anchored to settlement amounts and dates that were widely quoted.

How to complain: start with Groww, then SEBI SCORES

Several posts also shared a step-by-step redress path for users who believe they faced a discrepancy. The first step is to complain to Groww directly, described as a regulatory requirement before escalating. The in-app route shared is Profile - Help & Support - Raise a Ticket. Users are advised to keep screenshots of transactions and any error screens. The next step highlighted is filing a complaint on SEBI’s SCORES, which stands for SEBI Complaints Redress System. The process shared includes selecting the category “Stock Broker” and choosing the entity name. It also asks users to upload supporting documents like screenshots, email correspondence, and bank statements showing deductions, with files in PDF format and a stated 2MB limit per document. Social media guides stress that precise documentation matters, especially where the issue is about display versus actual debit.

Other channels mentioned: consumer court and documentation

Beyond SCORES, posts referenced additional complaint channels, though the details were not fully expanded. They also mentioned legal action through consumer court in the District Consumer Forum. The shared threshold for claims in that route is up to Rs 1 crore. Users discussing consumer court also emphasized keeping a full paper trail across app tickets and emails. In the viral withdrawal allegation, Groww’s response focused on “no deduction” and “transaction did not take place,” so bank records were repeatedly mentioned as key proof. Where GTT triggers are involved, users tend to collect order logs and timestamps. If the issue is a reconciliation mismatch, screenshots alone may not show the underlying ledger state. Several posts also advised capturing broker contract notes and ledger statements where available. The broader takeaway from these threads is that escalation is procedural, and the first response is expected to come via the broker’s own support workflow.

What the Zerodha vs Groww profit debate adds, and what it does not

The same threads also carried comparisons between Zerodha and Groww profitability. One set of posts claimed Zerodha made Rs 5,500 crore profit “last year” and that its net profit in 2024 was Rs 5,496 crore on revenue of Rs 9,372 crore. The same posts claimed Groww had revenue of Rs 3,145 crore, operating profit of Rs 536 crore, and a loss of Rs 800 crore due to a one-time tax payment. They also claimed Zerodha makes around Rs 8,000 profit per user versus less than Rs 500 for Groww. These figures were presented as a social media “deep-dive,” not as a regulatory filing in the shared context. Importantly, profitability comparisons do not directly validate or disprove an app-level discrepancy claim. They do explain why discussions can become polarized, with users linking business performance to perceived service quality. For a user dealing with a mismatch, the immediate question remains narrower: what the ledger shows, what the bank statement shows, and what the broker confirms in writing.