Re: [w3c/browser-payment-api] Detecting Payment Method Availability (#316)

I'd think a "Buy Now" can always appear even without `canMakePayment()`.  

If the merchant does not yet know the information they need, like shipping address, then "Buy Now" should send the customer to a page that asks for it, as the payment API should not return any private information.  At that point, the merchant can call `show()` with whatever information they posses, and the user chooses their payment app.  It's great if the merchant supplied enough information.  If not, the payment app must ask the user for anything missing. 

As an aside, we should expect privacy-oriented browser venders, like say Brave, Tor, etc., to hard wire `canMakePayment()` to true, if they allow the payment API at all, so any payment flow that really depends on it will break in them. 

-- 
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/browser-payment-api/pull/316#issuecomment-265819526