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

I am not really sure I understand the idea here: what's basic card payment if not legacy payment? Does it make any sense for a merchant to say 'I'm going to update my site to use this new API, but *not* support basic card payment and fall back to my legacy form field checkout instead'?

Putting that aside, does it not make more sense for legacy checkout to just be another `supportedMethod` rather than a boolean property?

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