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

Here are a handful of use cases from our base use case document that I feel are related to this feature:

6.1.3 (application or marketing elements) supports this directly in that it talks about loyalty cards and coupons.  However, at least in the latest draft these are not in any Roadmap "phase".

6.2.1 (discovery of accepted schemes) talks to having multiple accepted payment schemes.  If that's the case, it should be possible for different schemes to have different payment amounts (e.g., if you pay with Visa it is this much, in Bitcoin it is this much).

6.2.2 (selection of payment instruments) also goes to this case.  The user (or their automated agent) needs a way to intelligently decide which payment instrument or combination of instruments will be used.

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