Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CanMakePaymentEvent. #170

Merged
merged 6 commits into from Mar 28, 2018
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 9 additions & 2 deletions index.html
Expand Up @@ -882,7 +882,9 @@ <h2>
<a>PaymentMethodData</a>.
</li>
<li>If <var>methodName</var> is a <a>standardized payment method
identifier</a>, filter based on <a data-lt=
identifier</a> or is a <a>URL-based payment method identifier</a>
with <code>"supported_origins": "*"</code> in its payment method
manifest, filter based on <a data-lt=
"PaymentInstrument.capabilities">capabilities</a>:
<ol>
<li>For each <var>key</var> in <var>methodData</var>:
Expand All @@ -901,6 +903,11 @@ <h2>
handler and return the result.
</li>
</ol>
<div class="issue" data-number="157">
This is the current thinking about filtering of payment instruments.
As we continue to experiment with implementations, we are soliciting
feedback on this approach.
</div>
<section id="capabilities-example" class="informative">
<h2>
How to specify capabilities
Expand Down Expand Up @@ -2247,7 +2254,7 @@ <h2>
"!payment-method-id#standardized-payment-method-identifiers">standardized
payment method identifier</dfn>, and <dfn data-lt=
"URL-based payment method identifiers" data-cite=
"!payment-method-id#standardized-payment-method-identifiers">URL-based
"!payment-method-id#url-based-payment-method-identifiers">URL-based
payment method identifier</dfn> are defined by the Payment Method
Identifier specification [[!payment-method-id]].
</dd>
Expand Down