← back to v145 · secure-payment-confirmation-browser-bound-keys
conformance · v145
v145 · secure-payment-confirmation-browser-bound-keys — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
payment-request-exists |
PaymentRequest is exposed — the surface that invokes Secure Payment Confirmation flows. | exists | … | |
payment-request-show-is-function |
PaymentRequest.prototype.show is a function — the call that triggers SPC and, with browser-bound keys, signs over an extra device-bound key. | typeof | … | |
secure-payment-confirmation-supported |
Secure Payment Confirmation feature detection is available when implemented, with WebAuthn still exposed as the underlying credential surface. spec ↗ | script | … | |
credentials-container-exists |
navigator.credentials is exposed — SPC credential creation and assertion ride the WebAuthn surface that now also returns a browser-bound key signature. | exists | … | |
public-key-credential-exists |
PublicKeyCredential is exposed — SPC assertions are PublicKeyCredential instances; the new browser-bound signature is carried alongside. | exists | … | |
subtle-crypto-available |
crypto.subtle is exposed — the browser uses platform crypto to mint the device-bound key pair. | exists | … |