Adds a new static method to the Payment Request that allows web developers to get the capabilities of the browser's implementation of Secure Payment Confirmation. This helps web developers to easily know what capabilities are available for Secure Payment Confirmation so they can decide whether or not they want to use Secure Payment Confirmation with those capabilities.
This feature allows web developers to check for which capabilities are supported in the browser's implementation of Secure Payment Confirmation. Web developers want an easy way to check whether hardware browser bound keys are available with the Secure Payment Confirmation API and only use the API if if they are available. Without this method, web developers would need to initiate the Secure Payment Confirmation flow and force users to go through the dialog and authenticate just to ignore the data returned if it did not contain the browser bound key (in cases where browser bound keys are not available).
Docs: https://www.w3.org/wbs/83744/spc-mvp-2025/results https://github.com/w3c/secure-payment-confirmation/issues/290#issuecomment-3806454419 https://www.w3.org/2026/01/29-wpwg-minutes.html#3919 https://www.w3.org/2026/02/26-wpwg-minutes.html#bbkdetect
Samples: https://rsolomakhin.github.io/pr/spc-capabilities
Explainers: https://github.com/w3c/secure-payment-confirmation/blob/main/explainer-capabilities.md https://github.com/w3c/secure-payment-confirmation/issues/290#issuecomment-3806454419