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

Attempts with multiple methods creates a fingerprinting risk even with the rate limiting sadly.  And perhaps a quick series of forwards through TLDs can defeat the rate limiting anyways. 

Just some alternative approaches to `canMakeActivePayemnt()` : 
- Recommend to browser venders that they print big scary warnings whenever the user installs a payment method beyond the first one.  Realistically users should not give their browser more than one payment method anyways, due to the high risk of browsers being compromised.
- Recommend to browser venders that `show()` make it easy for users to return to the regular checkout process as if it failed. 
- Make `canMakeActivePayemnt()` a commitment to call `show()` that disallows any further network activity from the page except for calling `show()`. 

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