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

+1 to not specify how to display currencies.

My preference would be to keep things simple and go with something like "[A-Z0-9]{3-10}" (similar to @rsolomakhin's preference, but allowing for the often longer symbols in [this list](https://coinmarketcap.com/currencies/views/all/)).

-0.5 to mandating URLs for non-ISO symbols (although, like @rsolomakhin, I'm ok with free-form strings that might happen to be URLs).

I honestly believe that the problem of currency symbol conflict is not our job to solve. As long as the merchant has a way to pass a currency symbol to the payment app, the burden is upon them to agree what that symbol means, and the burden is upon the mediator to present this in a user-friendly way. At least for v1, I would prefer to not overcomplicate this.

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