Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Intent to Implement and Ship: isSecurePaymentConfirmationAvailable API

148 views
Skip to first unread message

Nick Burris

unread,
Apr 20, 2023, 12:58:34 PM4/20/23
to blink-dev, Stephen McGruer, Kaan Icer

Contact emails

nbu...@chromium.orgsmcg...@chromium.orgic...@chromium.org

Specification

https://github.com/w3c/secure-payment-confirmation/pull/233

Design docs

https://docs.google.com/document/d/10zFazJRJMwNLKmH-GJRFMDs4rONIO5kF8TvdFydmGek/edit

Summary

This is a Javascript API to provide an easier way to check if the Secure Payment Confirmation[1] feature is available. Currently, the only way to determine SPC’s availability is to create a PaymentRequest with the required parameters[2], which is clunky and difficult in the case where a developer wants to check for SPC before starting to process a payment. [1] https://www.w3.org/TR/secure-payment-confirmation/ [2] https://github.com/w3c/secure-payment-confirmation/issues/81#issuecomment-868473461



Blink component

Blink>Payments

TAG review

None

TAG review status

Not applicable

Risks

Interoperability and Compatibility

Gecko: N/A (https://github.com/mozilla/standards-positions/issues/570)

WebKit: N/A (https://github.com/WebKit/standards-positions/issues/30)

Web developers: Positive (https://github.com/w3c/secure-payment-confirmation/issues/81) We've received feedback from web developers that an easier mechanism to check for SPC availability would be useful.

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests?


Flag name

--enable-blink-features=SecurePaymentConfirmationAvailableAPI

Requires code in //chrome?

True

Estimated milestones

Shipping on desktop114
Shipping on Android114

Anticipated spec changes

https://github.com/w3c/secure-payment-confirmation/pull/233


Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5165040614768640

This intent message was generated by Chrome Platform Status.

Yoav Weiss

unread,
Apr 26, 2023, 6:24:16 AM4/26/23
to Nick Burris, Rick Byers, blink-dev, Stephen McGruer, Kaan Icer
LGTM1

Thanks for adding feature detection capabilities!!

I see some discussion on the PR about it being approved but not yet landed, due to desire to move a previous version to PR.
That seems fine, but at the same time, I join +Rick Byers' request to make sure the situation doesn't last too long. Also, you may want to consider moving to a Living Standard model, that typically can avoid those kinds of issues..

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADvKJHOUZTzhNtVZj6bgeskfwt%2BN3YOMFTFCj5Z8nufpB3_xhw%40mail.gmail.com.

Nick Burris

unread,
Apr 27, 2023, 10:32:52 AM4/27/23
to blink-dev, Nick Burris, Stephen McGruer, Kaan Icer




Summary

This is a Javascript API to provide an easier way to check if the Secure Payment Confirmation[1] feature is available. Currently, the only way to determine SPC’s availability is to create a PaymentRequest with the required parameters[2], which is clunky and difficult in the case where a developer wants to check for SPC before starting to process a payment. [1] https://www.w3.org/TR/secure-payment-confirmation/ [2] https://github.com/w3c/secure-payment-confirmation/issues/81#issuecomment-868473461



Blink componentBlink>Payments

TAG reviewNone

TAG review statusNot applicable

Risks
Interoperability and CompatibilityGecko: N/A (https://github.com/mozilla/standards-positions/issues/570)


WebKit: N/A (https://github.com/WebKit/standards-positions/issues/30)

Web developers: Positive (https://github.com/w3c/secure-payment-confirmation/issues/81) We've received feedback from web developers that an easier mechanism to check for SPC availability would be useful.

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?Yes

Is this feature fully tested by web-platform-tests?
Flag name--enable-blink-features=SecurePaymentConfirmationAvailableAPI

Requires code in //chrome?True

Estimated milestonesShipping on desktop114Shipping on Android114

FYI, we missed the 114 branch so we're pushing this back to M115.
 
Link to entry on the Chrome Platform Statushttps://chromestatus.com/feature/5165040614768640

Mike West

unread,
Apr 28, 2023, 3:22:02 AM4/28/23
to Nick Burris, blink-dev, Stephen McGruer, Kaan Icer
LGTM2.

I think it would be valuable to extend the spec PR with more description of the considerations around when the feature is available (see discussion at https://github.com/w3c/secure-payment-confirmation/issues/81#issuecomment-1527105768), but I don't think that will meaningfully change the shape of the API or its meaning in Chromium's implementation.

-mike


--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

Chris Harrelson

unread,
Apr 28, 2023, 11:30:27 AM4/28/23
to Mike West, Nick Burris, blink-dev, Stephen McGruer, Kaan Icer

Stephen McGruer

unread,
Jan 23, 2025, 10:36:42 AMJan 23
to blink-dev, Chris Harrelson, Nick Navarro, blink-dev, Stephen McGruer, Kaan Icer, Mike West
Hey folks,

Can't quite I'm coming back to this thread near on 2 years later 🤣, but wanted to fyi that this didn't actually ship in the end. However, we are finally coming back to it now (honest - I have CLs out! :D), and expect to ship this sometime in the coming months. It may change shape before finally shipping (in particular, I'm musing over whether true/false is sufficient information and whether we could give developers more specific enum reasons without leaking user privacy) - I'll come back to the thread for approval if we want to ship anything substantially different.

Thanks,
Stephen

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

Chris Harrelson

unread,
Jan 23, 2025, 11:20:18 AMJan 23
to Stephen McGruer, blink-dev, Nick Navarro, Kaan Icer, Mike West
On Thu, Jan 23, 2025 at 7:36 AM Stephen McGruer <smcg...@chromium.org> wrote:
Hey folks,

Can't quite I'm coming back to this thread near on 2 years later 🤣, but wanted to fyi that this didn't actually ship in the end. However, we are finally coming back to it now (honest - I have CLs out! :D), and expect to ship this sometime in the coming months. It may change shape before finally shipping (in particular, I'm musing over whether true/false is sufficient information and whether we could give developers more specific enum reasons without leaking user privacy) - I'll come back to the thread for approval if we want to ship anything substantially different.

I'm assuming no other facts on the ground (signals, TAG feedback, etc) have changed in the meantime? If so, then this plan sounds fine to me.
 

Thanks,
Stephen

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

Stephen McGruer

unread,
Jan 23, 2025, 12:58:46 PMJan 23
to blink-dev, Chris Harrelson, blink-dev, Nick Navarro, Kaan Icer, Mike West, Stephen McGruer
> I'm assuming no other facts on the ground (signals, TAG feedback, etc) have changed in the meantime? If so, then this plan sounds fine to me.

Yes, sorry, no other changes at this time from the wider W3C community. Partners continue to ask for an easier way to feature-detect SPC, and finally we're getting around to delivering!


Thanks,
Stephen

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
Reply all
Reply to author
Forward
0 new messages