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

We ran out of time discussing this on 19 May.

Summary of discussion is:
* ISO codes have implicit UI hints for browser (combined with locale info) so these provide enough for common currencies
* To get uniqueness we need URLs or similar so that anyone can define a currency (crypto-currencies, loyalty points etc)
* Proposal to resolve a resource from URL that provides UI hints potentially introduces a whole bunch of new issues (what happens when the resource load fails, who hosts the resource, what are the caching rules etc)
* Proposal to include UI hints directly in CurrencyAmount type could open up security issues (need to verify this as currency is processed by payment app not browser)

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