On 3 November 2026 the Supreme Court of India, in a bench of Justices PS Narasimha and Alok Aradhe, heard Indian app developers including Matrimony.com challenge Google Play's billing rules. The judges asked three practical questions. Can developers opt out of Google's payment system? Did the Competition Commission of India (CCI) examine the specific fee clauses? Was the disputed clause part of the original agreement? Google, through Sajan Poovayya, argued that the developers were recasting a competition dispute as a contract dispute to get around the CCI's findings, noting that the CCI had already found the fees neither unreasonable nor excessive. Developers counter that the rules conflict with the Payment and Settlement Systems Act, 2007. The matter returns on 1 December 2026.
The strongest case for Google
Google's position deserves a fair statement. A platform that builds the store, the security review, the payments rails and the discovery tools incurs real costs, and it is entitled to charge for them. Bundling a payment system with distribution is common across the industry, and developers signed the terms voluntarily. If every commercial term that a developer dislikes became a regulatory dispute, platform investment would suffer and courts would become price-setting bodies. That is a serious argument, and it is the reason this dispute should not be decided by generalised hostility to Big Tech.
What the record already shows
The regulatory record is more specific than a contract dispute. The CCI issued its combined order on 25 October 2022 in three cases: 07 of 2020, 14 of 2021 and 35 of 2021, against Alphabet Inc. and others. The appellate tribunal, NCLAT, ruled on 28 March 2025. It upheld the finding that mandatory use of the Google Play Billing System for paid apps and in-app purchases was one-sided and arbitrary, and lacked a legitimate business interest. That is a Section 4(2)(a)(i) abuse-of-dominance finding.
NCLAT also narrowed the case. It cut the penalty from Rs 936.44 crore to Rs 216.69 crore, calculated on Google Play's relevant turnover instead of Google's global turnover. It did not uphold the findings under Sections 4(2)(a)(ii) or 4(2)(c), and it found no denial of market access. It held that the CCI could not issue the ex-ante directions. The Supreme Court admitted cross-appeals from Google, the CCI and the Alliance Digital India Foundation in August 2025.
The pattern is useful. Competition law has already produced a reasoned, evidence-based, and proportionate outcome. The tying of billing was found abusive, the penalty was trimmed to the relevant market, and speculative remedies were pared back.
Why the Payments Act is the wrong lever
Developers argue that Google's billing conflicts with the Payment and Settlement Systems Act, 2007. Section 4 of that Act provides that, as the Reserve Bank of India describes it, no person other than the RBI can commence or operate a payment system in India unless authorised by the RBI. This is a licensing and systemic-stability statute. It asks who may run a payment system, not whether a dominant platform may force developers to use its own.
Stretching it to cover app-store fee design carries risk. If the Court holds that a payment-licensing law governs commercial billing terms, it could pull a wide range of platforms, marketplaces and developer ecosystems into licensing questions that Parliament did not address. Developers would also gain little. A licensing finding would not tell Google what a fair, cost-justified fee looks like, and it would leave the actual competition concern unresolved.
The hearing's real question: opt-out
The bench's first question, whether developers can opt out, is the correct one. Competitive harm in billing arises from compulsion, not from the existence of a Google payment system. Google has said, and the reported contract framing suggests, that terms were agreed. But the earlier litigation shows how little leverage developers had. After the Supreme Court refused interim relief in early 2024, Google removed apps of developers that had not paid under its new billing policy. A term accepted because the alternative is delisting is not much evidence of a bargain.
There is also a procedural history. The Madras High Court dismissed 14 of 16 petitions by Indian startups, including Matrimony, in 2023, holding the suits barred by Section 61 of the Competition Act. That route sent developers to the CCI, which is why the CCI's treatment of the specific fee clauses matters now. If the Court finds the CCI never examined the fee levels, the proper remedy is a remand to the competition authorities, not a new payments-law theory.
What a proportionate outcome looks like
- Keep the abuse finding narrow and evidence-based. Uphold the tying finding, which is well supported, and avoid broad statements on all platform fees.
- Test fees against cost and alternatives. A fee of up to 30% sits against roughly 2.35% reported for YouTube's separate payment processor in the NCLAT record. That gap invites scrutiny but is not itself proof of abuse; the CCI should examine what the fee actually pays for.
- Guarantee a genuine opt-out. Developers who can use third-party billing, with Google charging only for demonstrable distribution services, preserve both platform incentives and developer choice.
- Avoid the Payments Act as a competition tool. Using the wrong statute creates uncertainty for the whole digital economy.
A clear ruling on 1 December or after would give India's developers and platforms something they currently lack: a predictable rule for how much a dominant app store may charge, and on what terms. Contract law alone cannot supply that when one party sets the terms and controls access to the market.