- From: Ian Jacobs <ij@w3.org>
- Date: Tue, 28 Apr 2020 17:13:35 -0500
- To: Web Payments Working Group <public-payments-wg@w3.org>
- Cc: Clinton R Allen <clinton.r.allen@aexp.com>, Fawad Nisar <fawadnisar@discover.com>, Jalpesh Chitalia <jchitali@visa.com>, Benjamin Tidor <btidor@stripe.com>, Jeremy Wagemans <jezza@stripe.com>, Rouslan Solomakhin <rouslan@google.com>, Danyao Wang <danyao@google.com>, Justin Toupin <jtoupin@google.com>, Peter Saint-Andre <stpeter@mozilla.com>
Dear Card Payment Security Task Force,
At our 28 April call we will continue our pursuit of consensus for the proposed architecture for SRC through PR API [1].
Agenda:
* Comments from Discover
* Comments from American Express
* For discussion: use cases for merchant identifying SRCI through request data. Do people expect it to be a common use case that the merchant’s PSP
would be different from the SRCI? Also, where the PSP and SRCI roles are played by the same entity, are there still advantages in using PR API?
* SRC at WPWG code-a-Thon end of May:
https://github.com/w3c/webpayments/wiki/Code-A-Thon-2020
* User experience discussion: prolonging persistence versus facilitating login (or user recognition). What role could the Credential Management API [2] play,
including auto-login?
* Next call: 13 May
Call info:
- Usual call time: 11am-noon ET
- WebEx: http://www.w3.org/2018/11/cps.ics
- IRC: irc.w3.org in the channel #wpwg
Thank you,
Ian
[1] https://github.com/w3c/src/wiki/ProposedArchitecture
[2] https://www.w3.org/TR/credential-management-1/
[3] https://developers.google.com/web/fundamentals/security/credential-management
--
Ian Jacobs <ij@w3.org>
https://www.w3.org/People/Jacobs/
Tel: +1 718 260 9447
Received on Tuesday, 28 April 2020 22:13:41 UTC