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

> Presumably there is something bad that might happen as a result of some kind of validation? 

I have a feeling this is to do with currency codes that aren't valid international standards, especially in relation to Bitcoin. For example, in Swift `NSLocale.ISOCurrencyCodes().contains("BTC")` will evaluate to false. I guess the intent here was to prevent situations where user agents enforce the currency field contains an actual ISO code.

I wouldn't consider interpreting the field (for, say, displaying a currency symbol) as validation, but as you say, I think user agents will want to enforce requirements on that field, such as around length. 

The wording should probably be revisited and modified, or we should add some constraints to the currency field around length and valid characters.

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