The Umbrella

Consumer Behaviour

The Conversion That Costs You Trust: India’s Dark-Pattern Reckoning

A 2026 CCPA case shows why defaults matter. Review pricing, consent, optional additions and cancellation through the choices customers actually experience.

In this article
  1. A 2026 case makes the issue concrete
  2. The Indian framework predates that case
  3. Persuasion should leave the choice intelligible
  4. Conversion metrics can reward the wrong thing
  5. Review the journey as a first-time customer
  6. Five places to inspect carefully
  7. Make the price understandable before the commitment
  8. Check the words that accompany refusal
  9. Assign responsibility beyond the designer
  10. Test improvements without making deception a test arm
  11. Trust has an operational form
  12. The useful question for your next release
  13. Sources & Further Reading

A customer clicks “continue” and discovers that continuing also meant joining a programme, accepting promotional messages or buying something they did not choose.

The interface may have improved a short-term conversion metric. It has also made the meaning of a click less trustworthy.

Dark patterns deserve attention from Indian business owners because they sit at the junction of design, customer autonomy and commercial measurement. The question is not merely whether a page converts. It is whether customers understand the choice they are making and whether the business can stand behind it.

This article examines official Indian guidance and a 2026 enforcement example, then proposes a practical design review. It is editorial analysis rather than a legal opinion on a particular website.

A 2026 case makes the issue concrete

In a 17 July 2026 release, the government reported that the Central Consumer Protection Authority imposed a ₹1 lakh penalty on SpiceJet for dark patterns on its booking platform. The authority described automatic loyalty-programme enrolment and default promotional consent through pre-ticked choices. The release also records SpiceJet's explanation that the issue arose from a technical error.

The authority identified forced action, interface interference and confusing consent language. This is a report of that authority's findings and the company's stated explanation, not our independent adjudication or a claim about every booking on the platform.

The useful design lesson is tangible. A default can perform a commercial action before the customer has deliberately chosen it. Correcting the wording while preserving that behaviour may leave the underlying problem intact.

The Indian framework predates that case

A July 2025 government explanation says the CCPA issued its Guidelines for Prevention and Regulation of Dark Patterns on 30 November 2023, identifying 13 specified patterns. It also describes the June 2025 advisory asking ecommerce platforms to conduct self-audits and address deceptive practices.

Examples named in the official explanation include false urgency, basket sneaking, drip pricing and subscription traps. Read the actual guidelines and applicable rules for a formal compliance assessment; this article does not reproduce every definition or determine the legal status of an individual design.

For owners, the practical implication is that interface choices deserve business oversight. A checkout template or plugin does not become acceptable simply because it arrived as a popular default.

Persuasion should leave the choice intelligible

A clear product comparison can help someone choose. A genuine deadline can inform a decision. A recommendation can be useful if its basis and commercial relationship are understandable.

The problem arises when the interface obscures costs, misrepresents availability or makes the user's intended action difficult to execute. The design begins to serve the seller by reducing the customer's ability to choose deliberately.

Consider a hypothetical subscription checkout. Explaining that an annual plan costs less per month is informative if the total payment and renewal terms are visible. Making the monthly option hard to find while displaying only an annualised monthly equivalent can create confusion.

The example is a design scenario, not a legal finding about any specific company. Its purpose is to identify what a reviewer should ask: what will the customer reasonably believe, and does the actual transaction match that belief?

Conversion metrics can reward the wrong thing

If a report counts every completed purchase as equally successful, a confusing interface can look effective until refunds, support calls and customer dissatisfaction appear elsewhere.

The team responsible for the page may never see those costs. Marketing owns the conversion rate, support owns complaints and finance owns refunds. Each dashboard tells a partial story.

Bring the records together. Examine cancellation reasons, unexpected charges, difficulty opting out and customers who say they did not intend the action. These signals require investigation; they are not automatic proof of unlawful design.

A business should define a successful conversion as an informed, suitable action that it can fulfil. That is an editorial management recommendation, but it gives the measurement system a more useful objective.

A customer who correctly decides that an offer is unsuitable has not necessarily suffered a failed user experience. The interface helped them avoid the wrong purchase.

Review the journey as a first-time customer

Start outside the business's own account. Follow the advertisement, inspect the offer, add an item, examine charges and attempt to leave. Use ordinary phones as well as a large desktop screen.

At each step, write down what you believe will happen next. Compare that expectation with what actually happens. Familiarity is a serious obstacle here: employees may know the missing explanation so well that they no longer notice its absence.

Include someone who did not design the flow. Ask them to explain the total price, optional choices and next obligation without coaching. If the answer is wrong, investigate the interface before blaming the person.

Test error and cancellation paths too. A business can make purchasing simple while making correction bewildering. The customer experiences both as part of the same promise.

