Re: [w3c/payment-request] Editorial: change around payment handler language (closes #532) (#574)

dlongley commented on this pull request.



> @@ -841,9 +841,9 @@
               </li>
               <li>Determine which <a>payment handlers</a> support
               <var>identifier</var>. For each resulting payment handler, if
-              payment method specific capabilities supplied by the payment
-              handler match those provided by <var>data</var>, the payment
-              handler matches.
+              <var>data</var> contains filters that exclude the payment

Would the word "restrictions" or "constraints" help resolve the issue with the word "filters"?

"`data` may constrain which payment handlers can be used by specifying required capabilities. Only those payment handlers that have indicated their support for the capabilities specified in `data` match. If `data` provides no such constraints then any payment handler that supports the payment method identifier matches."

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/pull/574#discussion_r131727225