Infigo allows you to display multiple currencies and automatically update exchange rates using live data. When set up correctly, this ensures:
- Customers see the correct default currency
- Exchange rates stay up to date
- Manual maintenance is no longer required
This guide walks through how to set everything up, followed by common issues and how to resolve them.
Part 1: How to set up live currency conversion
To enable automatic exchange rates, you’ll need to configure the ExchangeRate-API provider.
Start by navigating to:
Configuration → Exchange Rate Providers
From here, select ExchangeRate-API exchange rate provider and open its configuration.

Depending on your setup, an API key may already be populated. If not, you can either use the shared Infigo setup or provide your own API key.

Once configured, go to:
Configuration → Currencies
Set the Current exchange rate provider to ExchangeRate-API and enable Auto update. This allows the platform to fetch and apply live exchange rates automatically.

At this point, your system is configured to use live rates. However, it’s important to understand that updates are not always instant. The frequency depends on the API tier being used.
Part 2: Understanding how exchange rates behave
Once live rates are enabled, they will override any manually entered exchange rates. However, this only happens when the API refresh occurs. Until then, previously entered manual values may still appear.
If you’ve added an additional charge (for example, a 5% markup), this also won’t show immediately. It is applied when the next API update runs, so there can be a delay before you see the effect reflected in pricing.
It’s also worth noting that currency matching is based on currency codes, not display names. This means you can safely rename currencies (e.g. “CAD” instead of “Canadian Dollars”) without affecting how the API updates them.
Part 3: Setting the correct default currency for users
To ensure customers see the correct currency by default, you need to consider how Infigo determines currency for guest users.
The most reliable approach is:
- Set your primary storefront currency (e.g. CAD)
- Disable Guest User Locale detection if you want all guests to see that currency by default
With the latest platform update, when Guest User Locale detection is disabled, the system will now correctly use the storefront’s primary currency for guest users.
If needed, logged-in users (or guests, if you expose a currency switcher) can still manually change currency.
Part 4: Common issues and why things don’t work
Even with everything set up correctly, there are a few common reasons why behaviour might not match expectations.
One of the most frequent is expecting exchange rates to update immediately. On the free API tier, updates typically happen less than once per day, so delays are normal.
Another common issue is thinking the API isn’t working because manual rates are still visible. In reality, those values remain until the next API refresh replaces them.
In some cases, exchange rates may not update at all. This can happen if the background task responsible for fetching rates isn’t running. Once enabled, the system will begin retrieving and applying exchange rates correctly.
Currency display issues can also occur due to browser behaviour. Currency selections may be stored in cookies, meaning changes won’t always appear immediately. Testing in a fresh incognito window is the best way to confirm updates.
Finally, inconsistencies can arise if different storefronts are using different exchange rate providers (for example, ECB vs ExchangeRate-API). For best results, ensure all storefronts use the same provider where possible.
Key takeaway
A successful currency setup in Infigo depends on two things working together:
- Correct configuration (exchange rate provider, primary currency)
- Understanding how the system behaves (update timing, cookies, user context)
Once both are aligned, currency display becomes predictable and exchange rates can be fully automated.