The short answer
The rules against dark patterns in India stopped being advisory in 2026. The Central Consumer Protection Authority penalised nine digital platforms in an action disclosed in August 2026, with penalties totalling close to 20 lakh rupees, for exactly the interface decisions that most growth teams treat as conversion tactics: charges added at the last step, pre-ticked add-ons, and buttons that shame the customer for declining.
The penalties themselves are small. What matters is that the regulator can act on its own motion, without a consumer complaint, and that the practices it named are present in a large share of Indian checkouts today.
What counts as a dark pattern
The CCPA's 2023 guidelines define a dark pattern as an interface designed to mislead or trick users into decisions they would not otherwise make, by subverting or impairing consumer autonomy. Thirteen patterns are named: false urgency, basket sneaking, confirm shaming, forced action, subscription trap, interface interference, bait and switch, drip pricing, disguised advertisement, nagging, trick question, SaaS billing, and rogue malware.
A June 2025 advisory told platforms to self-audit within three months and remove them. Uptake was thin — by the regulator's own account very few companies completed and published an independent audit — and enforcement followed.
The 2026 enforcement, and what each case teaches
The cases are more instructive than the fines, because each one maps to a pattern that a designer or growth manager chose deliberately.
- Drip pricing. Zepto Marketplace was penalised 7 lakh rupees over handling charges and membership fees that appeared during checkout rather than with the displayed price. The test is simple: if the number at the top is not the number at the end, the difference has to be visible before the customer commits.
- Basket sneaking. BookMyShow was penalised over a pre-ticked one rupee contribution to a charitable initiative. The amount is trivial; the consent is the point. Anything added to a cart that the customer did not choose is caught, however small and however good the cause.
- Confirm shaming. IndiGo changed its app interface after the regulator objected to an opt-out message written to make declining feel like a failure. "No thanks, I don't care about saving money" is a copy decision, and it is now a regulated one.
Others in the group were penalised over subscription traps and misleading prompts. Read together, the action is a statement that the regulator will treat interface copy and default states as consumer protection matters, not as design taste.
The thirteen patterns, translated into interface decisions
The legal names are abstract. Here is what each looks like in a build, which is the form a design or engineering team can actually act on.
| Pattern | What it looks like in the interface |
|---|---|
| False urgency | Countdowns that reset, "only 2 left" that is not stock-linked |
| Basket sneaking | Pre-ticked insurance, donations, warranties, memberships |
| Confirm shaming | Decline buttons written to embarrass |
| Forced action | Requiring an account, app install or subscription to complete an unrelated task |
| Subscription trap | One-click sign-up, multi-step cancellation, no in-app cancel path |
| Interface interference | Greyed-out real choices, misleading X buttons, disguised hierarchy |
| Bait and switch | Advertised item unavailable, substitute pushed at a higher price |
| Drip pricing | Fees, handling charges or convenience charges revealed late |
| Disguised advertisement | Sponsored results styled as organic listings or editorial |
| Nagging | Repeated prompts for permissions or upsells after refusal |
| Trick question | Double negatives and confusing consent wording |
| SaaS billing | Silent renewals and unrequested plan escalation |
| Rogue malware | Fake system warnings pushing installs |
The uncomfortable part: several of these are in your conversion playbook
Most Indian e-commerce teams did not set out to deceive anyone. They inherited patterns from A/B tests that moved a number. Urgency banners lift add-to-cart. Pre-ticked add-ons lift average order value. A difficult cancellation lifts retention on a dashboard, for one quarter.
What those tests do not measure is the refund, the chargeback, the one-star review, and now the regulatory file. We made the conversion-side argument in why customers abandon checkout: surprise costs at the final step are the single most cited reason people leave a cart. The compliance case and the commercial case point the same way, which is unusual and worth using internally.
How to audit your own site
Do it as a walkthrough, not a document review. Open your site in a private window, on a phone, as someone who has never bought from you, and record the screen.
- Note the price you first see and the price you are asked to pay. Every rupee of difference must have appeared before the payment step.
- Screenshot every checkbox before you touch it. Anything pre-selected that adds cost is a finding.
- Read every decline button aloud. If it sounds like a judgement, rewrite it.
- Try to cancel a subscription from a phone. Count the steps against the number it took to subscribe.
- Check that sponsored placements are labelled in a way a hurried person notices.
- Verify that every urgency claim is driven by real data, and switch off any that is decoration.
- Record the date, the findings and the fixes. An audit you cannot evidence is not much use when asked.
For most sites this is a day of work and a short sprint of changes. For a few, it surfaces a business model built on a default nobody wants to give up, and that is a conversation for the founder rather than the design team.
Where this is heading
Dark patterns have become one of the more actively enforced corners of Indian consumer law, and the direction of travel includes periodic audit expectations rather than one-off advisories. Alongside the DPDP consent requirements arriving in November 2026, the practical effect is that consent, pricing clarity and cancellation flows are all becoming things a business has to be able to show, not just claim.
The studio version of this advice is simple. Design the flow you would be comfortable explaining to the customer afterwards, price it in one number, and let the product do the persuading. If you want a second pair of eyes on a checkout before a regulator provides one, send us the flow.