>It also depends on how the data is used. If you display this value for informational purposes then it doesn't matter too much which rate was used. But if you use it for actual charges then this will matter significantly. If you're purchase is charged against US dollars the value will change for the foreign customer no matter what until the time the charge is made or the check is deposited or whatever causes the actual money transfer (unless you actually are the bank <g>)...

The client doesn't have any problem with that. As I said, this is not a shopping cart so only a few seconds elapse between the time the credit card form is shown, where the exchange rate is grabbed, just to enter credit card number and expiration date, and the time the save is done.

This is a problem most of the countries have because everything is based in US, mostly, and this is better to use that because of the international market. Here on the Universal Thread, I have a problem with that because it's Canadian based all the way. So, every year, we are loosing customers and this causes problem and support to do because of the confusion, as most of our customers are out of the country. For the client site, they are Canadian based but the decision was made to use US based rates. As only Visa and Mastercard can be deposited in Canadian US accounts, we would have face a problem to deposit Diners, Discover and Amex as those can only be deposited in Canadian CDN accounts. Otherwise, it would have been US all the way with no exchange rate. But, because all the cards cannot be processed the same way, the universal approach was to use US based rates, with exchange rate inclusion at the last minute just before the save.