- From: ianbjacobs <notifications@github.com>
- Date: Tue, 11 Apr 2017 08:39:51 -0700
- To: w3ctag/spec-reviews <spec-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 11 April 2017 15:40:39 UTC
Hi @dbaron, Thank you for the careful review. I can fill in a couple of blanks: 1) Payment method identifiers that are URLs will point to Payment Method Manifest Files. We are working on a separate specification for those. Our current draft of that spec is out of date with respect to "version 2" that we recently discussed at our face-to-face meeting: https://github.com/zkoch/zkoch.github.io/blob/master/pmi-v2.md 2) The system as a whole intends to support: a) Arbitrary payment methods, identified by URLs and described by payment method manifest files. b) Third party payment apps that register their support for different payment methods with the browser. The WG is developing the Payment Handler API [1] to that Web apps can request permission from the user to handle payment request events for different payment methods. Thus, the ecosystem will support both Web-based payment apps (through an open standard) and native payment apps (through proprietary APIs). Ian [1] https://w3c.github.io/webpayments-payment-apps-api/ -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/spec-reviews/issues/152#issuecomment-293304004
Received on Tuesday, 11 April 2017 15:40:39 UTC