[w3c/browser-payment-api] Should the list of transaction types be extensible? (#112)

Linked to #19 

There is an argument in favor of a well-defined list as these types provides hints to the user agent (which has no knowledge of payment method semantics) on how to display the payment details. This would be a challenge if the list was arbitrarily extensible.

That said, it may be that payment methods define new transaction types that they wish to support and they need a mechanism to do this. Should this be done purely in the payment method data?

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