Re: [w3c/browser-payment-api] Currency Types and Rendering (#185)

@adamroach,

> If the identifier is potentially a URL and there is no structure or other information to indicate what a human might call the currency, this may not be something that can be done sensibly. I'm trying to imagine our UX folks' response to this "well, just innovate!" suggestion, and... the discussion I envision doesn't go well.

What would implementations do if they could not, for whatever reason, retrieve the display information from a currency URL that was never previously retrieved or was not well-known? This case still has to be considered as it may occur even if we are to specify how to model the display information. I don't think the ability to pay should be denied, particularly if as soon as the Payment App is selected, the Payment App may be aware of the currency and be able to render it appropriately.

---
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/185#issuecomment-221909285