Promise<undefined> abort();

[NewObject]

Promise<boolean> canMakePayment();

readonly attribute DOMString id;

readonly attribute PaymentAddress? shippingAddress;

<h2>

<dfn>canMakePayment()</dfn> method

</h2>

<p>

The {{PaymentRequest/canMakePayment()}} method can be used by the

developer to determine if the <a>user agent</a> has support for one

<p>

A true result from {{PaymentRequest/canMakePayment()}} does not

imply that the user has a provisioned instrument ready for payment.

</p>

</div>

<p data-tests="payment-request-canmakepayment-method.https.html">

The {{PaymentRequest/canMakePayment()}} method MUST run the <a>can

</p>

</section>

<section data-dfn-for="PaymentRequest">

<p>

The <dfn>can make payment algorithm</dfn> checks if the <a>user

agent</a> supports making payment with the <a>payment methods</a>

</p>

<ol class="algorithm">

<li>Let |request:PaymentRequest| be the {{PaymentRequest}} object on

"[=state/created=]", then return <a>a promise rejected with</a> an

{{"InvalidStateError"}} {{DOMException}}.

</li>

<p class="note">

This allows user agents to apply heuristics to detect and prevent

abuse of the calling method for fingerprinting purposes, such as

<li>Let |identifier| be the first element in the |paymentMethod|

tuple.

</li>

</li>

</ol>

</li>

<code>canMakePayment()</code> protections

</h2>

<p>

</p>

<ul>

<li>Rate-limiting the frequency of calls with different parameters.

</li>

</ul>