Re: [webpayments] Should the payment request support multiple pricing options? (#79)

I think it's a good idea to have pricing options for loyalty cards, for example. I don't think it's necessary for version 1 of the API, in the interest of building the most common and simple API for now. Perhaps in version 2 would be better.

That being said, I would prefer option 3 ("Payment apps are able to request an updated payment request when users make choices that may change the price they pay"), because I want to avoid computational logic and exhaustive pre-calculation. Also, option 3 fits the "paymentRequest.setAddressChangeListener()" paradigm nicely. I'm thinking about perhaps "paymentRequest.setPaymentInstrumentTypeListener()", for example.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/79#issuecomment-179489111