From the Configuration menu, click Manage Currencies.
On this page, store administrators can create/publish additional currencies. Customers shopping on the site can choose from the published currencies, so they can see approximately how much the products would cost in their local currency. These currencies are for display purposes only! Transactions will always be sent to the payment gateway in the store's default currency. The payment gateway and the customer's bank will handle the exchange using live exchange rates.
In a MultiStore scenario, all payment gateways use the default store's master currency, regardless of each store's default currency setting.
The currency page is broken into several sections, explained below.
The bottom 2 sections will only appear if multiple currencies are set up.
Currencies attributes must be set properly for prices to be displayed properly on the front-end. Each attribute is explained below.
To add a currency, scroll to the bottom of the list of present currencies, and fill in the required fields on the New line, then click Save.
|This is the currency name, as it will appear to customers.
|This is the ISO 4217 currency code for the currency you are configuring.
|Not currently used
|This is the exchange rate, relative to your store's default currency. This rate can be entered manually for each currency, or retrieved from a live feed (see above for details). NOTE: The default currency will always ignore this field.
|If the currency is to be associated with a standard .NET display locale, put the locale name here (en-US, en-GB, etc), and the currency will be formatted according to that locale's standard.
|If the currency is not associated with a standard .NET locale (for example, the Euro is a common currency that has no .NET locale), this field is used to tell the software how to display prices in that currency. This string tells the software what symbol to use instead of a $ (and where to put that symbol), and what to use as delimiters (for thousands and for decimals). An example of this would be: €####,##
NOTE: While there are some currencies that use commas as the decimal separator and periods as the thousands separator (for example: 1.999,00), the .NET framework does not support this. Currencies that use this format can use the comma for the decimal separator, but should not attempt to use a period for the thousands separator. Large numbers will need to be formatted as 1999,99 in those currencies.
|If this box is checked, the currency will be available on the site.
|This determines in what order the currencies appear in the pulldown menu customers use to select their preference (see below). If set to 1, currencies display alphabetically.
This section is just for testing, to see how conversions will be handled between your currencies on the front-end of the site. No settings are affected by doing tests.
Live Exchange Rates
The store is able to connect to an online service run by the European Central Bank to pull in live exchange rates for many (but not all) currencies. This is a good way to ensure that your customers see an accurate price for the products on your site, and saves you from having to manually enter exchange rates. To request these live rates, simply click the Get Live Rates Button pictured below.
This feed uses the Euro as a base rate. If your store's default currency is not the Euro, you will need to use another feed to get live rates. To do this, populate the following Settings with the appropriate values. This is an advanced feature that will require a developer to create a custom XML package to handle the feed.
After clicking the 'Get Live Rates' buttons, two text fields with some XML will appear. Those are for debugging purposes for sites using live rates, and can generally be ignored unless you are having a problem with the live rates feed.
If multiple currencies are published on a site, customers will be able to choose which one they wish to use from a dropdown menu that displays on the storefront. This list is generated by the <%$ Tokens:CURRENCYSELECTLIST %> token (see here for more information on skin tokens).
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article