Re: [w3c/payment-handler] Just-in-time payment handler install (#240)

@jenan-stripe: I can see two approaches to `paymentRequest.canMakePayment()` with some benefits and drawbacks to both. We can figure this out together.

 * Option 1: If the app is not installed, `paymentRequest.canMakePayment()` returns `false`, even if the app supports just-in-time install.
 * Option 2: The HTTP header of the payment method may also specify what the browser should do for `paymentRequest.canMakePayment()`. The browser will read this information at the same time as checking whether the payment method supports a just-in-time install of a payment handler.

Does the group have any preference?

@adrianhopebailie: You're correct, the HEAD call would happen upon `new PaymentRequest(methods, cart)`, which is before `.show()`. The merchant may call `.show()` at any moment, but the browser has control of UX. If `.show()` happens before all HTTP headers have been read, I expect the browser to show a "Loading..." spinner sheet until all queries complete.

-- 
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-handler/issues/240#issuecomment-348221612