Re: [w3c/browser-payment-api] Making this API work with HTML Forms (#330)

I think I'm a bit confused by what "form data" means in this context. Does anything that can go into a JSON object constitute "form data"?

I don't think it's valid to compare this with "UAs that don't support this API" and their need to fall back to forms. By falling back to forms, they're limiting the payment methods that are available. For example, native-only forms of payment (e.g. Android Pay, Samsung Pay, etc) wouldn't be available. Put another way, there is no "pure form" equivalent of these forms of payment. As we get into more complicated forms of payment, this will continue to hold true.

Doesn't this also require having a Form for every form of payment that you support? That seems quite unfortunate to me.

-- 
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/issues/330#issuecomment-264035195