- From: Anders Rundgren via GitHub <sysbot+gh@w3.org>
- Date: Sun, 21 Jun 2020 10:07:12 +0000
- To: public-webauthn@w3.org
This Google-originated presentation https://www.w3.org/2020/02/3p-creds-20200219.pdf#page=5 indicates that WebAuthn for payments has a long way to go. There is no such thing as "Your PISP" because you are usually not supposed to have a relation with PISPs. To be fair this is a difficulty in the PISP concept in itself which is why I have proposed in Open Banking contexts that PISPs should stick to processing (by the user) already authorized requests. I.e. become "backend" services vouching for Merchants (and charging them for fees), which is a since ages back established concept, both technically and commercially. -- GitHub Notification of comment by cyberphone Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1396#issuecomment-647107376 using your GitHub account
Received on Sunday, 21 June 2020 10:07:14 UTC