Re: [w3c/browser-payment-api] Add `enableLegacyCheckout` option to PaymentOptions. (#365)

@nickjshearer,

My understanding is that `canMakePayment` is not a workable solution in some cases (see the thread linked to above for details from WorldPay). This is to be expected given that it's an API call that arose somewhat from compromise rather than ideals. Furthermore, it may turn out that some browsers implement `canMakePayment` in a way that prevents it from being an useful filter (i.e. it always returns `true`). In either of these cases, or simply in the case where a more privacy aware option is desired, having this additional feature is helpful.

In other words, this feature can be seen as an alternative to `canMakePayment` or as complementary; it can assist in filling in some gaps, given that `canMakePayment` is not an ideal API.

-- 
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/365#issuecomment-266184320