/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Apple updates its App Store rules in the Netherlands to let Dutch dating apps take payments through third-party processors, but a 27% commission still applies

But they can't avoid giving up a 27 percent commission  —  To help bring an end to wrangling with Dutch regulators that stretched …

The Verge Richard Lawler

Context & Ripple Effects

Apple’s change follows the Dutch order that required alternative payment options for dating apps, after which Apple outlined a 27% commission for alternative-payment transactions. The new rules implement that payment choice while preserving nearly all of Apple’s usual in-app purchase take rate.

The dispute was about more than the availability of another processor: Apple had maintained that its earlier Dutch approach required only a minor technical change. Retaining the 27% fee keeps the commercial terms central to the regulator-driven change.

First-order effects

  • Dutch dating-app developers can use third-party payment processors, but Apple still collects a 27% commission on those transactions.
  • Apple gives the affected developers a payment-routing option without materially surrendering its App Store revenue share.

Second-order effects

  • Third-party processors gain access to Dutch dating-app transactions, but their fees must fit alongside Apple’s 27% charge, limiting the economic room for developers to switch.
  • The Dutch ACM’s response becomes decisive for Apple: acceptance would validate a compliance model that preserves Apple’s take rate while changing the payment mechanism.

Third-order effects

  • If this model is accepted, platform-payment remedies may increasingly separate payment choice from platform compensation, leaving gatekeepers able to retain substantial transaction fees after opening processing.
  • The case points to regulatory scrutiny shifting from whether an alternative payment rail exists to whether the resulting fee structure creates meaningful competitive choice for developers.

The trend: App-store regulation is moving toward mandated payment optionality, while platform owners seek to preserve their economics through regulated take rates.

Discussion

  • @stroughtonsmith Steve Troughton-Smith on x
    No change to Apple's grotesque 27% tax on external payments it has nothing to do with, nor on its demand of audit rights for your company
  • @eric_seufert Eric Seufert on x
    Apple has softened its requirements for the use of off-platform payments for Dating Apps in the Netherlands. A separate app binary is no longer required, and the language of the pop-up notification modal has been changed https://developer.apple.com/ ...
  • @stroughtonsmith Steve Troughton-Smith on x
    Fun loophole in Apple's ‘dating apps in the Netherlands’ policy: “[devs] using these entitlements will be required to provide [every transaction] that has been facilitated through the App Store” However, external link policy prohibits parameters & only allows for a single link
  • @stroughtonsmith Steve Troughton-Smith on x
    So depending on your reporting/analytics practices and how you choose to implement this, you may have no data whatsoever as to whether a transaction has been facilitated by the App Store, or whether it was generated outside of the App Store 🙃
  • @mekentosj Alexander Griekspoor on x
    @reneritchie Excuse my French but what the F is with Apple and it having invented reader apps as some completely arbitrary category of apps in attempt to take the most vocal/influential criticasters off the table. What a bollocks. Sorry, but this is exactly why I cheer for the EU…
  • @baekdal Thomas Baekdal on x
    Can I just point out how ridicules it is that we should somehow be amazed by this. This should never have been something Apple had the power to allow or disallow. https://twitter.com/...
  • @mekentosj Alexander Griekspoor on x
    @reneritchie My problem has never been with margin or paying Apple, in fact I happily pay the fees given how much business they bring. The issue is with the arbitrary categories and rules, the gatekeeper/monopoly, curbing of innovation etc. For example, how does Facebook pay for …
  • @reneritchie Rene Ritchie on x
    @mekentosj I feel you. I've always said the only way to know if it's hurting innovation is to see if there's a major category of apps that grow on Google Play but are disallowed on App Store. That's just started to happen with game streaming services...
  • @reneritchie Rene Ritchie on x
    Normal apps, 70/30 (or whatever) creator/Apple works Normal service, 70/30 (or whatever) creator/service works “Reader apps” (I.e. double aggregators), 70/30/30 creator/service/Apple (or whatever) is impossible Hence years of arguments, deals, carve-outs, drama, etc. https://twit…
  • @reneritchie Rene Ritchie on x
    @mekentosj “Reader apps” are unique in that they have double brokers involved. Just like Apple aggregates apps for the App Store, they aggregate books or music or shows or whatever. 30/30/70 is impossible, so either Apple has to give up its cut, or the service has to, so they arg…
  • @reneritchie Rene Ritchie on x
    https://developer.apple.com/ ... - Distributing “reader” apps with a link to your website - Requesting the External Link Account Entitlement - Configuring and enabling the entitlement in Xcode - Understanding app and link requirements - Implementing the in-app modal sheet - Etc