Five places to inspect carefully

AreaReview questionA clearer design direction
Optional additionsDid the customer deliberately choose this?Separate choices with understandable labels
Price disclosureCan the buyer identify the payable total?Show costs clearly before commitment
UrgencyIs the deadline or scarcity claim supported?Use accurate limits and remove false pressure
Subscription termsAre renewal and cancellation understandable?Explain obligations near the decision
ConsentDoes the action reflect an affirmative choice?Review defaults, wording and behaviour together

These are review prompts, not a complete compliance checklist. The final solution depends on the product, jurisdiction and applicable requirements.

Document the actual behaviour rather than merely collecting screenshots of the intended design. A checkbox can look unselected in a mockup and arrive selected in production.

Make the price understandable before the commitment

A customer should be able to compare the offer using the relevant total and terms. If mandatory charges appear only after substantial effort, the earlier price may have given a misleading impression.

For a hypothetical service package, explain what the quoted amount includes and which costs depend on a later assessment. Some businesses cannot know the final price before inspecting the work. They can still explain the uncertainty honestly.

Do not present an estimate as a fixed price or a base fee as an all-inclusive amount. Label the basis and the condition that changes it.

The same principle applies to marketing your own services. Our cost guide separates production, management and media spend because a single headline number can hide meaningful differences in scope.

Clarity might reduce unsuitable enquiries. That can be beneficial if the remaining conversations are better informed and easier to serve. Measure the whole result rather than treating every lost click as damage.

Check the words that accompany refusal

A customer declining an optional offer should not have to accept a misleading or insulting statement about themselves. The design can describe the consequence plainly.

Compare hypothetical labels such as “Continue without the add-on” and “No, I do not care about protecting my purchase.” The second tries to turn refusal into an uncomfortable self-description.

The exact legal classification requires the applicable definition and context. As an editorial design judgement, the first is easier to defend because it explains the action without shaming the user.

Also check repeated prompts. A customer who has clearly declined should not need to negotiate with the interface on every subsequent screen. Determine when a prompt is genuinely helpful and when it merely wears down resistance.

These details are small enough to overlook in a campaign meeting and large enough to shape the customer's impression of the business.

Keep evidence of the approved behaviour and test it after configuration changes. A release can unintentionally restore a default or obscure a price. The relevant record is what the customer actually encountered, not only what a designer intended during the original review.

Assign responsibility beyond the designer

The owner, product manager, marketer and developer all influence the journey. A brief that demands more conversions without boundaries can create pressure for manipulative choices even if nobody explicitly asks for them.

Write the boundaries into the acceptance criteria. Specify how optional additions, pricing, consent and cancellation should behave. Have the person responsible for compliance review the relevant requirements.

When a third-party tool provides the flow, inspect its configuration and rendered behaviour. Record the version and settings used. Do not assume that the vendor's claims settle your responsibilities.

Create a route for employees to flag confusing experiences. Support staff often hear about misunderstandings before the design team sees them. Their records can reveal the distance between intended and experienced behaviour.

Test improvements without making deception a test arm

A business can compare clear explanations, layout and wording while preserving truthful choices in every version. There is no need to retain a known misleading design simply to establish whether it converts better.

Measure completed suitable purchases, support burden, cancellations and customer understanding. Define the observation period and acknowledge changes in traffic or offers that affect interpretation.

If clearer terms reduce checkout completion, examine who leaves and why. Some customers may be discovering an obligation they would previously have missed. That is a different result from a technical failure preventing willing buyers from paying.

The commercial objective remains legitimate: help suitable customers act confidently. A design review should improve that process, not make the page deliberately difficult or bury useful information under legal language.

Trust has an operational form

It is tempting to discuss trust as a brand feeling. In a checkout, trust has practical components: the amount is what the customer expected, the optional item is genuinely optional, and leaving the arrangement works as described.

A polished visual identity cannot compensate for a transaction that contradicts it. Nor can a warm support message undo every cost of an avoidable misunderstanding.

Our article on Indian-language customer journeys adds another dimension. A choice is not meaningfully clear merely because the business understands the language in which it is written.

The useful question for your next release

Before approving a conversion-focused change, ask someone to complete the journey and explain the bargain back to you. What are they buying, what will they pay, what is optional and what happens next?

If their answer differs from the actual transaction, the design needs work. The result may expose a technical bug, an unclear offer or a deliberate pressure tactic. Each requires a different remedy, but none should hide behind an attractive conversion rate.

The Umbrella can help connect brand promises and digital experiences. If your checkout is generating complaints that your campaign report does not show, bring the journey and the complaint themes. The customer should understand the same agreement your business thinks it is making.

Sources & Further Reading