<Ian> Scribe: Ian
NickTR: Happy 2020. It's the first time we've met in a while
NickTR: Please have your AC rep rejoin the group https://www.w3.org/2004/01/pp-impl/83744/join
https://www.w3.org/2004/01/pp-impl/83744/status
<nicktr> sophie: do we have to rejoin every time we re-charter?
<nicktr> ian: it's when we add a new REC track deliverable where there might be new patent commitments
<nicktr> ...in this instance, we have added an SRC REC track deliverable
NickTR: We have a good habit of
early in the year stating priorities for the year
... I've put a straw proposal in the agenda
====
Seek implementation experience and feedback for payment request and payment handler specifications (should merchant adoption be a separate priority? Feels important!)
Move payment request to proposed recommendation
Move payment handler to candidate recommendation
Create first published working draft of SRC payment method
Broaden payment method availability (including open banking/credit transfer)
====
NickTR: I think merchant adoption is an important priority
<Zakim> Ian, you wanted to also mention some objectives we documented after TPAC
<nicktr> ian: we postponed PR rec track work for more updates from adopters
<nicktr> ...payment handlers - we wanted more implementer support
<nicktr> ...webauthn was something that we cited
<nicktr> ...and now we have a joint task force
<nicktr> ...(ian runs through adoption objectives)
NickTR: I didn't include in my
list of 5 ... but interested in hearing from the group ... is
on webauthn
... where would it sit wrt other priorities?
[We confirm timing of two task forces: joint task force is half hour before Card Payment Security TF[
Gerhard: I think WebAuthn as a
standard is not the ideal kind of wording, but I'm picking up
the challenge between PSD2, SRC, etc.
... challenge between authenticating the cardholder to both
merchant and issuer
... delegating authentication (or authentication in two
domains)...that's something that will make payment handlers
more attractive if we can solve that problem.
https://github.com/w3c/webauthn-pay/wiki/Use-cases
Gerard: It's probably a more
acute problem for WebAuthn. Not sure we need to add to our
priority list
... maybe we just "keep track" of what's going on.
<Zakim> danyao, you wanted to ask about developer adoption
danyao: I want to comment or
question merchant / developer adoption
... from a Chrome perspective on developer adoption, it seems
like there may be a difference between payment solutions
developer and merchant developers
... our sense is that the APIs in the WG are "lower level
primitives" that provide some capabilities ....new UI patterns
etc.
... how these primitives are turned into an end-to-end solution
requires more work
... this is more true with payment handlers than basic
card
... we are thinking it would be good to clarify messaging that
PR API is lower layer for payment service provider
solutions
... and merchants may not need to be users of them.
NickTR: I think that's a helpful
perspective
... I think "Adoption" is our priority; we likely have
different communities...good nuance
<nicktr> ian: I agree with the characterisation
https://github.com/w3c/payment-request-info/wiki/FAQ
<nicktr> ...should we be updating our FAQ to reflect this messaging?
<danyao> +1 to keeping the merchant perspective
danyao: As a browser vendor that
supports some of these APIs is "I want to build a checkout
flow...when do I use the API v. a library v. a form?"
... we should probably provide some guidance about how to
choose from among these
... from our vantage point, I think this messaging is not clear
in the community
... I think the priority list for 2020 aligns with Chrome's
priorities pretty much
... we also want to emphasize PH API
... to move in the direction ultimately of sunsetting Basic
Card
... it's important that we clarify also that the core API is to
be built on for other experiences like coupons.
...clarification: "sunset Basic Card" means sunset the chrome
built in payment handler for it.
https://github.com/w3c/webpayments/wiki/prapi-deployment-faq
<scribe> ACTION: Danyao to work with Ian and Justin on updating the FAQ regarding deployment questions
NickTR: I am reaching out to merchants to see if they can give perspective on Irish market
[IJ is also reaching out to open banking folks]
NickTR: We invite people to offer to present, do demos, suggest agenda items
<nicktr> ian: demos are always welcome
<nicktr> +10 to more demos
<nicktr> ian: there will very likely be remote access
NickTR: Dublin is beautiful; I encourage you to make the trip
<nicktr> scribenick: nicktr
ian: this is a quick update
... getting PRv1.0 to proposed recommendation is a high
priority
... we need at least two browser implementations passing our
test suite
... I believe we had resolved the differences between safari
and chrome
... we now need more adoption and the privacy feature
danyao: yep - looks like the fixes are in from chrome and safari
ian: the implementation report
does not yet reflect these changes
... once that's done, we show those to the director
<Ian> 23 January
ian: we will give an update ou getting to FPWD on SRC at the next meeting
<Ian> Nick: Thanks all for coming to the call! We have a mature core spec. Seems like a critical year for success --- need to get adoption!
<Ian> ...as ever, thank you all!
<Ian> ...in particular browser imlpementers!
<Ian> ..with that, until 23 Jan