secure-payment-confirmation
secure-payment-confirmation copied to clipboard
w3c
Secure Payment Confirmation (SPC)
When we create a new payment credential using your roaming credential, it's implied that the browser stores the credential `displayName` and `icon` so that when it's presented as an authentication...
In some payment systems (e.g., cards with 3-D Secure) merchants may with to authenticate the user in some non-payments use cases, including as part of storing a card-on-file or modifying...
What changes would be needed in SPC to support recurring payment use cases (e.g., display and signing of terms such as recurrence period or number of transactions)? It would be...
Hi, EMVCo colleagues raised an issue about the size of icon in the Chrome implementation of the transaction dialog. I have since heard a concrete proposal: the icon should be...
During TPAC, we observed that SPC-capable credentials can also be used for login. I speculated about the possibility of not-payment sites attempting to create SPC-capable credentials for the purpose of...
Ian and I were chatting today and discovered that we had very different mental models about when SPC authentication is invokable; it seems worthwhile to hash these out and come...
## Introduction We’ve heard a lot about ‘frictionless authentication’ at TPAC 2020 regarding SPC. It’s considered an essential requirement for merchant adoption in certain markets, due to the historic pain...
Based on conversations with developers, there is a clear desire for an easy mechanism to know whether a browser/user agent supports SPC. (Related: Issue #65.)
The[ initial proposal](https://github.com/w3c/secure-payment-confirmation#authenticating-a-payment) assumed that Payment Request API (PR API) should be used to trigger the SPC flow. The client code would use PR API providing the payment method as...
Some new requirements, some questions to the existing ones, and few corrections.