WingNews logo WingNews
top | item 11897041

(no title)

ryantownsend | 9 years ago

Does anyone know if this is going to be available via the standardised Web Payments API? [1] (support being worked on by Chrome [2] and Microsoft Edge [3]) That way web developers won't need to build different implementations for different platforms.

[1]: https://web-payments.org/specs/#transactions

[2]: https://www.youtube.com/watch?v=yelPlCVZLEE

[3]: https://blogs.windows.com/msedgedev/2016/02/03/2016-platform...

discuss

order

zkoch|9 years ago

As a quick correction, the current Web Payments API (PaymentRequest) that is making its way through the W3C process is at https://w3c.github.io/browser-payment-api/. It's not the one from web-payments.org.

What Apple has announced so far is actually quite similar to PaymentRequest. Apple is a part of the Working Group, so this isn't a huge surprise. I am hopeful that the two implementations will converge rather quickly over the next few months. Apple emailed the public working group list expressing this hope as well [1].

For full disclosure, I am an editor on the PaymentRequest spec, and I work on Chrome.

[1] https://lists.w3.org/Archives/Public/public-payments-wg/2016...

apavia|9 years ago

https://lists.w3.org/Archives/Public/public-payments-wg/2016...

Verbatim from Apple:

"There are several differences between the Apple Pay API and the Payment Request API, and we look forward using the experience we've gained while working on it to help push the Payment Request API forward. We'll follow up with specific emails or GitHub issues on the main technical differences. A couple of the more important differences are:

* the API requires merchant validation, ensuring that bad actors' access to Apple Pay may be revoked;

* the canMakePayments() and canMakePaymentsWithActiveCard() methods help ensure we reveal user information to the site responsibly."