- From: Ian Jacobs <ij@w3.org>
- Date: Mon, 18 Sep 2017 13:08:29 -0500
- To: Payments WG <public-payments-wg@w3.org>, "Bhattacharjee, Manash" <Manash.Bhattacharjee@mastercard.com>, Olivier Yiptong <olivier.yiptong@airbnb.com>, "Patel, Keyur" <Keyur.Patel@mastercard.com>
Participants in the tokenization task force, Our next call takes place 19 September at 11:30am-12:30pm ET. We will meet on irc.w3.org on #wpwg. Previous call: 5 September https://www.w3.org/2017/09/05-wpwg-minutes Ian ====== Agenda * Review changes to draft “Encrypted Card Payment Method”. Olivier, are you available to discuss? https://github.com/w3c/webpayments-methods-tokenization/wiki/encrypted_card] * Check status of updates to Network Tokenization Manash, Keyur, are you available to discuss? https://github.com/w3c/webpayments-methods-tokenization/wiki/Network-Tokens * AdrianHB will talk to us about a new idea (see below) * What will we present at TPAC and who will present? https://github.com/w3c/webpayments/wiki/FTF-Nov2017 * Next meeting. Proposed 26 September. Thank you, Ian ====== New idea from AHB 1) The handler sends the card details of a secure connection to the gateway (using a URL provided in the payment request) and gets back a reference of some kind which it passes to the merchant in the PaymentResponse. 2) The merchant then submits the payment to the gateway with the reference instead of the card details and also all of the other contextual data that the gateway requires. The gateway would then use the reference to loo kup the card details it has in temporary storage and process the payment. This is subtly different in that the reference would be a single use value for a set amount. The gateway may also provide the merchant with a customer identifier that is consistent across multiple uses of the same card to assist the merchant with customer engagement. -- Ian Jacobs <ij@w3.org> https://www.w3.org/People/Jacobs/ Tel: +1 718 260 9447
Received on Monday, 18 September 2017 18:08:38 UTC