/
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 clarifies it will still collect a commission from Dutch developers using third-party payments; Google will too in South Korea, just lowering its fee by 4%

Mobile Dev Memo Eric Benjamin Seufert

Context & Ripple Effects

Earlier court coverage had already identified that developers using their own payment methods might still face an Apple commission. This report shows that opening payment choice does not necessarily remove the platform’s take rate.

Apple and Google are responding through different country-specific terms: Apple preserves a charge for Dutch developers, while Google applies a 4% reduction in South Korea. That distinction matters because payment-routing concessions can alter the fee level without ending platform monetization.

First-order effects

  • Dutch developers choosing third-party payments still owe Apple a commission, limiting the immediate margin benefit of switching away from Apple’s payment flow.
  • Google’s South Korean developers gain a 4% lower commission for third-party payments, while Google retains a revenue claim on those transactions.

Second-order effects

  • Apple’s Dutch terms and Google’s South Korean discount establish competing benchmarks for developers assessing whether external payment integration is worth its operational cost.
  • Payment providers serving these developers gain an opening to process transactions, but their economics must compete with platform fees that remain in place.

Third-order effects

The trend: App-store regulation is pushing Apple and Google toward country-specific alternatives to mandatory in-app payments while preserving some form of platform commission.

Discussion

  • @geradinlaw @geradinlaw on x
    (4) As Apple controls the (opaque) App Review process, it can for instance make the life of app developers seeking to take advantage of the ACM decision miserable. The @AutoriteitCM should pay attention to the risk of retaliation.
  • @randypicker Randy Picker on x
    The Netherlands requires Apple to allow dating apps to use third-party payment processors. And Apple will now switch to some yet-to-be-defined commission structure to, presumably, collect the same payments. Yes. Never about payment processing. Just an easy monetization tool. http…
  • @keleftheriou @keleftheriou on x
    May we also interest you in a higher-than-30% fee, due to the extra overhead of collecting it? 🙃 https://twitter.com/...
  • @macrumors @macrumors on x
    Dutch Regulators to Meet With Dating App Providers to Assess Apple's Plan for Alternate In-App Payment Options https://www.macrumors.com/... by @SamiFathi_ https://twitter.com/...
  • @joshdickson40 Josh Dickson on x
    The idea that Apple believes it's entitled to 4% (something like 150% of the actual credit card transaction cost) of an off-platform payment experience is... is something. https://twitter.com/...
  • @eric_seufert Eric Seufert on x
    Apple just clarified alternative payments on iOS. Spoiler: Apple still takes a commission. https://mobiledevmemo.com/...
  • @carnage4life @carnage4life on x
    Apple's approach to allowing 3rd party payments for IAPs in Netherlands will follow Google's approach in South Korea. Developers will still need to pay Apple a fee even if they use Stripe,etc. Google reduced their fee by 4% meaning there's zero benefit. https://mobiledevmemo.com/…
  • @carnage4life @carnage4life on x
    Apple & Google are going to tell developers “Fine instead of 30%, the fee is now 26% and after giving Stripe 2.9% + 30¢ plus a worse UX, you'll be worse off”. This is a diabolical way to meet the letter but not the spirit of laws. World class legal judo. https://t.co/YNXHgEeQdQ
  • @thomasbcn @thomasbcn on x
    “Apple just clarified alternative payments on iOS” https://mobiledevmemo.com/... by @eric_seufert The burden of alt payment will be high. Long live IAPs