https://www.w3.org/2018/12/src-prapi/
[IJ walks through three flows]
Lawrence: Can you clarify where we are in the process with these flows?
Ian: The goal is to build shared understanding on a set of flows that people think accurately reflect ways in which SRC and Payment Request can be used together. Once we have consensus on those, we can set about working with stakeholders on data models and ultimately to prototyping and experimentation.
deanezra: It looks from the flows that you're thinking that these cards or bank accounts will be controlled in the browser?
IJ: Some possibilities:
- Browser shows list of payment handlers
- Browser shows list of payment handlers and instruments you would get if you select the handler
- Browser shows list of payment handlers and instruments and user can select instrument (which is input to the handler)
deanezra: Chrome...if you add
cards to chrome it shows cards directly
... would need to deal with duplicates
IJ: Interesting question about SRC for card-in-browser
https://w3c.github.io/payment-handler/#userhint-attribute
IJ: Which of these best matches your view of SRC and PR API?
Lawrence: Enrollment is a
critical piece of this
... while we are exploring the payment side, we should also not
lose sight of the enrollment bit
<scribe> ACTION: Ian to create an SRC repo for issues etc
<trackbot> 'Ian' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., IFSF-EFT-WG-Lead, ijacobs).
Lawrence: It would be great to understand the enrollment user experience
<scribe> ACTION: Lawrence to read Nick's blog and the flow diagrams and bring feedback to the next call
<trackbot> Created ACTION-110 - Read nick's blog and the flow diagrams and bring feedback to the next call [on Lawrence Cheng - due 2018-12-19].
9 January 2019
Happy holidays!