| ▲ | raverbashing 13 hours ago | |||||||||||||||||||||||||
You certainly don't want your service caring about a test currency. Nobody is pricing their services in test currency They are either pricing in $ or in "units" and then converting upstream This is an even bigger foot gun than what's happening here | ||||||||||||||||||||||||||
| ▲ | skissane 11 hours ago | parent [-] | |||||||||||||||||||||||||
AWS supports billing in multiple currencies: https://repost.aws/knowledge-center/supported-aws-currencies So how is it a "foot gun" to add XTS as an additional currency, for internal use only? I presume AWS sets its prices in USD, and then converts them to the other currencies using the relevant exchange rate - the services themselves don't know about UAE dirham, but the billing system does. So XTS just becomes another exchange rate. You could even fix it as 1 XTS = 1 USD, although choosing a different exchange rate than parity is likely to surface more bugs. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||