ianbjacobs

Discussed today with WebAuthn WG [1]. Things are still in flux so no concrete suggestions at this time. [1] https://www.w3.org/2023/05/03-webauthn-irc

Keeping tabs here on the relationship of this pull request to SPC: https://github.com/w3c/webauthn/pull/1957

Closing this issue due to inactivity and the fact that many points have been taken into account separately.

Another use case I have heard: authenticating the user to get the candidate card list in a click-to-pay (SRC) flow.

FIDO has made available a review draft of CTAP that includes a section that references SPC: 12.6. Third-Party Payment authentication (thirdPartyPayment) https://fidoalliance.org/specs/fido-v2.2-rd-20230321/fido-client-to-authenticator-protocol-v2.2-rd-20230321.html#sctn-thirdPartyPayment-extension

@adrianhopebailie, see this presentation from Sep 2023: http://www.w3.org/2022/Talks/emvco-tpac-2022.pptx

From a recent conversation, just to be clear: these extra logos would be optional to provide.

Discussed with WebAuthn WG today [1]. More discussion needed in WPWG, in conjunction with fallback UX discussions. [1] https://www.w3.org/2023/05/03-webauthn-irc

Discussed at [25 April meeting](https://www.w3.org/2024/04/25-wpwg-minutes.html). One idea is to ping the URL at a well-known URL to get a preferred name.

cc @dcrousso