ianbjacobs

I deleted @cyberphone's comment. This is not part of our agenda and was never more than a comment and therefore there is no need for noise about it on this...

Thanks @marcoscaceres!

+1 to @stephenmcgruer's characterization. * SPC is not a payment method. * SPC provides authentication capabilities useful for payments on top of Web Authentication. * SPC is currently implemented in...

Hi @gsnedders, SPC is integrated into 3-D Secure [1]. It does not replace 3-D Secure. 3-D Secure implementations may make use of a variety of authentication methods (e.g., OTP, FIDO,...

See Related WebAuthn issue https://github.com/w3c/webauthn/issues/1667

Based on various discussions including https://github.com/w3c/webauthn/issues/1667 I have heard three main use cases involving SPC and login: 1) "1p only". A credential: * CAN be used by the RP for...

Update from SPC task force discussion today: apparently "3p-nologin" is not considered an important use case. That should make life easier.

Below is an updated proposal for short and longer term management of Web Authentication credentials for use with SPC and login. Goal: * Reduce the total number of user registrations,...

See related issue regarding user awareness of cross-origin bit: https://github.com/w3c/secure-payment-confirmation/issues/154

@stephenmcgruer, for 2.ii, you link to SPC mention of conditional UX. It might also be useful in your post on 1667 to signal the relationship of this capability to conditional...