Re: [w3c/webpayments-methods-tokenization] Opportunities (#6)

Thanks Ian. It is looking good.


Keyur Patel
Consultant, Software Engineering
Design Team | DST

MasterCard
114 fifth Avenue| NYC, NY 10014
 Mobile 1-9144139421
keyur.patel@mastercard.com
[cid:image001.png@01D2CE34.FED3CB80]<www.mastercard.com>

From: ianbjacobs <notifications@github.com>
Reply-To: w3c/webpayments-methods-tokenization <reply@reply.github.com>
Date: Monday, May 15, 2017 at 4:05 PM
To: w3c/webpayments-methods-tokenization <webpayments-methods-tokenization@noreply.github.com>
Cc: "Patel, Keyur" <Keyur.Patel@mastercard.com>, Mention <mention@noreply.github.com>
Subject: Re: [w3c/webpayments-methods-tokenization] Opportunities (#6)


Hi @MasterKeyur<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_masterkeyur&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=26MTryrZ5Q9z5a8w6c1Ey8ex3ifnVQK4huobo7tSIVo&m=qZdxzd1b4n2qdVN-MLxiA4L1sIfcg94QqFGdtrwZuLY&s=Fk1Ft7ue0SGa266A2GwXZ-GMjOsDvLNcXvd6HdCDv80&e=>,

I've made edits to incorporate your suggestions. Please let me know if you are satisfied with this text.

Ian

  *   Pass tokens generated through payment apps (e.g., by vault services) and authorized by users to the merchant (or PSP) to eliminate PCI-DSS compliance issues (by eliminating merchant exposure to PANs).
  *   Enable liability shifts by making it easier to circulate tokens that result from strong authentication (e.g., mobile device-enabled biometrics).
  *   Harmonize how tokens are communicated to the merchant (through the Payment Request API) so that it is easier for PSPs integrated with the merchant to use the token to process a payment.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_webpayments-2Dmethods-2Dtokenization_issues_6-23issuecomment-2D301588959&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=26MTryrZ5Q9z5a8w6c1Ey8ex3ifnVQK4huobo7tSIVo&m=qZdxzd1b4n2qdVN-MLxiA4L1sIfcg94QqFGdtrwZuLY&s=Ny297IRgnVhEwEvm-XMn1MlaBmMFqtC0b5qohrub8Ro&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AbVP7-5FyEdZWeP9FEEW-5FCZQLTzzQeSSO6ks5r6K-5FwgaJpZM4NZv5V&d=DwMFaQ&c=uc5ZRXl8dGLM1RMQwf7xTCjRqXF0jmCF6SP0bDlmMmY&r=26MTryrZ5Q9z5a8w6c1Ey8ex3ifnVQK4huobo7tSIVo&m=qZdxzd1b4n2qdVN-MLxiA4L1sIfcg94QqFGdtrwZuLY&s=Bg6oXON8Pxlb3VRKsTmOicTPmjMNIRLSBHaFRg0OTO0&e=>.

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.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments-methods-tokenization/issues/6#issuecomment-301813322