- From: Anders Rundgren via GitHub <sysbot+gh@w3.org>
- Date: Sat, 27 Feb 2021 07:02:55 +0000
- To: public-webauthn@w3.org
@rsolomakhin Major issues with both solutions is that: - Most banks already have deployed mobile payment authorization systems limiting their interest in investing in new systems that "does almost the same thing". - Most people still use "PCs" for shopping making QR a fairly necessary part of the plot. FIDO Web Pay (in contrast to SPC), should be attractive for Open Banking TPPs who could finally get away from systems requiring users to select bank in order to make a purchase. Note though that Open Banking is a rather slow boat... Personally I believe the code that is currently intended to be a part of the browser, _should long-term rather be a part of the client platform_ because then the same scheme and "virtual cards" could be used everywhere. Such a change would be invisible to all actors. Conclusion: there is no "low-hanging fruit" or quick wins here. However, the availability of: - Built in FIDO token support - Built in universal Payment Handler should be of interest for all but suppliers of proprietary payment systems. -- GitHub Notification of comment by cyberphone Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1570#issuecomment-787017940 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 27 February 2021 07:02:56 UTC