- From: ianbjacobs <notifications@github.com>
- Date: Mon, 03 Apr 2017 14:47:24 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 3 April 2017 21:48:22 UTC
Hi @mattsaxonwp, The spec has been edited and the section numbers may no longer be accurate (e.g., I think 17.4 used to be 19.4). I can't find your "section 7.4" In reading the text of what is now 17.4, it seems to me that as written, the mediator is full responsible. One question is "where does the mediator get the data to do the things listed in 17.4?" In the case of Web-based payment apps, we are defining a PaymentAppResponse [1]. The user agent will use it as the source of some of the information identified in 17.4 (e.g., methodName and details). Perhaps one way to address your comment is to add a note after the 17.4 algorithm, something like: "Note: methodName and details are provided by the user agent or other payment app." Ian [1] https://w3c.github.io/webpayments-payment-apps-api/#sec-payment-app-response -- 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/476#issuecomment-291283976
Received on Monday, 3 April 2017 21:48:22 UTC