How would they present that and make it clear to users that that’s far less secure than Apple Pay? Why would they do that?
Wasn’t this API basically invented to provide a standard complaint way of doing something like Apple Pay? Here you go.
How would they present that and make it clear to users that that’s far less secure than Apple Pay? Why would they do that?
Wasn’t this API basically invented to provide a standard complaint way of doing something like Apple Pay? Here you go.
No, the API invented so that the browser could act as an intermediary between many payment-requesting services and payment services, such as PayPal, PayTM, Apple Pay, etc.
They chose to limit support exclusively to Apple Pay, so that users won't have a choice.
This is not a case of “embrace and extend“ where Apple took something open and locked it down. This is a case of where existing functionality is now available any standards compliant way instead of having to use Apple’s custom JavaScript calls.
User still have the choice of entering their credit cards the same way they have for the last 20+ years. It’s not like you’re forcing ALL payment on the web through this.
I notice you didn’t propose a suggestion to the security/UI delima I mentioned. I am 100% willing to bet that’s why they didn’t add basic-card support. And it seems like a good decision to me.
This is a brand new API that basically no one uses. If websites start using it because they want to support Apple Pay and see it will be easier to support other payment methods on other browsers… isn’t that a benefit?
I don’t see how this is anything but a very positive move compared to the official way to support Apple Pay last month.
> But that didn’t happen UNTIL Apple made their own and everyone else decided they wanted one too.
Please, PayPal has had it for over a decade...
Or, as someone from Apple wrote:
> The ability for apps like PayPal to handle payments in the browser requires the Payment Handler API [1]. We aren't announcing support for Payment Handler here, just Payment Request.
> It's not like we're actively restricting or blocking these apps, we just haven't written the code to do this.
Edge's implentation: https://docs.microsoft.com/en-us/microsoft-edge/dev-guide/wi... Chrome's implementation: https://developers.google.com/web/fundamentals/payments/