@adrianhopebailie, > One may argue this is not very developer friendly but it has worked for the card industry for a few decades. Is this a viable solution? I think using a JSON number (which is how an integer would be represented) is problematic; different parsers may interpret certain values in different ways. In my view, the best way to protect integrity (with respect to parsing) is to use a string. Whether we express the value using the minor currency is another matter -- but I do think that if we use a currency code such as "USD", people will be confused if the amount is meant to be interpreted as cents. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/40#issuecomment-165538342Received on Thursday, 17 December 2015 18:26:31 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:12 UTC