dyevans

I have enabled currencylayer on that test site with my API key and it returns the same error. Although it is not obvious on the CurrencyLayer website I think you may have to pay to use anything other than USD as your default currency. This seems to be the case with all of the APIs you use. Given my site is very low traffic it is uneconomical for me to pay for an API service, plenty of other plugins seems to be able to pull their data from publicly available sources. I have found it easier to switch currency plugins to one that does not use these restricted APIs.

thanks for your help in any case,

Hi,

Your test website doesn’t have a WooCommerce install, so WPMLMC doesn’t work on it currently.

Hi, thanks for the reply,

Would definitely be a good idea to have the click and drop pricing, as I imagine that’s what most people using this plugin will be using.

I do find the limitation for the free version to be a little odd. If the only package size that is allowed is the one in the settings it kinda stops the plugin working all together.

either way, it would be good to just have that part greyed out in the free version to prevent the confusion!

• This reply was modified 1 year, 4 months ago by dyevans.

Having looked into this a little more, I can see that the Stripe Plugin itself allows payouts in other currencies, but the WooPayments plugin does not seem to allow this, if you attempt to add another account for payout it only allows you to add local US accounts. The Stripe plugin allows you to add a GB bank account with IBAN for dollar payments.

It may not be the best option in any case, but my original question still remains – if I can use multi-currency to list prices in USD but ultimately charge the customer in GBP.