Re: [w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157)

@ianbjacobs,

> My expectation is that through the dialog between mediator and user, the user's selected payment app will receive all the information that it needs. In the case (which I expect to be common at least initially) of a payment app that supports a small number of payment methods, the payment will will receive less information...but still all the information that it needs. In the case you describe, it sounds like the payment app would receive more information as a result of the dialog.

I don't think the mediator necessarily knows all of the information that the Payment App needs. I think the mediator's only purpose is to help a user pick the Payment App to send the payment request message to.

What about the case that you don't know you want to use two payment methods until you've gotten to your Payment App and found out that an account for a particular payment method has insufficient funds ... but another method could supplement to fulfill the request? And so on.

I think the mediator role should just be considered a router -- it shouldn't get more invasive/controlling than that.

---
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/157#issuecomment-214552004