Re: [w3c/webpayments-payment-apps-api] Revisiting payment app filtering (#96)

@adamroach, wrote:
> And I'm pretty confident that doing so does not involve any network interaction whatsoever.

This is the case for `canMakePayments()`, which is synchronous. But not the case for `canMakePaymentsWithActiveCard()`, as [Apple's own docs state](https://developer.apple.com/reference/applepayjs/applepaysession/1778000-canmakepaymentswithactivecard). 

@nickjshearer? Can you kindly confirm if Apple Pay makes a network request when `.canMakePaymentsWithActiveCard()` is called, as per the [`canMakePaymentsWithActiveCard()`documentation](https://developer.apple.com/reference/applepayjs/applepaysession/1778000-canmakepaymentswithactivecard) states. 

@tommythorsen, wrote: 
> The speed requirements on these two mechanisms are different. Since PaymentRequest.canMakePayment() most likely is called during page load, it's not a big deal if it talks to a server and returns an answer slowly, since it happens at a time when everything else is slowly being constructed as well. canHandle() on the other hand, may be invoked by the PaymentRequest.show() function, at a time when user interface is being shown to the user, and a list of payment options is being populated before the eyes of the user. This situation calls for a snappier response.

This is imposing UX/UI ideas on the spec: consider, the list of payment providers could be incrementally shown or become enabled as each becomes ready:

![screenshot 2017-02-07 14 43 17](https://cloud.githubusercontent.com/assets/870154/22677049/ce701826-ed43-11e6-8313-6f6ed8fd4872.png)

In the above, "wallet.com" is not ready yet for whatever reason.  

> The Apple Pay methods mentioned above, are equivalent to the PaymentRequest.canMakePayment() function, not to the canHandle() function. The fact that these Apple Pay methods might be asynchronous and may talk to the server, does not influence the speed requirements on the canHandle() filtering mechanism.

If the above holds, then I'd be in support of @rsolomakhin's [proposal](https://github.com/w3c/webpayments-payment-apps-api/issues/96#issuecomment-276423629)

 

-- 
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/webpayments-payment-apps-api/issues/96#issuecomment-277898356