Apple has updated its developer license agreement with language that allows the company to recover unpaid amounts it says it is owed by developers—potentially by deducting those funds from future revenue streams the App Store processes on a developer’s behalf.
The change, first reported by TechCrunch, centers on how Apple can collect commissions, fees, or other charges when developers use external payment systems in markets where local law permits links or alternative payment options. Under those regimes, developers may be required to report external payment activity back to Apple so the company can assess what it believes is due.
What changed in Apple’s developer agreement
In the updated agreement, Apple says it may “offset or recoup” unpaid amounts, including “any amounts collected by Apple on your behalf from end-users.” In practice, that means the company could recover money by subtracting it from proceeds tied to in-app purchases—such as subscriptions, digital goods, and services—or from revenue generated through paid app downloads.
The agreement also states Apple can collect these amounts “at any time” and “from time to time,” language that signals deductions could occur without a predictable schedule. For developers, that introduces the possibility of unexpected adjustments to payouts if Apple determines prior reporting was inaccurate or incomplete.
Notably, the text does not spell out the precise methodology Apple will use to determine whether a developer underreported earnings or miscalculated fees. That ambiguity could become a flashpoint for developers who want clearer standards and dispute-resolution timelines when money is withheld.
Why external payments are driving the issue
The policy shift matters most in regions where regulators or courts have pushed Apple to allow developers to route customers to external payment methods. When payments happen outside the App Store’s own checkout, Apple may still claim entitlement to a commission or other fee—depending on the jurisdiction’s rules and the specific business terms under which an app operates.
According to the report, the updated agreement could affect developers in markets including the European Union, the United States, and Japan, where the ability to use external payment systems has been expanding or is under active debate. The result is a more complex compliance burden: developers must track external transactions, report them accurately, and reconcile what they owe under local rules—while Apple reserves the right to collect shortfalls through deductions.
The U.S. commission dispute is still unsettled
In the U.S., the legality and scope of commissions on externally processed payments remains contested. As cited in the report, a federal appeals court earlier this month said a district court should consider allowing Apple to collect some commission, though not necessarily the full 27% fee the company previously sought in certain scenarios. That ongoing uncertainty makes the new contractual language especially consequential: it sets up a mechanism for collection even as the boundaries of what can be collected are still being argued.
How Apple could collect: deductions and broader account reach
Beyond allowing deductions from future App Store proceeds, the updated agreement expands the scope of where Apple may seek repayment. The company also says it can collect unpaid amounts from “affiliates, parents, or subsidiaries” connected to the developer account that owes money.
Practically, that could mean a developer with multiple apps—or a corporate group with several publishing entities—could see deductions applied across related accounts. For companies operating portfolios of apps, this raises the stakes of internal reporting controls: a dispute or miscalculation tied to one product could affect revenue flows for others.
The report notes the changes appear in Schedules 2 and 3, section 3.4, which addresses the delivery of applications to end users. While this may read like a technical contractual update, it has direct implications for cash flow and financial planning, especially for subscription-heavy businesses where payout timing is critical.
EU fees: from Core Technology Fee to Core Technology Commission
The agreement update arrives as Apple continues to evolve its European compliance framework. Among the variable costs developers may face is the EU’s Core Technology Fee (CTF), currently set at €0.50 for each first annual install beyond one million over the prior 12 months, according to the report.
Starting in January 2026, Apple plans to transition from the CTF to a new structure called the Core Technology Commission (CTC), described as a more complicated percentage-based fee. The report indicates Apple will collect the CTC from apps that use external payment methods or that operate under alternative business terms in the EU.
For developers, the combination of evolving fee structures and expanded collection mechanisms could increase the need for rigorous forecasting and audit-ready transaction records—particularly for apps that straddle multiple compliance models across countries.
What developers should watch next
While Apple frames the change as a way to recover unpaid amounts, developers are likely to focus on operational questions the agreement does not fully answer, including:
- How Apple will calculate alleged underreporting and what data it will rely on
- What notice, if any, developers will receive before deductions occur
- How disputes will be handled when developers disagree with the amount claimed
- Whether deductions could affect multiple apps or related entities through affiliate collection
As regulators continue to reshape app marketplace rules globally, the practical battleground is increasingly contractual: the fine print that governs reporting, commissions, and enforcement. With this update, Apple is signaling it intends to maintain collection leverage even as payment flows move beyond the App Store’s checkout.