- From: Adrian Hope-Bailie via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Sep 2021 07:49:41 +0000
- To: public-webauthn@w3.org
@cyberphone what you are proposing is not impossible as an eventual end-goal: a Web Payments API that involves payment specific interactions with secure hardware (as opposed to going via generic WebAuthn). However, as I think you know, the scope of such an undertaking is HUGE. The goal of SPC, as @stephenmcgruer alludes to above, is to figure out if the market is even interested in merchant initiated payment authN. Hence, the current design has some hacks but it will get us on a road to more experiments and iterations and ultimately a solution that the market will actually use. SPC is not a payment method, your comments about branding and icons suggest you are either missing the point or refuse to listen (I've pointed this out to you before). SPC is an **authN mechanism** that can be used by ANY payment method. To leverage SPC a payment method must define a way for the merchant to discover the credential IDs it can use for a particular transaction. In a card transaction using 3DS, this is defined in the 3DS spec, other payment methods will define other ways for this to work. That's not in scope for SPC. Please stay on topic in this thread so we can focus on the issue of cross-origin auth. -- GitHub Notification of comment by adrianhopebailie Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1667#issuecomment-915847842 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 September 2021 07:49:44 UTC