This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The HTTP Feature-Policy
header field's payment
directive controls whether the current document is allowed to use the Payment Request API. When this policy is disabled, the PaymentRequest()
constructor will throw a SyntaxError
.
Syntax
Feature-Policy: payment <allowlist>;
- <allowlist>
An allowlist is a list of origins that takes one or more of the following values, separated by spaces:
*
: The feature will be allowed in this document, and all nested browsing contexts (iframes) regardless of their origin.'self'
: The feature will be allowed in this document, and in all nested browsing contexts (iframes) in the same origin.'src'
: (In an iframe allow attribute only) The feature will be allowed in this iframe, as long as the document loaded into it comes from the same origin as the URL in the iframe's src attribute.'none'
: The feature is disabled in top-level and nested browsing contexts.- <origin(s)>: The feature is allowed for specific origins (for example, https://example.com). Origins should be separated by a space.
The values
*
(enable for all origins) or'none'
(disable for all origins) may only be used alone, while'self'
and'src'
may be used with one or more origins.Features are each defined to have a default allowlist, which is one of:
*
: The feature is allowed by default in top-level browsing contexts and all nested browsing contexts (iframes).'self'
: The feature is allowed by default in top-level browsing contexts and in nested browsing contexts (iframes) in the same origin. The feature is not allowed in cross-origin documents in nested browsing contexts.'none'
: The feature is disabled in top-level and nested browsing contexts.
Default policy
The payment
feature's default allowlist value is 'self'
.
Specifications
Specification | Status | Comment |
---|---|---|
Payment Request API | Candidate Recommendation | See Section 16. Feature Policy integration. |
Feature Policy | Editor's Draft | Initial definition. |
Browser compatibility
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
payment | Chrome Full support 60 | Edge Full support 79 | Firefox
Full support
74
| IE No support No | Opera Full support 47 | Safari No support No | WebView Android Full support 60 | Chrome Android Full support 60 | Firefox Android
Full support
65
| Opera Android Full support 44 | Safari iOS No support No | Samsung Internet Android Full support 8.0 |
Legend
- Full support
- Full support
- No support
- No support
- Experimental. Expect behavior to change in the future.
- Experimental. Expect behavior to change in the future.
- User must explicitly enable this feature.
- User must explicitly enable this feature.
See also
Feature-Policy
header field- Feature Policy
- Using Feature Policy