What do you mean? The app can use Apple's system and its own. If the developers don't want your money on terms fair to you, you don't buy.
Some things are relatively easy to refund via Apple, but not all of them. It's nearly impossible to get a refund for in-app purchases, gift cards, balance top-ups, auto-renewing subscriptions, redeemed digital goods, and so on. Coming from the EU, if I paid for these things directly with a credit card, I'd be able to get a refund in line with our consumer protection laws (if the item was sold deceptively, if it has a fault, if I am not satisfied for any reason within 14 days) that cover more or less all digital purchases - no problem.
To borrow your words, Apple's system is taking away trust. I like the refunds my European bank offers me because it operates under consumer-friendly laws. I don't trust Apple's refunds.
Anyway, opening any system to more choices for the consumer cannot decrease trust. If the consumer trusts the original payment option, they can use that. If that is not provided, but the customers don't trust other payment methods, the app won't make money. The market will soon negotiate so that the payment methods that customers and sellers find acceptable prevail. Apple fears it won't be their extortion (I mean payment system), and rightfully so. Aside from the Stockholm syndrome, there's very little reason to use it.
This is a good point. If an app does me wrong with a non Apple payment processor I can do a chargeback as a last resort. That's not really an option for Apple payment processing because I think it can get your whole Apple account banned.
That is also true. There is a very significant disincentive to charge back against sellers protected by Apple, Microsoft, Google, Amazon, PayPal, Stripe, and other similar payment gateways. The consumer protections are, therefore, eroded.
You're missing the part where app developers take away the Apple payment option because that way they can make it much harder to do refunds, cancel subscriptions, etc.
That decreases trust. Period.
You're claiming this is about adding choices, but it's not. App developers will be removing the choice for consumers to pay via Apple.
Saying it's my choice to then not use the app is disingenuous. When a good option is replaced with multiple worse options, there's no benefit to "more choices".
I don't need to, that's what I was already responding to. Please re-read my comment.
I really didn't think it necessary to reply to your sentence that "If that is not provided, but the customers don't trust other payment methods, the app won't make money" -- because it's so clearly relying on a false premise.
But since you need it further explained: trust in payment methods isn't binary. I prefer Apple payments but still use my credit card for everything else where it isn't available. If people can't use a better payment option, they'll fall back to a worse one. They usually won't just forego using the app entirely. Just look at the success of Adobe Creative Cloud despite its horrendous billing practices.
Again, that's what's wrong with your argument around choice. More choice leads to worse outcomes when you allow the best choice to be removed.
> You're not free to continue using Apple's payment system as a consumer.
Previously, apps could still require you to not use the apple payment option.
For example, Spotify only let you subscribe on the web because apple's 30% cut is larger than their margin, so they'd lose money if you subscribed in-app.
The "Buy" page in the app was just text saying "You cannot buy a subscription in the app". It couldn't link to the webpage since apple's rule banned that. It couldn't say "You can buy a subscription on our webpage" because apple's rules banned that.
Before, an app could simply not have any payment option in the app, and tell you "You cannot pay here". Now, an app can still choose to have no in-app payment and instead tell you "You can pay on the web", or embed that web payment option in-app.
You are still welcome to refuse to use any apps that don't support apple pay, as you could before.
I’m pretty sure this ruling just lets developers add an external payment option (and charge less for it). Apple’s IAP is still a requirement, so you’ll still have that option if it’s worth the 30% premium to you (it definitely is not for me).
Developers are free to include no payment mechanism in the app that would involve an iAP, and tell people to click to go to the website (which can open an in app browser window).
Well in that case, there must be a single endpoint, a common interface, to initiate a payment, track chargeback and view payment histories. Customers should have the option if they want to trust Apple with their payment details or 3rd-party.
You're not free to continue using Apple's payment system as a consumer.