- From: ianbjacobs <notifications@github.com>
- Date: Wed, 27 Apr 2016 08:48:03 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
- Message-ID: <w3c/browser-payment-api/issues/155/215126918@github.com>
@adrianhopebailie, > That's okay but I'd want us to state that the suggestions from the merchant SHOULD take preference over any from the browser, unless there is a good reason to not state that. I understand the motivation for that suggestion. I am not sure I want to specify the presentation relationship between merchant-provided and browser-provided suggestions. Here's a counter-proposal for the case where we enable merchant and browser recommendations: * The mediator must distinguish for user-installed payment apps, merchant suggestions, and user agent suggestions. * The mediator should maintain the order of merchant suggestions when making them available to the user. I expect user agents will distinguish themselves by offering additional features such as: * Allowing the user to select a default payment app for a given domain, to make it easier to pay. * Allowing the user to easily store credentials in the browser when there are no registered payment apps. We should not specify that sort of behavior. > I think in general we SHOULD respect the order of things as provided by the payee. +1 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/browser-payment-api/issues/155#issuecomment-215126918
Received on Wednesday, 27 April 2016 15:48:58 UTC