The %30 cut is for digital goods sold via Apple's stores, such as the AppStore, iTunes, iBookstore and in-app purchase. Physical goods have never had any kind of a restriction or revenue split.
Today you can go to the amazon or target app and buy physical goods using a credit card and Apple's cut of the sale is %0.
This just makes it easier and more secure for apps to take credit card payments. I think Apple may be getting a cut of the credit card fees when this happens, but that's between Apple and the card companies.
It looks like Applepay generates one-time cards by default resulting in a single-use Stripe token. Does that mean the use case this supports is only one-time payments versus "sign up with Apple pay+Stripe"? Any advice on how best to integrate Apple pay for recurring pay scenarios like Sumon?
This supports recurring payments too -- you can associate an Apple Pay-originated Stripe token with a Stripe customer object as normal, and then create charges for that that customer. (This means that the Lyft use-case also works largely unchanged.)
They're for completely different things. The 30% is for in-app only, but there is administrative costs with providing those resources (plus, Apple is a for-profit). This is for physical good.
Today you can go to the amazon or target app and buy physical goods using a credit card and Apple's cut of the sale is %0.
This just makes it easier and more secure for apps to take credit card payments. I think Apple may be getting a cut of the credit card fees when this happens, but that's between Apple and the card companies.