W3C home > Mailing lists > Public > public-payments-wg@w3.org > September 2017

Re: [Agenda] 19 September Tokenization Task Force call

From: Adrian Hope-Bailie <adrian@hopebailie.com>
Date: Tue, 19 Sep 2017 14:43:41 -0700
Message-ID: <CA+eFz_+svgTOXcq4eZadQQAM6sHAsDhfyu3dy4qaPO6y0YkSAw@mail.gmail.com>
To: "Bhattacharjee, Manash" <Manash.Bhattacharjee@mastercard.com>
Cc: Ian Jacobs <ij@w3.org>, Payments WG <public-payments-wg@w3.org>, Olivier Yiptong <olivier.yiptong@airbnb.com>, "Patel, Keyur" <Keyur.Patel@mastercard.com>, "Ahuja, Sachin" <Sachin.Ahuja@mastercard.com>
Apologies for missing this call I had a scheduling mix-up.
Will review the minutes and revert if necessary

On 19 September 2017 at 07:51, Bhattacharjee, Manash <
Manash.Bhattacharjee@mastercard.com> wrote:

> Hi Ian/All
>
> Mastercard team is still working for the first prototype with Airbnb team
> to validate the Network Token specs – hoping to provide an update to the
> group in Oct 1st week or so.
>
> No additional updates from us this week.
>
> Regards
> Manash
>
> Manash Bhattacharjee
> Director Products
> Digital Payments
>
> Mastercard
> 114 5th Avenue | New York, NY
> Mobile +1 914 325 9792
>  <http://www.mastercard.com/>
>
> -----Original Message-----
> From: Ian Jacobs <ij@w3.org>
> Date: Monday, September 18, 2017 at 2:08 PM
> 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>
> Subject: [Agenda] 19 September Tokenization Task Force call
>
>     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://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.
> org_2017_09_05-2Dwpwg-2Dminutes&d=DwIFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jm
> CF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-
> BBAsow4cBHv&m=J_qpAFsoQDrdhMt40sG7InX7yr4ZxIZF6CNiDKeKrdg&s=KjrDEqjCnh-
> 0R7SzefcliQCW5kYVFnLgrhAT2tGhWP8&e=
>
>     Ian
>
>     ======
>     Agenda
>
>      * Review changes to draft “Encrypted Card Payment Method”.
>        Olivier, are you available to discuss?
>        https://urldefense.proofpoint.com/v2/url?u=https-3A__github.
> com_w3c_webpayments-2Dmethods-2Dtokenization_wiki_encrypted-
> 5Fcard&d=DwIFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=
> SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=J_
> qpAFsoQDrdhMt40sG7InX7yr4ZxIZF6CNiDKeKrdg&s=8zkv6Mz6R_d7I2c1RdyGqk3dpUPbO_
> zlvooeTqSC1Nk&e= ]
>
>      * Check status of updates to Network Tokenization
>        Manash, Keyur, are you available to discuss?
>        https://urldefense.proofpoint.com/v2/url?u=https-3A__github.
> com_w3c_webpayments-2Dmethods-2Dtokenization_wiki_Network-
> 2DTokens&d=DwIFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=
> SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=J_
> qpAFsoQDrdhMt40sG7InX7yr4ZxIZF6CNiDKeKrdg&s=KMe32Ra_
> wbOioH3T9Xk6xuj2dtCkNePIEvrt9oGPPOQ&e=
>
>      * AdrianHB will talk to us about a new idea (see below)
>
>      * What will we present at TPAC and who will present?
>        https://urldefense.proofpoint.com/v2/url?u=https-3A__github.
> com_w3c_webpayments_wiki_FTF-2DNov2017&d=DwIFaQ&c=
> uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-
> Vy1vSyomQyrploSd-zO3dm80-BBAsow4cBHv&m=J_qpAFsoQDrdhMt40sG7InX7yr4ZxIZF
> 6CNiDKeKrdg&s=oBlxCAtDviBNCrBveDbhHDqZ225Z7r28XA8effkuAx8&e=
>
>      * 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.
> org_People_Jacobs_&d=DwIFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jm
> CF6SP0bDlmMmY&r=SBvc3OSB46CItHx4ro7Bo0RfCmg-Vy1vSyomQyrploSd-zO3dm80-
> BBAsow4cBHv&m=J_qpAFsoQDrdhMt40sG7InX7yr4ZxIZF
> 6CNiDKeKrdg&s=KoVzF0up9H4UAy_SDl3tK7GqNVmU_2fv6y06Smu1lWk&e=
>     Tel: +1 718 260 9447
>
>
>
>
>
>
>
> CONFIDENTIALITY NOTICE This e-mail message and any attachments are only
> for the use of the intended recipient and may contain information that is
> privileged, confidential or exempt from disclosure under applicable law. If
> you are not the intended recipient, any disclosure, distribution or other
> use of this e-mail message or attachments is prohibited. If you have
> received this e-mail message in error, please delete and notify the sender
> immediately. Thank you.
>
Received on Tuesday, 19 September 2017 21:44:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 19 September 2017 21:44:36 UTC