[w3c/browser-payment-api] 'Interactive' Bias in API (#467)

The WebPayment IG discussed a set of automotive use-cases, many of which have requirements to be non-interactive (for safety purposes).

We should review the API to see if the API lends itself towards non-interactive use.... Whilst I believe it does, the internal state machine does have an interactive status, and the spec a bias towards interactions with the user.

-- 
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/467