Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211)

@ianbjacobs, the spec does say that the user agent should update UX based on changes from the update algorithm but I specifically stayed away from describing how an implementation should display the total as payment methods are selected. There are many different ways to do this especially as related to the different ways that payment apps might be implemented. I think it is implicit that a wise implementation would find some way to indicate to the user the different prices per payment method but friendly amendments to make this more explicit welcome.

On the topic of matching payment request identifiers, my position is that we should deal with simple matching in v1, which is what is currently specified. Should a proposal for more complex matching semantics be adopted in the group then any requirements dealing with matching payment methods would need amending. Such a proposal would need to include a comprehensive solution to this issue.

---
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/pull/211#issuecomment-224757717