← back to v139 · securepaymentconfirmationavailability-api
conformance · v139
v139 · securepaymentconfirmationavailability-api — 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-still-exposed |
PaymentRequest is exposed — Secure Payment Confirmation rides on top of the Payment Request API. | exists | … | |
secure-payment-confirmation-availability-namespace |
navigator.secure_payment_confirmation_availability (or a SecurePaymentConfirmation namespace) exposes an availability() method. spec ↗ | script | … | |
availability-returns-promise |
Calling the availability hook returns a Thenable (Promise) — the API is async by spec. | script | … | |
public-key-credential-still-exposed |
PublicKeyCredential is exposed — SPC enrollment reuses WebAuthn credentials. | exists | … | |
payment-request-supports-secure-payment-confirmation-method |
PaymentRequest can be constructed with the 'secure-payment-confirmation' method identifier without throwing at construction time. | script | … | |
no-construct-required-for-availability-check |
Before this API, authors had to construct a PaymentRequest to test availability — the new availability() API makes that unnecessary. We probe that the method is on a stable global hook (not requiring a PaymentRequest instance). | script | … |