Re: [w3c/browser-payment-api] Consider removing merchant preference language (#481)

i would strongly caution against doing this. my reasons:

1. PR api is designed to serve merchants and users, and not allowing a merchant to provide a preference would be a disservice to them. 
2. It feels like the main beneficiary of this might be, indirectly, a credit card processing network. The PR api is designed for use cases beyond just credit card processing, and it is unclear why we should use the interests of one particular use case to change the generic spec.
3. If merchants don't have the basic control of selecting the order of instruments they prefer, it would create a disincentive (however small) for them to use the PR api.
4. No allowing specifying an order would encourage probing by merchants.

-- 
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/481#issuecomment-289151573

Received on Friday, 24 March 2017 21:50:49 UTC