Adds an additional cryptographic signature over Secure Payment Confirmation assertions and credential creation. The corresponding private key is not synced across devices. This helps web developers meet requirements for device binding for payment transactions.
This feature amends to Secure Payment Confirmation to keep up with syncing passkeys and device requirements for online payments. The Browser Bound Keys feature adds device binding in the browser to enabling payment use cases where device binding is required.
Browser bound keys are an additive feature for Secure Payment Confirmation, the risk is that other browser do not implement it.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Web developers should be able to inspect the new signature output which is defined in WebIDL, thus no changes are needed in devtools.
No milestones specified