Contact emailsrou...@chromium.org, nbu...@chromium.org, dan...@chromium.org
SummarySecure payment confirmation augments the payment authentication experience on the web with the help of WebAuthn. The feature adds a new PaymentCredential credential type to the Credential Management spec, which allows a relying party such as a bank to create a PublicKeyCredential that can be queried by any merchant origin as part of an online checkout via the Payment Request API using the proposed secure-payment-confirmation payment method.
Link to “Intent to Prototype” blink-dev discussionhttps://groups.google.com/a/chromium.org/d/topic/blink-dev/myUR5gyd5Js/discussion
Interoperability and CompatibilityThis feature adds a WebAuthn credential type and PaymentRequest payment method type, so the interop risk is that other browsers do not implement these types. The PaymentRequest API allows developers to specify multiple supported payment methods in case some are not supported.
Gecko: Positive signal from informal conversation in W3C Payment Handler meetings. This feature is part of the Payment Handler API for which Mozilla recently filed an intent to prototype.
WebKit: No signal
Web developers: Positive
Positive signals from Stripe, which is interested in experimenting with the feature.
Goals for experimentationThe experiment will allow us to prove the user benefit of the feature, and gather feedback on the API changes, consisting of the PaymentCredential type added to the credentials API, and the secure-payment-confirmation payment method added to the PaymentRequest API.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?No