- From: Ian Jacobs <ij@w3.org>
- Date: Fri, 24 Feb 2017 14:02:23 -0600
- To: Zach Koch <zkoch@google.com>, Kenneth Mealey <Kenneth.Mealey@aexp.com>, Andrew Pelehach <andrew.pelehach@samsungpay.com>, Molly Dalton <Molly.Dalton@microsoft.com>
- Cc: public-payments-strategy@w3.org
Minutes from today’s call:
https://www.w3.org/2017/02/24-wpwg-minutes
[PLEASE NOTE NEW TIME FOR CALL BELOW!]
Next steps:
* Ken and Ian will flesh out questions for FAQ
https://lists.w3.org/Archives/Public/public-payments-strategy/2017Feb/0007.html
They will go here as drafts:
https://github.com/w3c/payment-request-info
More questions welcome!
* Zach will continue conversations internally re: identity
* Zach will look to see whether he has any visuals to help communicate user experiences
Next meeting:
Friday, 3 March at noon ET (9am PT). Updated WebEx:
http://www.w3.org/2017/01/merchant_adoption-20170120.ics
Note that we moved the call one hour later!
Ian
> On Feb 23, 2017, at 12:24 PM, Ian Jacobs <ij@w3.org> wrote:
>
> Hi all,
>
> Our next meeting is tomorrow, 24 February, from 11:00-noon ET. WebEx:
> http://www.w3.org/2017/01/merchant_adoption-20170120.ics
>
> Agenda:
>
> * Branding. Zach, any updates?
>
> * Developer portal
> See https://github.com/w3c/payment-request-info
>
> I have begun to flesh it out. In addition, at the 10 Feb meeting [1] Ken and Andrew
> took an action to write up some FAQ questions. Below please see a batch that
> I wrote based heavily on an initial draft from Ken.
>
> * Face-to-face meeting. I’ve asked for 30 minutes on the agenda to talk about merchant
> adoption strategy. How should we use it?
>
> Ian
>
> [1] https://www.w3.org/2017/02/10-wpwg-minutes.html
>
> =====
>
> Q – How will checkout pages be different when merchants use the API? How much flexibility do merchants have (e.g., in the number of buttons they display)?
>
> Q - What is the difference between a payment method and a payment app?
>
> Q - What does a merchant need to do to accept a particular payment method?
>
> Q - How does a user register a payment app for use with the API?
>
> Q - How does a merchant handle payment method data it receives through the API?
>
> Q – How do merchants express their references for accepted payment methods? How does the browser use that information?
>
> Q – How do merchants express their preferences for payment apps they would like the user to use? How does the browser use that information?
>
> Q - Other than expressing preferences, does the merchant have any way to influence or modify the payment app selected by the user?
>
> Q – What influence does the browser exert over the user choice of payment app?
>
> Q– What influence will the payment app exert over the user choice of payment method?
>
> Q – How does the browser store user information unrelated to payment (e.g., shipping address)?
>
> Q - How do payment apps (whether browser or third party) store payment-related credentials?
>
> Q – What are the primary benefits of the API to merchants?
>
> Q – What are the primary risks of the API to merchants?
>
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 718 260 9447
>
>
>
>
--
Ian Jacobs <ij@w3.org>
https://www.w3.org/People/Jacobs/
Tel: +1 718 260 9447
Received on Friday, 24 February 2017 20:02:37 UTC