3 ms·

The very first line of the article states: “We’re pleased to announce that Safari 11.1 on macOS and Safari on iOS 11.3 now support the W3C Payment Request API

The very first line of the article states: “We’re pleased to announce that Safari 11.1 on macOS and Safari on iOS 11.3 now support the W3C Payment Request API for conducting Apple Pay transactions on the web.”

ucaetano 9y ago
Yes, I read that part: "W3C Payment Request API for conducting Apple Pay transactions" My question is: is this only for Apple Pay? Safari won't support any other payment method/service?
- aeontech 9y ago
  I’m not sure I understand the question - what other payment service are you thinking of? With this change developers can use the same code to initiate a payment no matter which browser they are in, instead of having to write custom code for triggering Apple Pay, that’s the win here. This doesn’t change how Apple Pay for the web works. You can use Stripe or any other merchant processor to process your Apple Pay payments, iirc.
  - ucaetano 9y ago
    The original specification and the Chrome implementation aren't restricted to a single payments app, such as Apple Pay: > The browser then presents the payments UI to the user, who selects a payment method and authorizes the transaction. A payment method can be as straightforward as a credit card that is already stored by the browser, or as esoteric as third-party application written specifically to deliver payments to the site. So if you have the PayPal app installed, you should be able to choose it as the payment method and so on. My question is if the Apple implementation on Safari restricts the payment methods only to Apple Pay, bocking any other payment services or apps.
    - aestes 9y ago
      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. [1] https://w3c.github.io/payment-handler/ https://w3c.github.io/payment-handler/
      - ucaetano 9y ago
        > It's not like we're actively restricting or blocking these apps, we just haven't written the code to do this. Is my guess right that such code will never be written?

ucaetano 9y ago

Yes, I read that part: "W3C Payment Request API for conducting Apple Pay transactions" My question is: is this only for Apple Pay? Safari won't support any other payment method/service?

aeontech 9y ago
I’m not sure I understand the question - what other payment service are you thinking of? With this change developers can use the same code to initiate a payment no matter which browser they are in, instead of having to write custom code for triggering Apple Pay, that’s the win here. This doesn’t change how Apple Pay for the web works. You can use Stripe or any other merchant processor to process your Apple Pay payments, iirc.
- ucaetano 9y ago
  The original specification and the Chrome implementation aren't restricted to a single payments app, such as Apple Pay: > The browser then presents the payments UI to the user, who selects a payment method and authorizes the transaction. A payment method can be as straightforward as a credit card that is already stored by the browser, or as esoteric as third-party application written specifically to deliver payments to the site. So if you have the PayPal app installed, you should be able to choose it as the payment method and so on. My question is if the Apple implementation on Safari restricts the payment methods only to Apple Pay, bocking any other payment services or apps.
  - aestes 9y ago
    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. [1] https://w3c.github.io/payment-handler/ https://w3c.github.io/payment-handler/
    - ucaetano 9y ago
      > It's not like we're actively restricting or blocking these apps, we just haven't written the code to do this. Is my guess right that such code will never be written?