--> https://lists.w3.org/Archives/Public/public-payments-wg/2018Sep/0022.html Agenda
---> https://w3c.github.io/webpayments-methods-tokenization/
<scribe> ACTION: stpeter to review edits to section 1 (Intro)
<trackbot> Created ACTION-104 - Review edits to section 1 (intro) [on Peter Saint-Andre - due 2018-10-02].
https://github.com/w3c/webpayments-methods-tokenization/issues/52
Add more detail to cryptogram flows
scribe: Facebook demo at TPAC
<Zakim> rouslan, you wanted to talk impl
rouslan: We think this is an
interesting spec
... we don't have immediate plans to implement but we are
looking at what the user-facing feature would be for this spec.
I think the spec looks promising but we are still figuring out
where it fits in.
IJ: what does that mean for Chrome?
Rouslan: Merchants that need
tokenization can get it in the short term through existing
wallets.
... however, if we can agree on a standardized tokenization
approach, this could make integration with merchants
easier.
... in the longer term I could see the value of this work.
IJ: Have you been thinking about questions like "onboarding beyond tokenization"?
Rouslan: Not so much. I have been thinking about merchant validation being delegated to players such as the networks.
Jonathan: Merchant registration is part of what the networks are doing, and we think it's key to ecosystem security.
IJ: Would other parts of the ecosystem be ok with Google returning a token without merchant validation?
rouslan: I think some sort of
trace will be needed (e.g., logging origin of merchant or
iframe PSP)
... for auditing purposes.
... but I note that canMakePayment does not fire for
standardized payment methods
IJ: I can see "convergence" of *Pay as one strategy, but another is "new payment handlers from issuers, etc."
Rouslan: I think that *Pay
convergence is a good first step (even if not yet
engaged)
... a first step could be "convergence on the data model" but a
later step could be adoption in a URL-based payment
method
...rather: first step is data model convergence with URL-based
payment method; second step is convergence on a single
(standardized) payment method
rouslan: Yep, that's what I said.
Ian: I will incorporate the convergence strategy into planning the tokenization discussion at TPAC.
Ken: One vision is the browser
offers tokenization service for merchant; may involve
merchant/browser agreements.
... also want to help get tokenization adoption to increase
payment security
IJ: I also want to hear more from issuing banks
Rouslan: I think it's still true that merchants are not yet asking a lot for tokens, but we see that the industry as a whole is moving to tokenization and 3DS, so we'd like to be at the forefront.
Ken: +1
https://github.com/w3c/webpayments/wiki/FTF-Oct2018
Ian: I expect to have two sessions given the large number of people, most of whom have not been in the task force. The first session will be an update session on Tuesday. We have about 30 minutes to cover topics such as these:
Ian: The second session would (if people want) be a breakout session. We have 2 2-hour breakout slots. I urge us to have a deeper conversation about this specification given that lots of relevant parties will be in the room.
9 October