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

I do understand the problem WorldPay are talking about - but a much better way to solve this is just to make the legacy payment option another payment method just like basic card. 

The problem with this change as it stands is it's fundamentally incompatible with our charter. From your pull request (emphasis mine):

> If the <code>enableLegacyCheckout</code> value of <em>request</em>@[[\options]] is <code>true</code>, ***then provide an option on the user interface*** to complete checkout on the payee's website without selecting a payment method.

And from the [WG charter](https://www.w3.org/Payments/WG/charter-201510.html):

> This Working Group is chartered to Recommend programming interfaces; not user interfaces.

So I can't see how we can take this since it very clearly defines a user interface requirement, which the WG has explicitly said it's not going to do.

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

Received on Saturday, 10 December 2016 19:06:31 UTC