← back to v145 · secure-payment-confirmation-ux-refresh
conformance · v145
v145 · secure-payment-confirmation-ux-refresh — conformance probe
5 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
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
payment-request-exists |
PaymentRequest is exposed — the entry point that brings up the refreshed Android UX. | exists | … | |
spc-is-secure-context |
SPC requires a secure context — feature detection should reflect that via isSecureContext. | exists | … | |
secure-payment-confirmation-method |
PaymentRequest accepts the 'secure-payment-confirmation' method identifier — feature exposed via constructor accepting this method. spec ↗ | script | … | |
payment-request-can-make-payment |
PaymentRequest.prototype.canMakePayment is a function — the surface that gates whether the refreshed UX would be shown. | typeof | … | |
spc-payment-entity-logos-output |
PaymentResponse.prototype is exposed — the type the refreshed UX returns to merchants, with new cancel/opt-out state codes. | exists | … |