Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175)

This issue ties in very closely with #185, and I think the proposal I make in there would provide a reasonably clear path forward. I'll reiterate them here:

>1. Any three-letter code MUST be an ISO 4217 code
>2. The payments API document will define a short list of codes of the form "+XXX" corresponding to well-known non-ISO-registered value instruments (e.g., "+BTC")
>3. Any other currencies can be represented by a URL, as proposed in #185.

If we can come to consensus around that as a general direction, I'm happy to draft text to this effect in the form of a PR.


---
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/175#issuecomment-219610639