See also: IRC log
https://lists.w3.org/Archives/Public/public-payments-strategy/2017Feb/0007.html
https://github.com/w3c/payment-request-info
https://github.com/w3c/payment-request-info/wiki/FAQ
IJ: (Note to self: add disclaimer
these are draft answers)
... Ok to start to push these to the site?
Ken, Andrew: Ok to put on site...but let's scrub site
https://github.com/w3c/payment-request-info/wiki/ImplementationStatus
IJ: I might say "experiment with" instead of "launch"
(IJ: need to learn more about WebView scenario)
Ken: if you are having interop
issues, where do you go to find out?
... e.g., not yet supported, or is a bug?
... What version of browser supports this spec?
IJ: Explain feature
detection
... I think it's tough to determine whether it's a spec bug or
a browser bug
Andrew: one scenario is interop
with apps that link to merchant sites
... the app's browser
Q. Is this API available for in-app payments?
Q. What's the expected impact on cart adoption/conversion?
IJ: I would mention autofill data from google, doing better than that, and don't have much data yet
andrew: +1 to shared narratives
Ken: Another approach I took
relates to the value of a 1-click button
... and impact
... I found some data (not sure how reliable) that showed the
difference in conversion rates on a site with 1-click v other
sites
Ian: +1 if we can link to public data
Ken: there is also public
information re: cart abandonment
... that's another piece of business case for why doing
this
Ken: I have seen this worldpay
chart a lot
... this one is aging; would be good to find more recent
IJ: +1 to looking at document reasons for abandonment and how this helps
https://www.w3.org/Payments/IG/wiki/Web_Payments_WG_Charter_FAQ
Ken: +1 to throwing it out there and let people contribute other questions and more recent/relevant data
Q. How/when will this solution scale?
IJ: Can you say more about what that one mean?
Andrew: Two elements to this one
<KenM> Source: http://www.formisimo.com/blog/shopping-cart-abandonment-rate/
Andrew: merchants want to know
where they fit into the timeline..and when they will see others
using it
... the other piece of this is from ecommerce platforms who
support lots of merchants ...how scalable is it for their
platform
IJ: Let's ask shopify!
... +1 to highlighting scalability, easy support for new
payment methods
Andrew: I have a 2016 chart...but not as familiar with the source
Ken: We can also see whether
there is consistency across years
... and in particular the stubborn hold outs that we think that
the spec addresses them
Andrew: For some people I've spoken with, they get the conversion topic
Ken: Segmentation changes the
speaking points
... there are also different topics such as user experience,
security
... you need a diverse set of benefits and value proposition to
address the diverse needs of each group
IJ: Happy to draft; but I can't do this for 10 days or so
Andrew: Not sure I could answer all the questions right now; would like to see them
Ken: I can take a shot at
answering some of them
... I can also point to who I think should be answering
them
IJ: would be great to come up with a strategy for answering each question
Ken: We also need diagrams
... or rather imagery for business/marketing people
... here's how you could adopt it into what you have
... maybe organized by segment
... some scenarios like (1) one button (2) small number of
buttons
[IJ notes two graphics: what the checkout page looks like (buttons); what the app selection looks like]
Q. What payment methods work with W3C's API?
Q. What wallets do I need to support?
(IJ got that question at CNP last year)
- Developer portal feedabck
- Support for a shared brand
Ken: PCI involvement might also
provide some assurances to merchants
... forward motion from pilots would also provide incentive and
motivation
... illustrate this is taking off
https://lists.w3.org/Archives/Public/public-payments-strategy/2017Feb/0007.html
https://github.com/w3c/payment-request-info
zkoch: Still working on it
https://github.com/w3c/payment-request-info/wiki/FAQ
zkoch: There are three columns
1) How do I use the API
(technical questions)
2) Marketing questions
(benefits, impact on conversinos, who has launched, etc.)
3) User experience flow questions
scribe: here's my checkout, how
is this supported?
... I need coupon cods
Molly: also fundamental questions
v. edge
... +1 to tech v. user experience
zkoch: On the question of "how we
think this will end up"
... we have a long integration guide, lots of technical details
and subtleties
... it's long and we get lots of questions anyway
... so I think we should break them out
... also helpful to breakout across audiences (on multiple
pages)
... part of the goal is to also have browser vendors get behind
single documentation site
... I think that there are incentive structures such as "PR API
supporting tokenization with easy UX"
Ken: clarity around PCI would
help
... visibility of a partnership would help
<zkoch> They move….slower?
<zkoch> ;)
Ken: Beyond developer guides, we need business-level value proposition
(Revisiting other topics)
- graphics
- value proposition
IJ: Got any visual?
Ken: I'm happy to contribute to
building visuals
... creating a few different examples
... e.g., if you are a large merchant with a single buy
button
... or if you are a merchant with your own pay button but have
also committed to other brands , how does it work?
<scribe> ACTION: zkoch to look at whether there are reusable mockups [recorded in http://www.w3.org/2017/02/24-wpwg-minutes.html#action01]
<trackbot> Created ACTION-53 - Look at whether there are reusable mockups [on Zach Koch - due 2017-03-03].
1) The flow
2) impact on merchant checkout sites for various segments
2) impact on user experience of data entry / choosing how to pay
zkoch: I will check out our pitch deck
[Recap]
Prep for FTF
- visuals
- FAQs
- brand questions
Proposed: 8am PT on 3 March
zkoch: that's sort of early
<zkoch> :D
Proposed: 9am PT on 3 March
Ken: +1
Molly: +1
Zach: +1
... but I am out 3 March