<scribe> Scribe: Ian
IJ: Nearly ready for PR but have
a few things left
... hope to be at PR by TPAC
https://www.w3.org/2019/Talks/ij_risk_20190808/?full#Cover
IJ: Want to go through it?
Pranjal: Could you share the slides on the public mailing list?
<scribe> ACTION: Ian to share slides on the list.
<trackbot> 'Ian' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., IFSF-EFT-WG-Lead, ijacobs).
https://github.com/w3c/webpayments/wiki/FTF-Agenda-201909
IJ: Some additions - SRC take up? payment handler future?
Lawrence: I think we should spend
some time looking at adoption
... a pulse check...are we adding value where we endeavored to
do so?
... are we getting closer to solving these issues?
... review what we heard would be useful ... are we checking
the boxes?
... In order for us to get a sense of where we are....enumerate
the boxes and see if we are satisfying them
Ryan: +1
<jv> +1
IJ: We should look at use cases +1. We have been looking at obstacles to adoption
Lawrence: I am happy to
contribute
... but we could use input from merchant side
<scribe> ACTION: Ian to work with Lawrence and others to help frame where we are in meeting goals (for TPAC)
<trackbot> 'Ian' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., IFSF-EFT-WG-Lead, ijacobs).
[Laura describes MAG participation in April meeting]
Ryan: We are merchants for this conversation.
Lawrence: I would like to dive
into smaller and medium merchants and the journeys they need
improved
... how do we capture those journeys?
laura: I think sitting down with
large merchants and what they do today and what they couldn't
do with PR API
... I think that's partly what we did in APril
https://www.w3.org/2019/04/03-wpwg-minutes.html#item03
Lawrence: We have captured some merchant requirements; would be good to summarize those and consumer expectations
https://github.com/w3c/src/wiki
IJ: Would merchants be willing to send hints through the pipe to help payment handler establish user identity?
Lawrence: Two parts of the
journey....for a consumer new to SRC...what does that
experience look like? Or if already enrolled a card, what would
that experience look like?
... on the call yesterday it was clear those journeys would be
different
... and also there would be different regulatory
requirements
... in the EU, for instance, payment credentials are sensitive
data
... what is required to comply with local requirements?
... if information is passed through PR API...is that
representable when it comes to strong authentication to
retrieve payment instruments?
... we are looking into that further in the TF
Ryan: We would be interested in looking at that question.
8 August