BigCommerce’s flexible Currency settings assist developers in building Multi-Currency storefronts that empower shoppers and merchants to do business in their currency of choice. Allowing customers to shop and check out in their native currency provides a more consistent and positive shopping experience, and maintaining price expectations throughout the shopping process encourages conversions for merchants.
This article provides a high-level guide to multi-currency concepts in BigCommerce as well as specific instructions on adding currencies via the control panel. For additional details on how currencies are surfaced throughout BigCommerce APIs, user interfaces, and storefront components, see How Currencies Work.
In BigCommerce, there are two types of currency that can be set up: a display currency and transactional currency.
Display currency - When a currency is set to display-only, shoppers in associated countries will see prices on the storefront in that currency, but the actual order will be transacted in the store’s default currency. Shoppers at checkout see the estimated price in the display currency with a note indicating the actual currency and amount to be charged.
Transactional currency - When a currency is set as transactional, shoppers in associated countries will both see prices on the storefront in that currency and be charged in that currency when they check out.
- If the shopper’s card-issuing bank differs from the merchant's bank account country, additional cross-border fees may apply that can change the final settlement amount.
- You can choose whether a currency should be display-only or transactional when adding or editing a currency.
Before setting up multiple currencies on a store, ensure your store is using the following:
- A Stencil theme.
- The Optimized One-Page Checkout (opens in a new tab) type.
- A multi-currency compatible payment gateway (opens in a new tab) set up and enabled. (Your store's default currency can use any gateway).
Additionally, review the Currency API reference to get aquainted with the endpoints and resources related to configuring multiple currencies.
Make sure to not change the store’s default currency. This could cause the currency to malfunction.
Transactional currencies can't be created via API, so they'll need to be added via the active MSF-enabled control panel. To do so:
- Navigate to Settings > Setup > Currencies, then select Add a Currency...
- Select the currency code that corresponds to the currency you want to set up, then click Next.
- Configure the currency’s display and transactional settings.
- Click Save.
For more in-depth instructions and helpful screenshots, see Adding a Currency (opens in a new tab) in the Help Center.
Do not change the default currency -- this may lead to unintended currency conversion issues. For instance, changing the default currency will not trigger price recalculation for the catalog. Additionally, changing the default currency will enable the newly assigned currency as transactional.
For details on how currencies are surfaced throughout BigCommerce APIs, user interfaces, and storefront components, see How Currencies Work
See the table below for a list of supported and unsupported features.
|Optimized One-Page Checkout
|Legacy Blueprint Themes
|Stripe Payment Gateway
|Other Payment Gateways
|Store credit in default currency
|Store credit in display currencies
|Customer group discounts in default currency
|Customer group discounts in display currencies
|Discounts created through Promotions
|Legacy coupon codes
|Storefront product filtering
|Merchants use this currency when any auto-conversion of pricing (product, tax, shipping, promotions) occurs.
|When a merchant displays prices in a currency on a storefront in which the shopper might or might not use to perform a transaction. Display currency is also often called "presentment currency" in the payments industry.
|Comprised of the currency and amount, the transactional currency is what BC passes to the payment provider and what is charged to a shopper's bank account. If there's a discrepancy between the storefront display currency and the transactional currency, a shopper has to pay a conversion fee and the conversion rate used is outside of BC's scope.
|The currency the merchant gets paid out to their bank account. If there's a discrepancy between the currency that a shopper transacts in and the currency in which a merchant settles, the merchant has to pay a conversion fee, and the conversion rate used is outside of BC's scope. The merchant can set their settlement currency through its payment provider.
|BigCommerce Conversion Rate
|Any conversion rate set on BigCommerce used to convert the product’s default currency pricing into a new non-default currency. The conversion rate can be static or dynamic.
|Static Conversion Rate
|One of the two auto-converted pricing options. If a merchant manually enters a static conversion rate, then the conversion rate will remain the same until and unless the merchant updates their currency settings to use a different conversion rate. Using this method avoids constantly fluctuating prices in non-default currencies.
|Dynamic Conversion Rate
|One of the two auto-converted pricing options. If a merchant selects a dynamic conversion rate, they've tied themselves to a currency-conversion service, which will update the conversion rate at a certain frequency. This helps shopper-facing pricing remain most aligned to the store's default currency and keeps the non-default currency conversion rate at market rate. The Merchant can either use BigCommerce Currency Service provided in the Currency setup page, or they can use the API to automatically update the exchange rate from their trusted source.
|Bank Conversion Rate
|Conversion rate is used by merchants' or shoppers' payment or credit card providers when auto-converting from store's transactional currency. This rate might not align with the BC conversion rate, and BC has no visibility into it.
|Rather than opting for auto-converting product pricing from default currency using the BigCommerce Conversion Rate, the merchant has a choice to set price per product per currency. You can implement multi-currency pricing through price lists.
Do Multi-Currency settings work with the Checkout SDK?
The Checkout SDK works with multi-currency. There is no additional setup needed for the SDK. After setting up currency in the Control Panel the SDK will work as normal.
Do my theme customizations work with Multi-Currency Settings?
If the theme is set up to show the currency on the storefront, there should be no issues. Please see your theme developer if that is not the case.
Can shoppers still select a currency?
Shoppers will still be able to select their currency of choice on the storefront. This will depend on the stores themes and customizations.
Will my analytics show in the transactional or display currency?
Analytics shows an approximate price in the store's default currency. This is based on the configured exchange rate. There is no abandoned cart analytics or web analytics such as Google Analytics. Currently, it does not break down analytics by currency.
How can I setup settlement currencies in Stripe?
Please reach out to Stripe for more information on setting up the account. Supported Settlement Currencies (opens in a new tab) (Stripe Documentation)
- How Currencies Work
- Using Price Lists (opens in a new tab)
- Managing Currencies (opens in a new tab)
- Tax (opens in a new tab)
- Supported Currencies (opens in a new tab)
- Supported Settlement Currencies (opens in a new tab)