Deprecate and remove support for the `showOptOut` parameter in the Secure Payment Confirmation API (https://w3c.github.io/secure-payment-confirmation/#dom-securepaymentconfirmationrequest-showoptout) This parameter was designed to support developers in certain regions who believed they needed to offer an opt-out experience that was embedded into the Secure Payment Confirmation experience. (See previous feature entry - https://chromestatus.com/feature/5133415903920128). However, two years after adding the feature we are no longer seeing demand or uptake for this feature from web developers, and it constrains the future development of the API. As such, we are removing support for the `showOptOut` feature. Developers who need an 'opt out' mechanism are encouraged to display HTML UX to the user for this before calling SPC. To avoid silent breakage of developers who are setting this flag, construction of SPC with `showOptOut: true` will throw instead of silently ignoring the parameter. Spec issue discussion: https://github.com/w3c/secure-payment-confirmation/issues/274
The `showOptOut` parameter was designed to support developers in certain regions who believed they needed to offer an opt-out experience that was embedded into the Secure Payment Confirmation experience. (See previous feature entry - https://chromestatus.com/feature/5133415903920128). However, two years after adding the feature we are no longer seeing demand or uptake for this feature from web developers, and it constrains the future development of the API. As such, we are removing support for the `showOptOut` feature. Developers who need an 'opt out' mechanism are encouraged to display HTML UX to the user for this before calling SPC. To avoid silent breakage of developers who are setting this flag, construction of SPC with `showOptOut: true` will throw instead of silently ignoring the parameter. Spec issue discussion: https://github.com/w3c/secure-payment-confirmation/issues/274