Ninth Circuit sends Epic v Apple back to Judge Gonzalez Rogers: the link-out fee and your web shop
By UA Ledger staff — Archive date: 3 min read

The Ninth Circuit reversed the stay in Epic v Apple, sending the link-out fee question back to the district court. What that leaves open for a web shop.
The Ninth Circuit reversed the stay in Epic v Apple today and sent the case back to Judge Yvonne Gonzalez Rogers, the district judge who found Apple in contempt of her original injunction. Her task now: work out exactly what fees, if any, Apple can charge developers who link users out to an external payment page. Apple is separately preparing a Supreme Court petition, so this is not the end of the dispute. It is a return to the judge most familiar with it, while the bigger question sits in a longer queue.
The link-out fee: what actually changed today
Nothing in the mechanics of a US link-out changed on April 28. Developers in the US have been able to direct users to external payment pages without Apple's standard commission since the original contempt ruling. What changed is procedural: the appeals court removed the pause that had left some of the enforcement mechanics unsettled while Apple's appeal was pending, and handed the specific fee question back to the district court rather than resolving it itself.
That distinction matters for anyone running a web shop off the back of the ruling. Judge Gonzalez Rogers now has a live mandate to determine what, if anything, Apple can charge on external transactions. Apple has signalled in other filings that it does not accept the current no-commission state as final, and the Supreme Court route is explicitly aimed at revisiting that.
What this means for a buyer's web shop plan
A UA team that has built or is building a web shop funnel around US link-outs should treat the current terms as provisional, not settled policy. Three practical points follow.
First, do not architect a permanent pricing model around a zero-commission assumption. If Judge Gonzalez Rogers or a subsequent appeal reinstates some form of fee on link-out transactions, margin assumptions built into a web shop's pricing need to be able to absorb that without a scramble.
Second, keep the compliance surface area small. The narrower and more literal a developer's implementation of the injunction's actual text, the less exposed it is if the standard tightens. Apple's own argument, made elsewhere in this litigation, is that it never violated the injunction's text even when found in contempt, which suggests the company will keep testing the boundary of what "compliant" means.
Third, watch Apple's own Supreme Court bid, which the company is pursuing on a narrow procedural question about the contempt finding rather than the underlying commission dispute. A narrow question can still produce a broad-sounding headline. Read any Supreme Court development for the actual scope of the question being reviewed, not the framing in the first paragraph of coverage.
None of this is a reason to pause a web shop build. It is a reason to build the pricing and technical architecture so that a less favourable fee ruling is an adjustment, not a rebuild.
Related archive reading
These articles provide related context and remain subject to their stated review status.
Featured
Related posts
More from the Platforms desk
platforms
·Archive date: 4 min read
Roblox Everywhere: when a platform ships standalone apps, it competes for your installs
measurement
platforms
·2 min read
AppLovin Ad Review drops user-level journeys for aggregate-only reporting
measurement
platforms
·2 min read
Apple adds an EU alternative ATT prompt from iOS 27.2 — mandatory in five markets
platforms
·1 min read