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

> Do browser vendors think this would make sense to treat this like a payment method, albeit special? Or would that be inefficient, confusing, etc.?

I don't think that we should be adding either the `"payee-legacy"` payment method or the `"enableLegacyCheckout"` option. If a merchant was using the services of https://a-payment-service.com, then `"https://a-payment-service.com"` should become a payment to participate in the ecosystem.

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

Received on Monday, 12 December 2016 20:32:21 UTC