The author does not seem to understand the difference between Apple Pay (incorrectly spelled as "ApplePay") and in-app purchases, or at least incorrectly assumes both to be called "Apple Pay". This makes the article basically impossible to understand to anyone not noticing that subtlety.
In fact, the actual Apple Pay is considered by Apple to be just another form of third-party payments for apps that sell "in-app-purchase like things" (i.e. prohibited by default, begrudgingly allowed where local law prohibits that limitation).
Apple Pay is Apple's payment card wallet, with Apple completely out of the loop for the actual payment, and there's no extra cost on top of the card payment to the merchant.
"In-app purchases" are a "merchant of record" solution where Apple acts as an intermediary between app vendor and buyer. They handle taxation, refunds, promotion etc., and take a generous cut for that service.
Merchant-of-record solutions have their use case (not everybody wants to deal with local taxation, for example!); what many people are mad about is that Apple generally has a rule that says "you must use ours if you're selling "digital goods" unless you're on a short list of exemptions".
This article, as far as I can tell, is trying to make the argument that Apple ought to allow competition between their merchant-of-record solution, other merchant-of-record solutions, and apps directly acting as the merchant, and I largely agree; I just wish it made that point more legibly.
Yeah, this is a remarkably sloppy article that’s just plain wrong. Apple requires using in-app purchases for digital goods. Which is emphatically NOT Apple Pay, as you mention. It just charges whatever card is attached to your Apple Account.
For physical goods etc, like the Apple Store app which the author incorrectly calls out, IAP are not mandated (neither is Apple Pay), and in fact you couldn’t use IAP for physical goods even if you wanted.
This is the key distinction - the article is about IAP (Apple's 15-30% commission system for digital goods) not Apple Pay (the payment method), which explains the confusion in other comments.
I am the author of the article.
The EU wanted to increase competition by allowing Alternative Payments, thus Apple had to change its rules.
I shortened the term "App Store In‑App Purchase system" for "purchase of digital goods or services" for "developers with apps in the European Union" (==> doesn't apply to the rest of the world, and it doesn't apply when you sell physical goods) to `ApplePay`, because nobody except developers has ever heard of the long term.
If Apple's new rules would be accepted by the EU, the result is that the EU consumer either can (continue to) use the payment system linked to their Apple account to pay for e.g. some outfit in a game like they did the last 15 years, or they can't anymore because the developer chose a 3rd party payment system (e.g. Taler) and is no longer allowed to offer that.
If you think the use of "ApplePay" is confusing, please suggest another short term we should use in the article instead. What about "Apple payments"?
(Demanding all shops in the mall use only 1 payment card (e.g. Costco) is illegal in the EU - except if you don't pay individually in the shops but only once when you leave the mall, since then you are (legally) paying a single merchant (Costco) who of course can decide which cards to accept. But for my airport analogy the customer is paying in the shop/app and not in the mall/AppStore.)
I believe they mean iOS in-app purchases when they say "ApplePay". Swap the two out mentally while reading, and it makes a bit more sense.
To be honest, I'm very surprised by that mistake, given where it's published – I'd hope that people working on GNU Taler understand the basics of their competitive environment.
Yea, that makes more sense, but still seems incorrect?
Just on my phone, several apps let me subscribe via the Apple AppStore but also by subscribing on their website with a credit card (like Discord, NYT, AllTrails, HBO, etc)
And that’s not even considering that when I pay for an in-app purchase… I’m paying with my credit card. Apple takes their cut, but it’s still my Amex or visa or whatever that I’m using via my Apple account.
It feels like the only viable part of this beef is that apps can’t accept both in-app purchases and alternate payments directly on their iOS app for functionality within the app?
> Just on my phone, several apps let me subscribe via the Apple AppStore but also by subscribing on their website with a credit card (like Discord, NYT, AllTrails, HBO, etc)
This is one of the few historical exemptions from Apple's otherwise ironclad IAP rules for so-called "reader apps".
Still, until very recently, these apps could not even mention that you can buy content/subscriptions on their website for cheaper (or, in some cases like the Kindle app, exclusively buy it there), let alone link to said website.
Now, the landscape is somewhat fragmented: In the EU, thanks to the DMA, external linking to external payment methods is allowed, but comes with a "scare sheet" and still grants Apple a cut of 20%(!). (This is about to change, I believe, but I'm not super up to date on it.)
In the US, developers can now apparently link to external payment sites (in SAfari) without Apple being allowed to charge a commission at all. This is a very recent development, and I haven't seen it in action myself.
Also the core analogy is wrong: If I own the concession rights for an airport, I am absolutely taking a non-trivial commission on every Chipotle burrito and Starbucks latte sold there.
I've just checked 3 different apps which offer premium features. All of them go straight to Apple Pay, without showing any other options.
EDIT: okay, I think get it now. In-app purchases != taking payments in general. E.g. I have different options for payments when using the Amazon app but only Apple Pay when buying a pro version of a metronome app. It's in-app purchases that force Apple Pay.
In-app purchases (ie upgrading an App subscription) are different from purchases in an app (ie buying things on Amazon). Entirely different platforms and structures that have been separate forever.
What's probably happening here is that you are paying Apple using Apple Pay. Apple is the merchant of record for in-app-purchases.
So it's not entirely incorrect (but definitely confusing) to say that the end user is "paying using Apple Pay", but they're paying Apple, not the app vendor.
I believe they may be confusing the requirements. If I understand the App Store rules, you can accept payments from other places but you have included ApplePay as an option too. So, Apple doesn’t restrict you to ApplePay only but that you have to include ApplePay.
I could be mistaken, yes but that was what I remember being clarified with the Epic Games debacle. Epic _only_ wanted to give user only one available option but Apple said they had to give them an Apple IAP option too.
> Would the EU allow Visa or Mastercard to impose such exclusion rules on merchants who want to accept their credit cards? Definitely not.
I mean Costco has been doing this for many years and people seem ok with it? It's somewhat annoying but I get enough value out of Costco that myself and I think many are happy with the tradeoff.
That's a rule imposed by Costco, not by Visa or Mastercard. Structurally, that's a completely different story.
In fact, Visa's and Mastercard's rules used to even prohibit merchants from any kind of selective acceptance (e.g. "no commercial cards" or "only debit cards") or even from charging different fees by type. This used to be called the "honor all cards rule", but is now no longer legal in many markets in its most narrow form, i.e. "same fees for all cards".
Giving merchants the option of selective payment method acceptance, or of offering discounts for some but not others, is extremely important for competition between payment methods. For example, allowing merchants to charge higher payment fees for cards that pay large kickbacks to the cardholder, or to alternatively give them a direct discount for "cheaper" cards, is one of the few bargaining chips merchants have over the networks and by extension issuers, if one were to try to address the problem of expensive card payments from a free markets perspective.
Outright not accepting one of the two large networks, in exchange for probably a significant cut in fees by the other, is a pretty smart move that works even under "honor all cards", but is only feasible if you're Costco – if you're a corner store, you'd probably just lose roughly half of your customers in the US.
So you’re saying Apple IAP as merchant of record forcing use of Apple Pay is ok (?) but Apple App Store forcing use of Apple IAP as the only merchant of record is not?
(You were clarifying the difference between these things elsewhere so hoping you could clarify this, thanks.)
(And I want to see more Costco v Apple comparisons!)
No, I’m not trying to argue that at all! I consider forced in-app purchases very problematic.
I’m just saying these are structurally very different scenarios and I don’t think they can be used as an analogy.
The core issue is that in the case of Costco, there’s only two immediate actors: Costco and its customers. For Apple in-app purchases, there’s three: Apple, app vendors, and Apple users. The argument is leveraging that Apple is unfairly monetizing its captive user base through app vendors.
Now Costco is also leveraging its captive user base, but they are doing so against card issuers, which can be seen as somewhat affiliated with cardholders (and thus by extension Costco consumers) – because they pay them kickbacks in exchange for preferring using one card over the other!
Both fascinating case studies in economics, but structurally distinct.
Dyson sold in the Costco Warehouse must use Costco as the merchant. WidgetApp sold in the Apple App Store must use iOS IAP merchant of record solution (??).
Costco Warehouse forces use of Visa (or Mastercard - depends on country). Apple iOS IAP does NOT require Apple Pay.
Of course Apple doesn’t buy goods from suppliers before selling them to customers, unlike Costco. And Costco Warehouse is members only, unlike Apple (unless you squint and view iPhone ownership as a membership).
Kind of, but the analogy does break down since there isn't only one store that Dyson can sell you vacuums at. There is some level of stickiness since Costco requires an upfront membership, but it's really not as pervasive.
Imagine people living in houses or apartments with a proprietary kind of power outlet, and the patent owner/real estate developer is willing to grant you, an appliance manufacturer, a license for power plugs compatible with that outlet – under the condition that you exclusively sell them in their storefronts, for a 30% cut.
I've never been in a Costco - is that a mall where you pay in each shop individually, or a single store where you pay the total at the exit? In the latter case, the customer is legally only buying from one merchant, who can of course decide which payment system(s) to accept.
But in the former case, in the EU it would be illegal for the mall operator to dictate which payment methods shops may offer their customers.
The author does not seem to understand the difference between Apple Pay (incorrectly spelled as "ApplePay") and in-app purchases, or at least incorrectly assumes both to be called "Apple Pay". This makes the article basically impossible to understand to anyone not noticing that subtlety.
In fact, the actual Apple Pay is considered by Apple to be just another form of third-party payments for apps that sell "in-app-purchase like things" (i.e. prohibited by default, begrudgingly allowed where local law prohibits that limitation).
Apple Pay is Apple's payment card wallet, with Apple completely out of the loop for the actual payment, and there's no extra cost on top of the card payment to the merchant.
"In-app purchases" are a "merchant of record" solution where Apple acts as an intermediary between app vendor and buyer. They handle taxation, refunds, promotion etc., and take a generous cut for that service.
Merchant-of-record solutions have their use case (not everybody wants to deal with local taxation, for example!); what many people are mad about is that Apple generally has a rule that says "you must use ours if you're selling "digital goods" unless you're on a short list of exemptions".
This article, as far as I can tell, is trying to make the argument that Apple ought to allow competition between their merchant-of-record solution, other merchant-of-record solutions, and apps directly acting as the merchant, and I largely agree; I just wish it made that point more legibly.
Yeah, this is a remarkably sloppy article that’s just plain wrong. Apple requires using in-app purchases for digital goods. Which is emphatically NOT Apple Pay, as you mention. It just charges whatever card is attached to your Apple Account.
For physical goods etc, like the Apple Store app which the author incorrectly calls out, IAP are not mandated (neither is Apple Pay), and in fact you couldn’t use IAP for physical goods even if you wanted.
This is the key distinction - the article is about IAP (Apple's 15-30% commission system for digital goods) not Apple Pay (the payment method), which explains the confusion in other comments.
OK that’s super confusing but makes sense. I can choose between Apple Pay and other options in literally every app I use and was very confused.
I am the author of the article. The EU wanted to increase competition by allowing Alternative Payments, thus Apple had to change its rules. I shortened the term "App Store In‑App Purchase system" for "purchase of digital goods or services" for "developers with apps in the European Union" (==> doesn't apply to the rest of the world, and it doesn't apply when you sell physical goods) to `ApplePay`, because nobody except developers has ever heard of the long term.
If Apple's new rules would be accepted by the EU, the result is that the EU consumer either can (continue to) use the payment system linked to their Apple account to pay for e.g. some outfit in a game like they did the last 15 years, or they can't anymore because the developer chose a 3rd party payment system (e.g. Taler) and is no longer allowed to offer that.
If you think the use of "ApplePay" is confusing, please suggest another short term we should use in the article instead. What about "Apple payments"?
(Demanding all shops in the mall use only 1 payment card (e.g. Costco) is illegal in the EU - except if you don't pay individually in the shops but only once when you leave the mall, since then you are (legally) paying a single merchant (Costco) who of course can decide which cards to accept. But for my airport analogy the customer is paying in the shop/app and not in the mall/AppStore.)
What is this article talking about?
Basically every app I have on my phone that takes payments from me accepts ApplePay and also credit cards.
I believe they mean iOS in-app purchases when they say "ApplePay". Swap the two out mentally while reading, and it makes a bit more sense.
To be honest, I'm very surprised by that mistake, given where it's published – I'd hope that people working on GNU Taler understand the basics of their competitive environment.
Yea, that makes more sense, but still seems incorrect?
Just on my phone, several apps let me subscribe via the Apple AppStore but also by subscribing on their website with a credit card (like Discord, NYT, AllTrails, HBO, etc)
And that’s not even considering that when I pay for an in-app purchase… I’m paying with my credit card. Apple takes their cut, but it’s still my Amex or visa or whatever that I’m using via my Apple account.
It feels like the only viable part of this beef is that apps can’t accept both in-app purchases and alternate payments directly on their iOS app for functionality within the app?
> Just on my phone, several apps let me subscribe via the Apple AppStore but also by subscribing on their website with a credit card (like Discord, NYT, AllTrails, HBO, etc)
This is one of the few historical exemptions from Apple's otherwise ironclad IAP rules for so-called "reader apps".
Still, until very recently, these apps could not even mention that you can buy content/subscriptions on their website for cheaper (or, in some cases like the Kindle app, exclusively buy it there), let alone link to said website.
Now, the landscape is somewhat fragmented: In the EU, thanks to the DMA, external linking to external payment methods is allowed, but comes with a "scare sheet" and still grants Apple a cut of 20%(!). (This is about to change, I believe, but I'm not super up to date on it.)
In the US, developers can now apparently link to external payment sites (in SAfari) without Apple being allowed to charge a commission at all. This is a very recent development, and I haven't seen it in action myself.
Also the core analogy is wrong: If I own the concession rights for an airport, I am absolutely taking a non-trivial commission on every Chipotle burrito and Starbucks latte sold there.
Can you provide an example?
I've just checked 3 different apps which offer premium features. All of them go straight to Apple Pay, without showing any other options.
EDIT: okay, I think get it now. In-app purchases != taking payments in general. E.g. I have different options for payments when using the Amazon app but only Apple Pay when buying a pro version of a metronome app. It's in-app purchases that force Apple Pay.
In-app purchases (ie upgrading an App subscription) are different from purchases in an app (ie buying things on Amazon). Entirely different platforms and structures that have been separate forever.
That's not Apple Pay, these are iOS in-app purchases. If you or the author call it that, nobody here will understand you.
Makes sense now, thanks.
To be fair, as a user, I don't see the expression "in-app purchases" while I _do_ see the Apple Pay logo. It's easy to get them confused.
What's probably happening here is that you are paying Apple using Apple Pay. Apple is the merchant of record for in-app-purchases.
So it's not entirely incorrect (but definitely confusing) to say that the end user is "paying using Apple Pay", but they're paying Apple, not the app vendor.
I believe they may be confusing the requirements. If I understand the App Store rules, you can accept payments from other places but you have included ApplePay as an option too. So, Apple doesn’t restrict you to ApplePay only but that you have to include ApplePay.
I don’t believe there is any “must support Apple Pay if accepting card payments” rule.
If there is, it’d be honored in the breach; uncountable apps take card payments but not Apple Pay.
I could be mistaken, yes but that was what I remember being clarified with the Epic Games debacle. Epic _only_ wanted to give user only one available option but Apple said they had to give them an Apple IAP option too.
IAP and Apple Pay are completely different.
The article is false. Plenty of apps on the App Store offer both credit card payment and Apple Pay.
Why is that flagged?
> Would the EU allow Visa or Mastercard to impose such exclusion rules on merchants who want to accept their credit cards? Definitely not.
I mean Costco has been doing this for many years and people seem ok with it? It's somewhat annoying but I get enough value out of Costco that myself and I think many are happy with the tradeoff.
That's a rule imposed by Costco, not by Visa or Mastercard. Structurally, that's a completely different story.
In fact, Visa's and Mastercard's rules used to even prohibit merchants from any kind of selective acceptance (e.g. "no commercial cards" or "only debit cards") or even from charging different fees by type. This used to be called the "honor all cards rule", but is now no longer legal in many markets in its most narrow form, i.e. "same fees for all cards".
Giving merchants the option of selective payment method acceptance, or of offering discounts for some but not others, is extremely important for competition between payment methods. For example, allowing merchants to charge higher payment fees for cards that pay large kickbacks to the cardholder, or to alternatively give them a direct discount for "cheaper" cards, is one of the few bargaining chips merchants have over the networks and by extension issuers, if one were to try to address the problem of expensive card payments from a free markets perspective.
Outright not accepting one of the two large networks, in exchange for probably a significant cut in fees by the other, is a pretty smart move that works even under "honor all cards", but is only feasible if you're Costco – if you're a corner store, you'd probably just lose roughly half of your customers in the US.
So you’re saying Apple IAP as merchant of record forcing use of Apple Pay is ok (?) but Apple App Store forcing use of Apple IAP as the only merchant of record is not?
(You were clarifying the difference between these things elsewhere so hoping you could clarify this, thanks.)
(And I want to see more Costco v Apple comparisons!)
No, I’m not trying to argue that at all! I consider forced in-app purchases very problematic.
I’m just saying these are structurally very different scenarios and I don’t think they can be used as an analogy.
The core issue is that in the case of Costco, there’s only two immediate actors: Costco and its customers. For Apple in-app purchases, there’s three: Apple, app vendors, and Apple users. The argument is leveraging that Apple is unfairly monetizing its captive user base through app vendors.
Now Costco is also leveraging its captive user base, but they are doing so against card issuers, which can be seen as somewhat affiliated with cardholders (and thus by extension Costco consumers) – because they pay them kickbacks in exchange for preferring using one card over the other!
Both fascinating case studies in economics, but structurally distinct.
I’m trying to understand the structure, is this about right?
Costco Warehouse = Apple App Store.
Dyson (vacuum vendor) = WidgetApp (digital goods vendor).
Dyson sold in the Costco Warehouse must use Costco as the merchant. WidgetApp sold in the Apple App Store must use iOS IAP merchant of record solution (??).
Costco Warehouse forces use of Visa (or Mastercard - depends on country). Apple iOS IAP does NOT require Apple Pay.
Of course Apple doesn’t buy goods from suppliers before selling them to customers, unlike Costco. And Costco Warehouse is members only, unlike Apple (unless you squint and view iPhone ownership as a membership).
Kind of, but the analogy does break down since there isn't only one store that Dyson can sell you vacuums at. There is some level of stickiness since Costco requires an upfront membership, but it's really not as pervasive.
Imagine people living in houses or apartments with a proprietary kind of power outlet, and the patent owner/real estate developer is willing to grant you, an appliance manufacturer, a license for power plugs compatible with that outlet – under the condition that you exclusively sell them in their storefronts, for a 30% cut.
I've never been in a Costco - is that a mall where you pay in each shop individually, or a single store where you pay the total at the exit? In the latter case, the customer is legally only buying from one merchant, who can of course decide which payment system(s) to accept. But in the former case, in the EU it would be illegal for the mall operator to dictate which payment methods shops may offer their customers.
Apple double/triple dips on every angle.
- $ from hardware sales
- $ from developer(s) per year
- % cut from App Store listing
- % cut from IAPs
- very small % cut/recapture from web of fees imposed by banks/cc/debit networks via Apple Pay
They are very motivated to keep all parties within their Apple wall.
[dead]