{"id":52518,"date":"2026-07-03T14:23:46","date_gmt":"2026-07-03T18:23:46","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=52518"},"modified":"2026-07-03T14:23:46","modified_gmt":"2026-07-03T18:23:46","slug":"uk-cma-proposals-for-external-payments-and-nfc","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2026\/07\/03\/uk-cma-proposals-for-external-payments-and-nfc\/","title":{"rendered":"UK CMA Proposals for External Payments and NFC"},"content":{"rendered":"

Ben Lovejoy<\/a>:<\/p>\n

\n

The EU required Apple to permit third-party app stores, while a US court<\/a> ruled that developers have the right to direct iPhone users to third-party payment platforms for app purchases and subscriptions. Britain’s Competition and Markets Authority (CMA) is now proposing to apply this latter rule in the UK.<\/p>\n<\/blockquote>\n\n

Tim Hardwick<\/a> (John Gruber<\/a>):<\/p>\n

\n

The U.K.’s competition regulator has proposed letting app developers direct users to payment options outside Apple’s App Store and Google’s Play Store, in a move aimed at increasing competition and reducing the fees charged by the two companies.<\/p>\n

[…]<\/p>\n

The regulator said any fees Apple and Google charge developers for enabling such “steering” must be fair and reasonable, remain below existing App Store and Play Store commissions, and allow developers to either pass savings on to consumers or reinvest them in innovation.<\/p>\n<\/blockquote>\n\n

John Gruber<\/a> (Mastodon<\/a>):<\/p>\n

\n

Requiring Apple to allow apps to steer users to the web to make payments is, I’ve long argued<\/a>, sensible regulation. I’ve also long argued<\/a> that Apple has been obstinate in disallowing it. If in-app payments — through Apple’s system — can’t compete with out-of-app payments on the web, something is wrong with IAP. But it’s wrong to assume that payments outside IAP will result in lower prices and better policies for users.<\/p>\n<\/blockquote>\n\n

Nick Heer<\/a>:<\/p>\n

\n

They may increase prices when costs grow<\/a> but that does not mean they do the opposite. But who cares? Lower costs permit more flexibility on pricing and, even if that money ends up in the pockets of developers instead of Apple, is that supposed to be a bad thing? Is there a reason why someone should be upset that they might pay the same amount but an indie developer gets to keep more of it?<\/p>\n

The proposed policies<\/a> are pretty straightforward from what I can see. Among other obligations, Apple is not allowed to use or require scare tactics<\/a> when users are routed to an external payment mechanism and, while it is allowed to charge a steering fee, it is not allowed to count services not used by developers offering third-payments nor double-count for services already accounted for by other developer fees. Also, the CMA calls bullshit on Apple’s claim that third-party payments are particularly risky[…]<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n