UK App Store Steering Fees: Why the Coalition for App Fairness Wants Stronger Rules

Allowing an app to direct a customer to another payment route sounds like a simple change. In practice, the effect depends on the fee, the terms of the link and the experience offered to the customer. That is the central issue in the debate over app store steering in the United Kingdom. The Coalition for App Fairness has argued for restrictions on charges attached to transactions outside the stores, while the Competition and Markets Authority has considered how such charges should be justified.

What steering means

In this debate, steering means allowing a developer to tell users about options outside an app store’s payment route, including a way to complete a purchase elsewhere. The CMA’s June consultation proposed requirements intended to make those options available on fair and reasonable terms. Consultation responses were subsequently published.

The coalition argued that permitting a link would achieve little if restrictive fees continued to remove the commercial benefit. Its publicly available response called for transparent evidence supporting any charges. Those arguments are the position of a stakeholder group; they should not be confused with a final regulatory decision or an instruction that every developer may immediately change its payment arrangements.

A permitted link does not settle the economics

Consider a fictional subscription business comparing two payment routes. The business needs to examine the amount it receives after all applicable charges, not simply whether an external checkout is available. A new fee attached to steering could affect the value of moving a transaction, even if the payment processor itself costs less.

Renewals matter as well as the first purchase. A charge that applies once and a charge that follows every later renewal can produce very different results over a long customer relationship. The relevant comparison therefore includes the conditions of the fee, its duration and how the platform identifies transactions that fall within it.

Evidence is central to the disagreement

The CMA described an evidence-based approach to assessing fair and reasonable steering fees. The coalition’s position emphasised transparent information about the costs of facilitating steering and limits on fees for transactions the platforms do not process. Both formulations put the basis of a charge at the centre of the discussion.

A reader should nevertheless distinguish a proposal from an implemented rule. The evidence reviewed here documents the consultation and stakeholder response. It does not establish a completed enforcement action or a specific approved fee. Developers should consult current official documents before relying on a headline to make a commercial change.

The customer experience can change the result

An external purchase route may involve a browser, another account or different steps for managing a subscription. If the customer cannot understand who is charging them, where to cancel or how to obtain help, an apparently cheaper route can create confusion. The design of the whole journey deserves attention.

For a developer evaluating options, a practical test should follow a customer from the offer through payment, confirmation and later account management. Record where explanations are needed and where the user might become uncertain. A price advantage is more meaningful when the purchase can be completed and supported clearly.

Small teams need a complete cost comparison

A business that operates its own checkout takes responsibility for additional work, even when it uses a payment service. Support enquiries, reconciliation, refunds and account updates must fit into its operating capacity. Those tasks should be considered alongside any change in platform charges.

This is why a regulatory opening does not dictate the best route for every product. A small team may value an integrated process; another may already have a mature customer account system. The important question is which arrangement can be operated reliably at an acceptable total cost for the particular business.

Keep the regulatory questions separate

The debate covers several related issues: the ability to communicate with customers, the terms of an external link and the justification for charges. Treating all three as one simple permission can conceal where the actual restrictions remain. A meaningful update should explain which requirement changed and when it takes effect.

The same distinction applies to different jurisdictions. A development in another market may influence the debate, but it does not automatically establish what a UK developer is permitted to do. Product teams should tie their decisions to the rules and platform terms relevant to their own users and distribution.

What to watch next

The most useful developments will clarify implementation dates, the evidence used to assess fees and how the customer journey may be presented. Those details will matter more to day-to-day operations than a broad claim that steering is either allowed or blocked.

The coalition’s challenge is ultimately about whether choice becomes economically practical. The regulator’s process will determine the applicable requirements. For developers and consumers, the outcome should be assessed through the terms actually implemented, the transparency of charges and the usability of the alternative routes, rather than through a promise of savings that has not yet been demonstrated.

Sources: CMA’s consultation announcement, published consultation responses and CAF’s statement. Business examples are hypothetical editorial analysis.

Originally reported by digitalmusicnews.com. Adapted for our readers.