<li>If the <a>current settings object</a>'s <a data-cite=

<a>allowed to use</a> the "<a data-lt="payment-feature">payment</a>"

feature, then <a>throw</a> a "<a>SecurityError</a>"

<a>DOMException</a>.

<p>

specified on the <a>iframe</a> element. See <a href=

"#feature-policy"></a> for details of how <a>allowpaymentrequest</a>

and <a data-cite="feature-policy">Feature Policy</a> interact.

</p>

</section>

<section id="feature-policy">

<h2>

Feature Policy integration

</h2>

<p>

This specification defines a policy-controlled feature identified by

the string "<code><dfn data-lt="payment-feature" data-nodefault=

"">payment</dfn></code>". Its <a href=

"feature-policy#default-allowlist">default allowlist</a> is

'<code>self</code>'.

<div class="note">

<p>

A <a data-cite="html#concept-document">document</a>’s <a data-cite=

"html/multipage/dom.html#concept-document-feature-policy">feature

policy</a> determines whether any content in that document is allowed

to construct <a>PaymentRequest</a> instances. If disabled in any

document, no content in the document will be <a>allowed to use</a>

the <a>PaymentRequest</a> constructor (trying to create an instance

will throw).

</p>

<p>

The <a>allowpaymentrequest</a> attribute of the HTML <a>iframe</a>

element affects the <a data-cite=

"feature-policy#container-policy">container policy</a> for any

document nested in that iframe. Unless overridden by the

<code><a data-cite=

"html/multipage/iframe-embed-object.html#attr-iframe-allow">allow</a></code>

attribute, setting <a>allowpaymentrequest</a> on an iframe is

equivalent to <code>&lt;iframe allow="fullscreen *"&gt;</code>, as

described in <a href=

"feature-policy#iframe-allowpaymentrequest-attribute">Feature Policy

§iframe-allowpaymentrequest-attribute</a>.

</p>

</div>