Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682)

marcoscaceres commented on this pull request.



> @@ -3340,6 +3358,11 @@ <h2>
         <h2>
           Payment Handler Matching
         </h2>
+        <p>
+          A user agent's payment handler matching algorithm takes into account

We can do it here, but as a note (i.e., class = "informative" and in `<div class=note>`)... like:

### How user agents match payment handlers
A merchant can accept payment by supporting many different payment handlers (e.g, "basic-card" and "`https://example.com/pay`"). As such, when a merchant initiates a request for payment, a user agent will typically display a "payment sheet" and give the user the option to select from the matching payments handlers available. The matching is done on: 
  
  * The payment method identifier: e.g., the user agent supports "basic-card", 
     but not "https://example.com/pay". So "basic-card" would be the only 
     option available to the user. 

  * User preference - a user might say they exclusively want to use "https://example.com/pay", and not be bothered with "basic-card". So the use completes the payment with the "https://example.com/pay" payment method. 

And so on... 

I think it would be overstepping to mention payment method manifest or 3D at this point (obviously). But if those two could be generalized, then we should include them above maybe... depends if it would imply support for something none supports yet.  

-- 
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/682#discussion_r168381132