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

ianbjacobs 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

@marcoscaceres,

Here is some additional detail. If you want to understand why some apps show up in the list and some don't, you need to be aware of:
 * Payment method identifier matching defined in PR API.
 * canMakePayment() matching, which is payment method specific 
 * payment method manifest matching
 * potentially other matching to come (e.g., if we add a layer for 3DS flows where the merchant can say "I only accept payments from apps that do 3DS flows given the jurisdiction in which I operate.")

I'd like to raise awareness of this. I welcome your suggestions of how and where that might be done.

Ian

-- 
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_r167872389