This is the second origin trial for Secure Payment Confirmation, with the primary goal of increasing enrollment rate from the first origin trial by enhancing the user experience. We’ve added a browser UI prompt to improve trust and understanding, and enabled the feature for iframes for a more seamless user flow and better developer ergonomics.
Secure 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.
Intent to Prototype: https://groups.google.com/a/chromium.org/d/topic/blink-dev/myUR5gyd5Js/discussion
Intent to Experiment (v1):
This feature adds a WebAuthn credential type and PaymentRequest payment method type, so the interop risk is that other browsers do not implement these types.
Gecko: No signal
WebKit: No signal
Web developers: Positive
Positive signals from Stripe, which is interested in experimenting with the feature.
This second experiment will allow us to validate the hypothesis that an improved enrollment experience will increase enrollment rates. The original experiment’s goal still stands, 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.
We intend to experiment with Stripe on Mac and Windows to first prove the user benefit, and then extend the feature to all platforms, except WebView where PaymentRequest is not supported.
This is great news!
Question: M91, is that stable or canary build?