I observe only lukewarm support for merchant-recommended payment apps in V1 of the specification. A modified version of the proposal is this: * To recommend payment apps (native or web), the merchant provides a list of payment app identifiers via Payment Request API. For Web-based payment apps, the identifier is an origin. * The user agent is free to use this information in a variety of ways, including (1) Highlighting in a special way any registered payment apps that the merchant has recommended or (2) displaying information about trusted payment apps. This specification would not initially describe how the user agent establishes that a payment app is trusted. Any thoughts on this reduced approach that still allows merchants to provide some preference information? Ian -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments-payment-apps-api/issues/48#issuecomment-277329345
Received on Friday, 3 February 2017 18:50:09 UTC