← back to v135 · align-error-type-thrown-for-payment-webauthn-credential-creation-securityerror-n

conformance · v135

v135 · align-error-type-thrown-for-payment-webauthn-credential-creation-securityerror-n — 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.

browser: spec: https://github.com/w3c/secure-payment-confirmation/pull/281 chromestatus: #5160752715137024 generated 2026-06-01T08:35:00Z by conformance-author-v1-subagent
0
pass
0
fail
0
blocked
6
total
id contract kind verdict detail
publickeycredential-exists PublicKeyCredential is exposed — SPC credential creation flows through WebAuthn. spec ↗ exists
navigator-credentials-create-is-function navigator.credentials.create is a function used to create SPC credentials. spec ↗ typeof
spc-payment-extension-supported isPaymentCredentialCreation extension or 'payment' extension surfaces — the entry point for SPC credential creation. spec ↗ script
create-without-user-activation-rejects The Chrome 135 alignment expects missing-activation payment credential creation to use NotAllowedError rather than the legacy payment-specific SecurityError. spec ↗ script
securityerror-remains-a-distinct-domexception SecurityError remains a distinct DOMException name for policy, origin, and RP ID failures; it is no longer the expected missing-activation payment create error. spec ↗ script
notallowederror-domexception-constructible NotAllowedError is the aligned DOMException name for the Chrome 135+ missing-activation payment create failure. spec ↗ script