RE: [Minutes] 3 April Tokenization Task Force call - PAR & MIT

All

I hadn’t seen this before I sent my other note but I think it gives pointers to similar information that I provided.

While I cannot provide specifics about Mastercard’s implementation of PAR, I can confirm it’s live and has been for some time. There is some limited public information available in the Mastercard rules that can be found here: https://www.mastercard.us/en-us/about-mastercard/what-we-do/rules.html


This provides the Mastercard specifics on the use of PAR beyond what EMVCo has defined.

Just wanted to clarify that Mastercard has a live implementation of PAR and other brands also do as far as I am aware.

Simon

Simon Dix
Vice President
Industry Standards

Mastercard
2200 Mastercard Blvd | O Fallon MO 63368-7263 USA
tel +1-636-722-2391
[cid:image001.png@01D3CC1E.DDA79930]<www.mastercard.com>



From: Kenneth Mealey [mailto:Kenneth.Mealey@aexp.com]
Sent: Tuesday, April 3, 2018 5:36 PM
To: giulio@apple.com; Ian Jacobs <ij@w3.org>
Cc: Web Payments Working Group <public-payments-wg@w3.org>; Richard Garreth Waller <Richard.G.Waller@aexp.com>; Clinton R Allen <clinton.r.allen@aexp.com>
Subject: RE: [Minutes] 3 April Tokenization Task Force call

Hi Giulio;
Hope you are well.

As you may know, some of the challenge with integrating EMVCo’s ‘work in progress’ material into the W3C’s ‘work in progress’ material is navigating what’s public and what’s not, at any given point in time.  As I don’t represent AXP in EMVCo, I can’t represent the current status of EMVCo’s PAR, i.e. has not yet been released to market and no support dates yet set.  However, to be helpful in the meanwhile, I’ll share the below links and attached PR announcement (all in the public domain) that provide ample detail on what PAR is and what it’s intended to do.

https://www.emvco.com/document-search/?action=search_documents&publish_date=&emvco_document_version=&emvco_document_book=&px_search=PAR<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.emvco.com_document-2Dsearch_-3Faction-3Dsearch-5Fdocuments-26publish-5Fdate-3D-26emvco-5Fdocument-5Fversion-3D-26emvco-5Fdocument-5Fbook-3D-26px-5Fsearch-3DPAR&d=DwMGaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=jyw_awFUVVx8y8ukyWYfH87_pCDXQdUacY1L8A1pDX0&m=VKY5n2uIH_7YR_9DrTEflJ39Ud2ylFhz0DLJT1zygZg&s=NPzYWF8u6--9KalQUUZ2sTus8v64P4VzH7xQ__MoYGU&e=>

https://www.emvco.com/terms-of-use/?u=wp-content/uploads/documents/EMVCo-Website-Content-Webinar_PAR_October-2016.pdf<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.emvco.com_terms-2Dof-2Duse_-3Fu-3Dwp-2Dcontent_uploads_documents_EMVCo-2DWebsite-2DContent-2DWebinar-5FPAR-5FOctober-2D2016.pdf&d=DwMGaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=jyw_awFUVVx8y8ukyWYfH87_pCDXQdUacY1L8A1pDX0&m=VKY5n2uIH_7YR_9DrTEflJ39Ud2ylFhz0DLJT1zygZg&s=ggrScB5Fm4MeXrvdqaxbO_9-ja3w8cQmwFse0N1Peww&e=>

Kind regards,
Ken

From: giulio@apple.com<mailto:giulio@apple.com> [mailto:giulio@apple.com]
Sent: Tuesday, April 03, 2018 5:45 PM
To: Ian Jacobs <ij@w3.org<mailto:ij@w3.org>>
Cc: Web Payments Working Group <public-payments-wg@w3.org<mailto:public-payments-wg@w3.org>>
Subject: Re: [Minutes] 3 April Tokenization Task Force call

Hi Ian and WG,
regarding tokenization, it would be great to hear more about PAR (=Payment Account Reference) and MIT (=Merchant Initiated Transactions) in Singapore, ideally from the networks, and how they address some of the current token shortcomings, and over what timeline.

Best
Giulio





Giulio Andreoli
 Pay
giulio@apple.com<mailto:giulio@apple.com>
+1 (415) 218-1787

On Apr 3, 2018, at 9:44 AM, Ian Jacobs <ij@w3.org<mailto:ij@w3.org>> wrote:

Hi all,

Minutes from today’s tokenization task force call:
https://www.w3.org/2018/04/03-wpwg-minutes<https://urldefense.proofpoint.com/v2/url?u=https-3A__isolate.menlosecurity.com_1_3735928037_https-3A_www.w3.org_2018_04_03-2Dwpwg-2Dminutes&d=DwMGaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=jyw_awFUVVx8y8ukyWYfH87_pCDXQdUacY1L8A1pDX0&m=VKY5n2uIH_7YR_9DrTEflJ39Ud2ylFhz0DLJT1zygZg&s=7tkKesrfRocCvhZLpb2QmVnf1id4x2r-K2BRMhjEI_w&e=>

The next call (after Singapore) will take place 24 April.

Thank you,

Ian
--
Ian Jacobs <ij@w3.org<mailto:ij@w3.org>>
https://www.w3.org/People/Jacobs/<https://urldefense.proofpoint.com/v2/url?u=https-3A__isolate.menlosecurity.com_1_3735928037_https-3A_www.w3.org_People_Jacobs_&d=DwMGaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=jyw_awFUVVx8y8ukyWYfH87_pCDXQdUacY1L8A1pDX0&m=VKY5n2uIH_7YR_9DrTEflJ39Ud2ylFhz0DLJT1zygZg&s=dBLYD4B-n7SnlLLsUsKn2n6RM9RrCBiliE_Q5oEZPys&e=>
Tel: +1 718 260 9447




________________________________
American Express made the following annotations
________________________________

"This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you."

American Express a ajouté le commentaire suivant le
Ce courrier et toute pièce jointe qu'il contient sont réservés au seul destinataire indiqué et peuvent renfermer des renseignements confidentiels et privilégiés. Si vous n'êtes pas le destinataire prévu, toute divulgation, duplication, utilisation ou distribution du courrier ou de toute pièce jointe est interdite. Si vous avez reçu cette communication par erreur, veuillez nous en aviser par courrier et détruire immédiatement le courrier et les pièces jointes. Merci.
________________________________
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.