https://github.com/w3c/webpayments/wiki/Agenda-20180322
Shay: Pronounced "Shy"
... from BlueSnap...I am the system architect
... BlueSnap provides online payments; facilitate for
merchants
... we are integrating with PR API and expect a release
soon
... we are currently integrating with chrome and edge
... we'd like to help with tests / beta implementation
NickTR: Welcome to the group;
great to have new participant from the acceptance side
... please don't hesitate to ask questions
IJ: Let's chat about tokenization and encryption prototyping.
Rick: I work for American Express
on the product team working on tokenization, QR,
contactless
... previously I was at Visa Europe
... a lot of experience in the product and network side
... happy to lend a hand on tokenization and 3DS as well
NickTR: currencySystem was marked at risk; it is not being implemented.
https://github.com/w3c/payment-request/issues/617
<AdrianHB> There haven't been any implementations so it needs to come out. That doesn't prevent it coming back later if required.
<nicktr> ian: could roy or peter or adrian add any detail but I noted in PR API that Marcos had noted the feature
<nicktr> ...Marcos has a pull request to remove
<nicktr> ...that's certainly the safest way to do it
<Zakim> AdrianHB, you wanted to confirm the details of the PR
adrianHB: I think it would be
useful to summarize for everyone what will be implemented if
not currencySystem
... the removal of currencySystem doesn't present non-standard
currencies being used...it just means that if you use, say, a
cryptocurrency code, it will be accepted because it matches the
correct format, but browsers don't know what to do from a UX
perspective.
... if that's where we ok today, that's fine.
... if we in the future have new requirements around things
like loyalty points we can return to it
stpeter: I agree with AHB's description
AdrianHB: I blogged about this
some time ago; some voice support for inclusion but nobody
stepped up to impelment
... for now I think we should remove it and keep CR exit
simple
NickTR: It sounds like there is consensus for the removal
AdrianHB: I propose we do a Call
for Consensus
... we can send that out today.
IJ: I don't think this is strictly speaking required by process, but like the CfC idea
NickTR: Then let's issue a CfC to remove currencySystem from PR API
<AdrianHB> +1
<rouslan> +1
+1
<nicktr> +1
<stpeter> +1
https://github.com/w3c/payment-request/pull/694/files
IJ: Was AHB's request to address explicitly how non-ISO codes are handled?
AHB: At least it would be good to know what is currently supported.
<scribe> ACTION: AdrianHB to follow up with the editors to get info on current behavior and whether spec should say how non-standard codes may be handled
<trackbot> Created ACTION-87 - Follow up with the editors to get info on current behavior and whether spec should say how non-standard codes may be handled [on Adrian Hope-Bailie - due 2018-03-29].
<scribe> ACTION: Ian to draft CfC to remove currencySystem
<nicktr> ian: Web Commerce Interest Group is now meeting monthly
<nicktr> ...We have arranged for 26th March (10-11am ET) to get an update from Manu Sporny on Verifiable Claims
https://lists.w3.org/Archives/Public/public-webcommerce-ig/2018Mar/0002.html
<nicktr> ...and also decentralised identity ("DID")
https://docs.google.com/presentation/d/1qOjzppFLXtL7Is-MQ94BAyJhsZ3Otc2qKVz1hC0c10M/edit
<nicktr> ...Manu has produced some slides
<nicktr> ...I expect good turn out
https://github.com/w3c/webpayments/wiki/FTF-April2018
NickTR: Thanks again to Ripple
for hosting (at the hotel)
... FTF meetings are typically productive. We are proposing to
run a number of breakout sessions
... On Day 1 we'll check in PR API and company implementation
and CR exit status
... then in the afternoon of day 1 and on day 2 we have a
series of breakouts
IJ: I am trying to coax Zach to lead morning of day 1
NickTR: Looking for volunteers on other sessions as well
AHB: I volunteer for ILP and Tokenization
Ian: +1
... ...but let's sync up
... For 3DS let me ask at the task force call
IJ to AHB: Please see if the hotel has a polycom
<AdrianHB> ACTION: AdrianHB to ensure venue supports remote dial-in
<trackbot> Created ACTION-88 - Ensure venue supports remote dial-in [on Adrian Hope-Bailie - due 2018-03-29].
<nicktr> ian: we should figure out dinner plans
<nicktr> ...and also possibly Friday
<nicktr> ...and we will informally share info about arrival times
<nicktr> ian: I have some more notes
<nicktr> ...It's always good to see demos and prototypes
<nicktr> ...please feel free to show stuff off
<nicktr> ...For example, if Bluesnap have a demo, that'd be great
<nicktr> ...It looks like Tokenisation demo might not be available in time
<nicktr> ...though Mastercard still moving ahead
Ken: Some input ...
... thanks for organizing the FTF meeting and to Ripple for
hosting
<Shay> Will be happy to present our integration
Ken: the agenda looks good to
us
... Amex is very interested in PH API, tokenization, 3DS
... we are looking into a demo for singapore and will keep you
posted
IJ: MY thought was that developers would look at PH API and payments folks tokenization, but we can re-arrange as needed
<nicktr> ian: part of the 3ds tf discussions is what to have available for Singapore
<nicktr> ...and lots of work on flows
<nicktr> ...and work on working with web authentication
<nicktr> ...I don't think we'll have code but I'd love to have use cases
<nicktr> ian: ATOS have an intern working on a prototype of Paylib payment handler
<nicktr> ...and I will add a Bluesnap demo
<nicktr> ian: we are also aiming for Monday and Tuesday of TPAC week for on next F2F