13:57:05 RRSAgent has joined #wpwg 13:57:05 logging to https://www.w3.org/2021/10/26-wpwg-irc 13:57:10 Meeting: Web Payments Working Group 13:57:23 Agenda: https://github.com/w3c/webpayments/wiki/Agenda-TPAC2021 13:57:27 Chair: Nick 13:57:29 Scribe: Ian 13:57:55 present+ 13:57:58 present+ Anne_Pouillard 13:58:03 present+ Rouslan 13:58:05 present+ Davor 13:58:21 clinton has joined #wpwg 13:58:37 present+ Alain_Martin 13:58:41 present+ Stephen_McGruer 13:58:45 Anne has joined #wpwg 13:58:47 present+ John_Bradley 13:59:25 present+ Bart_de_Water 13:59:51 nick_shearer has joined #wpwg 14:00:05 present+ Clinton_Allen 14:00:13 present+ Nick_Shearer 14:00:41 takashi has joined #wpwg 14:00:47 Hemnath_Dhananjayan 14:00:53 present+ Hemnath_Dhananjayan 14:00:58 present+ Takashi_Minamii 14:01:04 present+ Eric_Alvarez 14:01:24 present+ Jordan 14:01:26 present+ Chris_Dee 14:01:52 present+ present+ Haribalu_Venkataramanaraju 14:01:55 present+ Haribalu_Venkataramanaraju 14:02:23 agenda+ Adyen/Airbnb pilot 14:02:26 ChrisD has joined #wpwg 14:02:29 agenda+ PayPal Topics 14:02:37 agenda+ I18N joint meeting 14:02:48 agenda+ Unlocking the Potential of the Internet of Value 14:03:03 present+ Solai 14:03:08 agenda? 14:03:10 agenda? 14:03:15 rouslan has joined #wpwg 14:03:24 present+ Rouslan 14:03:31 bryanluo has joined #wpwg 14:03:40 present+ 14:03:44 jeanLuc has joined #wpwg 14:03:54 present+ 14:03:54 present+ Manish 14:04:01 present+ Krunal_Patel 14:04:05 present+ Emil_lundberg 14:04:08 zakim, take up item 1 14:04:08 agendum 1 -- Adyen/Airbnb pilot -- taken up [from Ian] 14:04:09 aleksei has joined #wpwg 14:04:09 present+ 14:04:13 present+ Antoin_Cathelin 14:04:23 present+ Jayadevi_Natarajan 14:04:34 present+ Uno_Veski 14:04:38 present+ Solai 14:05:01 Davor: Our goal of implementing SPC was to reduce drop-off rate in challenge flow of 3DS. 14:05:14 ...we have about 10% drop-off rate ordinarily. 14:05:27 ...SCA is here to stay, so we want to streamline 14:05:28 Manish has joined #wpwg 14:05:36 ...we started working last April with W3C, Airbnb, Google 14:06:04 ...in August 2021 we had our first successful SPC payment in Airbnb environment internally 14:06:16 ...that led us to API changes 14:06:24 ...and then a stable version of the API in Chrome 95 14:06:33 ...we are ready to start the Airbnb demo in the next month 14:06:40 ...here's a video of our flow 14:06:50 present+ Rolf_Lindemann 14:07:13 present+ Aleksei_Akimov 14:07:27 Rolf has joined #wpwg 14:07:33 Davor: We faced some challenges along the way. 14:07:47 ...we needed to change our integration a bit to implement a graceful fallback to 3DS. 14:08:02 ...one thing that proved difficult was to track instrument enrollment across devices 14:08:17 ...we had to choose between "always authenticating" and relying on a cookie. There are advantages to each. 14:08:40 ...there is now a UI when there is no credential match; a cookie helps us avoid that UX 14:08:45 present+ Jonathan_Grossar 14:08:57 present+ Gerhard_Oosthuizen 14:09:12 Davor: We also wanted to be able to distinguish user canceling and genuine error 14:09:27 ...we use a cookie for this as well; if present the error is due to "canceling" 14:09:36 ..it's not a foolproof approach but it's the best we came up with. 14:09:54 ...if someone uses our integration in an iframe, this iframe can be sandboxed, which can limit or make our integration not work at all 14:10:12 ...we hope that, in the next steps, to address these challenges as well as a few others. 14:10:24 ...we are satisfied with progress so far and look forward to the demo. 14:10:35 jonathan has joined #wpwg 14:10:41 q+ 14:10:42 Gerhard has joined #wpwg 14:10:45 present+ Nick_Telford-Reed 14:10:49 q+ 14:11:06 q+ 14:11:13 ack clinton 14:11:32 hemnath has joined #wpwg 14:11:34 Clinton: There was a password in your flow. What was that for? 14:12:02 Davor: That password field is part of our challenge simulator. It's not part of SPC. You need to go through this ID&V before enrollment of the SPC credential. 14:12:12 ack ros 14:12:23 zakim, who's here? 14:12:23 Present: Ian, Anne_Pouillard, Rouslan, Davor, Alain_Martin, Stephen_McGruer, John_Bradley, Bart_de_Water, Clinton_Allen, Nick_Shearer, Hemnath_Dhananjayan, Takashi_Minamii, 14:12:26 ... Eric_Alvarez, Jordan, Chris_Dee, present+, Haribalu_Venkataramanaraju, Solai, bryanluo, benoit, Manish, Krunal_Patel, Emil_lundberg, AdrianHB_, Antoin_Cathelin, 14:12:26 ... Jayadevi_Natarajan, Uno_Veski, Rolf_Lindemann, Aleksei_Akimov, Jonathan_Grossar, Gerhard_Oosthuizen, Nick_Telford-Reed 14:12:26 On IRC I see hemnath, Gerhard, jonathan, Rolf, Manish, aleksei, jeanLuc, bryanluo, rouslan, ChrisD, takashi, nick_shearer, Anne, clinton, RRSAgent, Zakim, jeff, bdewater, 14:12:30 ... AdrianHB_, pea13, canton, dlehn, kirkwood, weiler, ljharb, benoit, rowan_m, manu, dlongley, slightlyoff, Travis, hadleybeeman, falken_, tobie, nicktr, hober, smcgruer_[EST], 14:12:30 ... Joshue108, ntelford, mkwst, Ian, jeffh, AdrianHB 14:12:38 Rouslan: Please same more about the iframe challenges and what needs improvement. 14:13:28 Davor: It's difficult to simulate this locally. Basically, Airbnb's integration is using a sandboxed iframe environment, which, for example, does not allow setting a cookie by embedded code. 14:13:37 q? 14:13:40 ack ros 14:13:52 qq+ 14:13:56 ack sm 14:13:56 smcgruer_[EST], you wanted to react to ros 14:14:00 ack ros 14:14:03 ack rouslan 14:14:29 smcgruer_[EST]: There's a general question - how to provide a good flow depending on whether user is enrolled or not enrolled, without leaking information. 14:14:45 q+ to wonder out loud about conditional ui 14:14:48 ...WebAuthn says "use a cookie" but we exist in a 3p context 14:15:03 ...and we'll be talking about no 3p cookies at all. I don't have suggestions right now 14:15:09 ack AdrianHB 14:15:19 AdrianHB: I have an idea. ;) 14:15:38 present+ Arno_van_der_Merwe 14:16:16 AdrianHB: A design goal from a long time ago was for the browser to mediate on behalf of the user, and to enable streamlined flows without revealing too much to the merchant site. 14:16:20 present+ Erhard_Brand 14:16:31 q? 14:16:56 AdrianHB: I think PR API and Payment Handlers could help address the issue that was raised. 14:17:13 q+ to muse on Payment Handlers as a 1p context 14:17:16 q? 14:17:19 ...Davor, have you thought about using SPC with other payment methods? 14:17:35 Davor: Personally I have not thought a lot about that yet (but my colleagues may have). 14:18:24 Antoine: We have had some discussions about using SPC in different contexts for delegation of authentication under PSD2. In open banking, for example, there are some challenges distinct from cards. 14:18:41 ...so the current focus is on refining our approach with cards before looking at other methods 14:18:48 q+ 14:19:01 Antoine: But some other payment methods might be interested in this. 14:19:03 q? 14:20:08 q- 14:20:10 qq+ 14:20:10 Antoine: The major challenge with other payment methods is that incentives are different (e.g., iDeal has a well-established SCA approach already) 14:20:37 Antoine: In Brazil SPC might be useful for debit card payments, for example. 14:20:44 ..but I do think that we'll see more usage of SPC 14:21:07 q? 14:21:12 ack nick 14:21:12 nicktr, you wanted to react to AdrianHB_ 14:21:36 NickTR: I'd like to continue the conversation around FIDO Europe WG who are talking with banks about FIDO for login. 14:21:51 ...I think if we get traction in that space, then SPC could be used "sort of for free" in an open banking context 14:22:01 ...we need a concerted cross-industry effort to get there 14:22:26 bryanluo has joined #wpwg 14:22:34 present+ Ryan_Watkins 14:22:49 Antoine: If issuers ask us to use SPC we'd be happy to do so. 14:23:00 ...but I agree we need an industry-wide push 14:23:23 ...issuers think first about COMPLIANCE rather than reducing fraud or user experience 14:23:34 ...we need to develop our messaging to speak to that audience 14:23:47 present+ Tomasz_Blachowicz 14:24:22 Antoine: We need, say, top 20 issuers in Europe and the rest will follow 14:24:24 q? 14:24:40 bryanluo_ has joined #wpwg 14:24:50 ack rouslan 14:24:52 rouslan, you wanted to wonder out loud about conditional ui 14:25:12 q+ 14:25:19 dezell has joined #wpwg 14:25:24 rouslan: i hear some concerns about "no credential found User Experience" 14:25:31 present+ David_Ezell 14:25:31 ...additionally we thought it was not going to disrupt the flow a lot. 14:25:44 ...but if you feel that it is an issue, do you think that Conditional UI might be a better approach? 14:26:16 ...the privacy of SPC comes in part from an ability to not be able to distinguish "no credential" from "cancel" 14:26:27 ...the UX is there to prevent a timing attack 14:26:31 zakim, close the queue 14:26:31 ok, Ian, the speaker queue is closed 14:27:35 q? 14:27:43 rouslan: With Conditional UI, the api returns a promise that "hangs." The "hanging" of the promise means either credential not found or user canceled. 14:27:56 ...I think with a hanging promise we can avoid the UI 14:28:07 ...if this is of interest please let us know 14:28:35 +1 14:28:35 [Say +1 if of interest!] 14:28:35 +1 to know more 14:28:38 +1 14:28:39 +1 14:28:53 +1 to learn more about what a "hanging promise" is 14:28:58 ack Gerh 14:28:58 +1 14:29:15 [From WebEx, Eric Alvarez says +1] 14:29:49 Gerhard: It would be interesting to build an open banking prototype to understand issues in more detail. 14:29:57 present+ Gargi 14:30:06 q- 14:30:37 Gerhard: With open banking a flow exists where you just pick your bank. You are redirected to the bank site (and no information is shared with the merchant). 14:31:20 ...in the general flow, your identifying instrument has not yet been shared with the merchant 14:31:32 ...but using SPC in this context MIGHT therefore leak more information than in the general flow 14:31:36 ....we need to be attentive to that 14:31:41 q? 14:31:44 present+ 14:31:46 RRSAGENT, make minutes 14:31:46 I have made the request to generate https://www.w3.org/2021/10/26-wpwg-minutes.html Ian 14:31:51 RRSAGENT, set logs public 14:32:03 q? 14:33:14 Alain: "Signed payment request" has been pushed in the Berlin Group but there is no enthusiasm to implement the change request. 14:33:24 Question: Would Alain be able to share details around those proposed changes? 14:33:27 John_bradley has joined #Wpwg 14:33:27 ...if people here would find it useful to do SPC in open banking, we may need to apply additional pressure. 14:33:41 NickTR: Ian, Adrian, and I spoke with them a month ago. 14:34:47 q? 14:34:55 zakim, close item 1 14:34:55 agendum 1, Adyen/Airbnb pilot, closed 14:34:56 I see 3 items remaining on the agenda; the next one is 14:34:56 2. PayPal Topics [from Ian] 14:34:58 zakim, take up item 2 14:34:58 agendum 2 -- PayPal Topics -- taken up [from Ian] 14:35:54 Gargi: This is an open question for this group. Recognizing the user is an important topic. We've been talking a lot about privacy at this meeting. Most browsers allow customers to manage cookies and allow them to delete data. 14:36:08 ..how are we thinking about tracking registrations going forward? 14:36:14 q? 14:36:16 ...how do we keep track of returning devices? 14:36:32 q? 14:37:12 Gargi: When you register a device? Are you seeing that privacy settings are making it difficult to track registrations? 14:37:19 ..how do you avoid re-registering customers? 14:37:46 Davor: We have seen it happen. If the user's browser deletes the cookie or 3p cookies are not allowed, we go through enrollment again. 14:37:49 present+ Susan_Pandy 14:38:01 present+ Kazuhiro_Hoya 14:38:12 Gargi: It's great that customers are increasingly privacy aware. 14:38:22 ...a lot of our identification relies on cookies. 14:38:42 q+ 14:38:50 q+ 14:39:14 Ian: We'll have some discussion tomorrow on user recognition. 14:39:19 ack clin 14:39:33 Clinton: Yes, this is a challenge, especially with cross-browser availability 14:39:37 ack sm 14:40:18 smcgruer_[EST]: On the browser front, the general thrust is that privacy be respected and changes are possible with user consent and understanding. 14:40:26 +1 14:40:27 ...we can share more information with user awareness. 14:40:50 Gargi: From a consent management approach, can there be out-of-the-box integration with browser? 14:41:15 Ian: Request Storage API 14:42:35 smcgruer_[EST]: Roughly speaking, the API intends to give user ability to share storage, with consent. 14:42:45 ..but there are some limitations to that API that don't make it great for payments 14:42:49 q+ 14:42:54 ...due to partitioned storage approach 14:42:56 ack AdrianHB 14:43:11 smcgruer_[EST]: +1 to exploring this space 14:43:15 ack AdrianHB 14:43:27 q+ to ask paypal whether they have issues with iframes or top-level cookies 14:43:29 Nick_Shearer: I can get some more details on Request Storage as well. 14:43:43 q+ 14:43:47 qq+ 14:43:48 -> https://developer.mozilla.org/en-US/docs/Web/API/Storage_Access_API Storage Access API 14:44:08 ack AdrianHB_ 14:44:08 AdrianHB_, you wanted to react to AdrianHB 14:44:30 AdrianHB: At the risk of being burned at the stake, part of the problem here is that we are trying to use general solutions for a very specific use case 14:44:52 q? 14:44:52 ...we are asking users to give general permissions for specific things, and that tends to confuse the user 14:45:14 ...PR API has the advantage of a UX that is specific to payments, and can offer specific behaviors for that use case 14:45:27 q? 14:45:31 ack ros 14:45:31 qq+ 14:45:32 q- 14:45:35 ack rouslan 14:45:35 rouslan, you wanted to ask paypal whether they have issues with iframes or top-level cookies 14:45:45 q- 14:45:57 rouslan: I agree that if a browser and user could know for sure that a payment was happening, that would be great for users. 14:46:09 ...but payments are very complex 14:46:15 ...I want to understand the PayPal question more 14:46:26 ...in my limited experience, PayPal uses redirects for payments 14:46:35 ...in that 1p context you have access to all your cookies 14:46:50 ...or are you explicitly interested in cross-origin iframes? 14:48:08 Gargi:Webviews are one conversation 14:48:19 ...for almost all iframes where we redirect for 3DS use cases we are sandboxed 14:48:21 q? 14:48:32 Rouslan: Thank you 14:48:33 q? 14:49:06 q+ 14:49:10 Gargi: Because of the lack of information we have, or the customers that we see coming back ... but we don't have a deterministic ID for them. ....we were wondering whether that is a problem for others 14:49:13 ack rouslan 14:49:19 +1 14:49:27 rouslan: SPC was designed to solve this problem 14:49:49 ...what does SPC not solve for you? 14:50:11 Gargi: What we wanted to do with Request Storage (or another approach) 14:50:17 q+ to muse on Payment Handler as a 1p context 14:50:19 ...please help us understand how SPC solves this 14:50:22 q? 14:50:26 ack sms 14:50:27 ack smcgruer_[EST] 14:50:27 smcgruer_[EST], you wanted to muse on Payment Handler as a 1p context 14:50:28 ack smc 14:50:41 Uchi_Uchibeke has joined #wpwg 14:50:44 smcgruer_[EST]: Payment handler was designed in this space. Gives access to a 1p context for payments. 14:51:13 ...I have some concerns about whether it's payment-specific enough, but it is designed to be a payment context that would support access to the data. 14:51:24 Hi do you mind sharing the link for the TPAC session today, please? 14:51:31 we should consider what a PH without its own UI might enable. 14:51:35 q? 14:51:35 q+ 14:51:58 ack rouslan 14:51:59 q+ 14:52:18 rouslan: people don't want to call SPC if they're not enrolled 14:52:35 ...do we think that the no credentials dialogue is the problem? 14:53:11 q+ 14:53:21 q+ 14:53:31 ack clinton 14:53:48 clinton: It sounds a lot like some of the challenges we look at with Secure Remote Commerce (SRC) 14:53:50 q- 14:53:52 q+ 14:53:52 +1 14:54:02 clinton: The relationship of instruments to users is Many-to-1 14:54:08 ...you need a cookie or similar to identify the person 14:54:22 ...and independent of the browser from there you determine the available instruments 14:54:50 ...the challenge is knowing the consumer before working with them as someone who wants to complete a payment 14:54:58 q? 14:55:02 zakim, close the queue 14:55:02 ok, Ian, the speaker queue is closed 14:55:28 ack Nick 14:55:55 Nick_S: We don't have a strong position on SPC yet (at Apple). I am interested in the desire to know more about the consumer before payment is initiated. 14:56:08 ...I think it really depends on the context in which the payment is made 14:56:20 ...I would be interested to dig further into what information people want to know. 14:56:39 q? 14:56:42 ack Ian 14:56:57 eg wouldn't "shipping address" be important, for example, to prevent accepting money if the merchant is unable to ship the user the item? 14:57:00 To answer Nick_S: What payment instrument types does the current user have that it can pay with? 14:57:27 that also matters for regional law things - it's not legal to ship alcohol to every state, for example 14:59:03 s/payment instrument types/payment instruments/ 15:00:22 zakim, close item 2 15:00:22 agendum 2, PayPal Topics, closed 15:00:24 I see 2 items remaining on the agenda; the next one is 15:00:24 3. I18N joint meeting [from Ian] 15:00:24 I believe the solution is sharing payment instrument identifiers in a "non trackable" way. i.e. The user has a payment instrument of type X with a temporary identifier (different for each tx) Y 15:00:27 zakim, take up item 3 15:00:28 agendum 3 -- I18N joint meeting -- taken up [from Ian] 15:00:44 ' The user has a payment instrument of type X ' can be a tracking vector 15:01:05 s/tracking/fingerprinting 15:01:42 I have made the request to generate https://www.w3.org/2021/10/26-wpwg-minutes.html Ian 15:01:47 xfq has joined #wpwg 15:03:04 addison has joined #wpwg 15:03:09 present+ 15:03:21 r12a has joined #wpwg 15:03:36 present+ Atsushi_Shimono 15:03:41 present+ 15:03:43 present+ Bert_Bos 15:03:46 present+ Richard_Ishida 15:04:03 present+ Fuqiao_Xue 15:05:00 plh has joined #wpwg 15:05:04 present+ 15:05:26 same issue here 15:05:59 https://github.com/w3c/payment-request/pull/971 15:06:12 Ian: introduces Issue 971 15:06:38 ...the plan is go ahead with the recommendation 15:07:11 @ljharb for regional law things: if I think of Shopify's checkout, the steps are contact info, shipping info, payments. so that determination if alcohol can be shipped would be made before payments 15:07:11 ...we have a couple of choices about how to fix: localizable (sp?) for a webwide solution or a more specific fix 15:07:39 q? 15:07:47 Ian: Is that the shared understanding of how we will proceed on PR API? 15:07:49 https://github.com/w3c/payment-request/pull/971#issuecomment-935364801 15:08:05 addison: Localizable is kind of stalled, but we think it's the right path forward collectively. 15:08:13 ...discussion is whether it belongs in WebIDL or somewhere else 15:08:31 ...one clarification on your summary: I'm not quite sure what the proposal is for Payment Request 15:09:38 ian: we propose a recommendation with "hooks" 15:09:50 ...if localizable comes along, we can use that 15:10:11 ...if it looks like it's going to be a long time, do a specific solution 15:11:17 q? 15:11:24 Ian: It would be an actual Recommendation with hooks 15:11:31 Addison: Our concern is backward compatibility. 15:12:03 ...people will want to interoperate with those. If we don't describe "lang" and "dir" from the outset and put normative language around them, we'll be in a state where we have non-internatoinlized fields 15:12:20 q+ 15:13:09 bdewater: ah k 15:13:41 q- 15:16:05 Addison: We'd like to see a platform-wide solution to the degree possible. 15:16:38 Ian: How is it going? 15:16:48 Addison: Slowly. Lots of specs with a small number of i18n-able strings 15:16:55 ...I recognize that what you have with PR API is relatively a corner case 15:17:19 q? 15:17:44 plh: It's not clear whether we are going to have a single general solution. 15:18:06 ...from a developer perspective, dir/lang would need to be optional (leveraging document default) 15:18:12 ..and there are ways to make it backward compatible 15:19:12 present+ Kris_Chapman 15:19:13 q? 15:19:55 nickTR: It's a pragmatic question. it sounds like we can either wait for Localizable on an undefined time scale. 15:20:16 ...or put in a 1-off implementation for dir/lang but implementers are unpersuaded because it's an edge case. 15:20:53 1) Wait for localizable, no rec 15:20:59 2) Rec with hooks for future localizable 15:21:03 3) Rec with dir/lang 15:21:47 NickTR: I think the WG's leaning would be #3. 15:22:03 Bert has joined #wpwg 15:23:01 smcgruer_[EST]: i missed the context, what JS language feature did you have in mind? 15:24:27 Ian: I think it's either #1 or #2 (that's what I'm hearing) 15:24:55 smcgruer_[EST]: hmm - maybe i'm not understanding. what lang does `croissant` have? 15:25:09 Addison: Personally it's not our job holding up Recommendations. This WG has worked with us well, and I appreciate the willingness to continue to work with us as we navigate the space. 15:25:31 ...I don't know if it's helpful overall for us to hold you up from Rec as long as we all have a commitment together to work on resolving the issue. 15:25:56 Addison: Right stake in the ground is important. 15:26:27 Ian: What else can we do to be helpful in your conversation about Localizable? 15:26:36 Addision: It is already helpful to say "this is hurting us not having this." 15:27:05 ...this is a large multi-year process. It's costly to have lots of 1-off solution. 15:27:15 ..that makes option #3 unattractive 15:27:48 r12a: Thank you for agreeing to put into the spec BEFORE recommendation a Note that says "This needs to be fixed but we don't yet know how to do it. We are working on it we will add to the spec." 15:29:42 NickTR: PROPOSED: We go forward with option #2 (Rec with hooks) 15:29:49 +1 15:30:00 +1 15:30:05 +1 15:30:39 ACTION: Ian to work with r12a on language for a Note in the specification 15:31:25 Ian: I expect to take to GitHub 15:31:50 .com/w3c/secure-payment-confirmation/issues/93 15:31:58 https://github.com/w3c/secure-payment-confirmation/issues/93 15:33:04 zakim, close item 3 15:33:04 agendum 3, I18N joint meeting, closed 15:33:05 I see 1 item remaining on the agenda: 15:33:05 4. Unlocking the Potential of the Internet of Value [from Ian] 15:33:10 zakim, take up item 4 15:33:10 agendum 4 -- Unlocking the Potential of the Internet of Value -- taken up [from Ian] 15:33:40 thank you I18N team! 15:33:56 zakim, take up item 4 15:33:56 agendum 4 -- Unlocking the Potential of the Internet of Value -- taken up [from Ian] 15:34:03 I have made the request to generate https://www.w3.org/2021/10/26-wpwg-minutes.html Ian 15:34:16 addison has left #wpwg 15:35:33 Uchi(Coil): We want to change payments on the web to be more Fair, Transparent, Faster 15:35:45 Bert has left #wpwg 15:36:26 r12a has left #wpwg 15:37:38 present+ Jeff_Hodges 15:37:52 present+ Jeffrey_Yasskin 15:38:24 xfq has left #wpwg 15:42:03 clinton has joined #wpwg 15:43:09 q? 15:44:56 -> https://github.com/interledger/rafiki Rafiki 15:46:54 q? 15:49:12 Uchi: Interledger can get us closer to more payments and more payment options for all users. 15:49:41 ...see more information at interledger.org, github.com/interledger/rafiki 15:49:44 ..and fynbos.dev 15:50:26 q+ to ask about coil's plans for payment request 15:50:30 q+ 15:50:34 Uchi: I look forward to collaborating with all of you to unlock value on the Web 15:50:43 ack rouslan 15:51:02 Rouslan: Is there anything that you envision a browser can do that would be useful for users in this space that cannot be done with a JS library? 15:51:59 Uchi: Improve Web monetization spec 15:52:02 q+ to also respond to rouslan 15:52:15 Uchi: And implement Web Monetization natively 15:52:41 Uchi: There's also an opportunity for a wallet system in the browser 15:53:10 q+ later 15:53:13 q- 15:53:20 ack AdrianHB 15:53:20 AdrianHB_, you wanted to also respond to rouslan 15:54:53 smcgruer_[EST]: We've invited Coil to contribute to the Chromium open source project. At this point I don't think the Chrome team has resources to invest in this directly, but we are very interested in the space. 15:55:25 Uchi: We also have some opportunities through the Interledger Foundation 15:55:52 ...which can support work by engineers on open source code bases 15:55:53 q? 15:55:58 ack nicktr 15:56:16 nicktr: What are Coil plans regarding Payment Request? 15:57:03 Uchi: I am open to advocating Coil's involvement in these APIs 15:57:17 q? 15:57:17 q? 15:57:43 NickTR: Thank you, Uchi 15:57:51 thanks Uchi! 15:57:52 [Adrian struggles with Audio] 15:57:56 There is an example of browser integration done in Firefox 15:58:02 NickTR: I'm excited by the work on ILP, Rafiki 15:58:16 ...I am hearing interesting use cases like bi-directional micropayments for streaming content 15:58:21 There are grants that have been made available for technical scholars to experiment with other browsers 15:58:35 NickTR: There are 1000s of use cases for that. 15:58:40 zakim, close this item 15:58:40 agendum 4 closed 15:58:41 I see nothing remaining on the agenda 15:58:45 Topic: Tomorrow 15:58:54 NickTR: Thanks everybody who spoke today. 15:59:04 Coil will likely try to use SPC for payments when it's own product evolves to making discreet payments like tips/donations 15:59:15 NickTR: ...tomorrow: Web Authn. Frictionless flows and user recognition 15:59:29 RRSAGENT, make minutes 15:59:29 I have made the request to generate https://www.w3.org/2021/10/26-wpwg-minutes.html Ian 16:00:06 zakim, bye 16:00:06 leaving. As of this point the attendees have been Ian, Anne_Pouillard, Rouslan, Davor, Alain_Martin, Stephen_McGruer, John_Bradley, Bart_de_Water, Clinton_Allen, Nick_Shearer, 16:00:06 Zakim has left #wpwg 16:00:09 ... Hemnath_Dhananjayan, Takashi_Minamii, Eric_Alvarez, Jordan, Chris_Dee, present+, Haribalu_Venkataramanaraju, Solai, bryanluo, benoit, Manish, Krunal_Patel, Emil_lundberg, 16:00:09 ... AdrianHB_, Antoin_Cathelin, Jayadevi_Natarajan, Uno_Veski, Rolf_Lindemann, Aleksei_Akimov, Jonathan_Grossar, Gerhard_Oosthuizen, Nick_Telford-Reed, Arno_van_der_Merwe, 16:00:11 rrsagent, bye 16:00:11 I see 1 open action item saved in https://www.w3.org/2021/10/26-wpwg-actions.rdf : 16:00:11 ACTION: Ian to work with r12a on language for a Note in the specification [1] 16:00:11 recorded in https://www.w3.org/2021/10/26-wpwg-irc#T15-30-39 16:00:14 ... Erhard_Brand, Ryan_Watkins, Tomasz_Blachowicz, David_Ezell, Gargi, jeff, Susan_Pandy, Kazuhiro_Hoya, addison, Atsushi_Shimono, r12a, Bert_Bos, Richard_Ishida, Fuqiao_Xue, plh, 16:00:14 ... Kris_Chapman, Jeff_Hodges, Jeffrey_Yasskin