Robert: I'm here with Capital
One
... working in our commerce strategy and development group
nicktr: Thanks everyone and
welcome Robert
... I hope journeys back from Japan were present
<nicktr> https://github.com/w3c/webpayments/wiki/Agenda-20191003
NickTR: Some resources available (minutes, summary)
<nicktr> Minutes from F2F https://www.w3.org/2019/09/15-wpwg-minutes.html
NickTR: The audience for the
summary is both those who attended for aide-memoire, but also
for people who missed the meeting
... Any TPAC attendee corrections or things people want to pick
up?
... any questions?
[None]
NickTR: Questions welcome as you read the materials
Ian: Lots of info, new ideas, will take a while to tease them out and lock them down
AdrianHB to look into a modal dialog spec - IN PROGRESS, see modal dialog explainer
<nicktr> https://github.com/adrianhopebailie/modal-window/blob/master/explainer.md
[IJ gives background on the proposal]
<Zakim> rouslan, you wanted to pick things up
rouslan: In Chrome we support 3rd
party payment handlers
... you can plug in and get a first-class experience for your
users
... to get this experience you need to register yourself as a
payment handler
... the user may be able to install/uninstall you as a payment
handler
... but we've found out that the UX that Chrome creates may be
useful for other applications (e.g., password managers, or 3DS
step-up flow)
... we've also heard from Mozilla that it might be easier to
start with the user interface
... even if firefox doesn't support all of the payment handler
features for now that chrome does
... so we've written up an explainer and are soliciting
feedback, including from the W3C Technical Architecture
Group
... overall I don't see many issues with it
... I view this as refactoring the Payment Handler API to
remove the generally applicable bit
... the payment handler API will be calling into this other
specification, delegating some responsibility to it
... so we'd have 2 specs, which makes it easier for browser
vendors to adopt in a stepwise manner
<nicktr> scribenick: nicktr
ian: can you characterise whether this is a big change to payment handler API?
rouslan: not too much
ian: what is the concrete next step and which group would work on this?
<Ian> [Ian hears "WICG"]
rouslan: WPWG should continue to
incubate - though we might have to move to WICG in the
future...
... would be great to have an eager partner who has a great use
case
<Ian> scribenick: Ian
AdrianHB: Rouslan summarized
nicely.
... I do think one use case we've heard is single sign-on. I
think we should also get the WebAuthn WG feedback on the
proposal.
NickTR: I see Marcos asking more broadly for features useful to building PWAs.
IJ: Does this secure modal dialog have any bearing on PR API?
Rouslan: No, I don't think so.
Ian: Justin, any progress on this "Justin to check internally at Google about what adoption data can be shared"
Justin: Hope to tackle in October
Ian: No progress on my
actions
... Anything on this AHB? "AdrianHB to organize testing of
assumptions about dropping the sheet."
AdrianHB: Early untested
assumptions are that the spec does not strictly require the
sheet
... so people can experiment with UX without spec changes
... it would be useful to get feedback on use cases people have
and how it would be impacted by no sheet or a new type of
selector
... I propose to redraft the action item to make it more
concrete
NickTR: One hot topic of the 2
days was how to increase adoption
... what should we be doing?
<nicktr> scribenick: nicktr
ian: we've been doing adoption
work but it is clear that we need to do more
... the biggest obstacles include lack of payment method, lack
of interoperability for handlers, lots of frcition around the
payment sheet, and merchant engagement more generally
... Vishal suggested other forums like MRC and others
... Airbnb made concrete suggestions (detailed in Ian's
blog)
... To make this real, we need to treat this more formally with
deliverables, timeframes etc, so that's something we need to
look at and distribute the load
<Ian> scribenick: Ian
lte: These are all the right
topics; how do you allocate resources
... as far as merchant engagement, we have been trying to work
out an arrangement with MRC where we partner and this could be
one of those
... MAG has also developed within our membership some
technology pros ... these would be the folks to get into a
room
... how we go about this is tough of course
... so I think there is a great opportunity to get the
technology professionals in the room
... the business side can come along.
<Zakim> nicktr, you wanted to talk about financial inclusion as a different adoption lever
nicktr: I also think PR API and
PH API provide a platform for a lot of different developers and
stakeholders to get a gold standard payment experience
... we've not reached out in the financial inclusion
space
... any suggestions for how to get additional engagement in
that community?
IJ: What caused you to think about that?
NickTR: One challenge of smaller
participants in the payments space is that they can't make the
same investment in technology
... I've been thinking about payment handler as an opportunity
to level the playing field a bit
... so was thinking about underserved communities who could
experiment and more easily reach people since they can leverage
the web infrastructure
Ian: I've been chatting with open source people about PR API support
IJ: We'd like to turn this adoption list into concrete actions with accountability. More work to do on that.
NickTR: So AHB and I will be looking for help on these
NickTR: Airbnb offered to host a
meeting in Europe
... e.g., Dublin or Paris
... we've looked at organizational meeting calendars and
propose some days in March
NickTR: Anybody aware of any industry events we need to avoid?
[None heard]
17 October
NickTR: TPAC pain point exercise analysis by Lawrence and Ian
- Draft charter
- PR API next steps