Creating a product page for local currency and prices

Before starting this tutorial, make sure you understand the following topics from the Quick start section:

Nexio provides the capability of converting product prices based on the customer's local currency. This is known as multi-currency pricing (MCP). The conversion is done based on the current currency rates based on the settlement currency that is specified in the merchant account.



You must have a gateway connection that supports MCP in order to do this. To enable your merchant account for retrieving the currency conversion rates, contact Integrations Support.


You can take advantage of MCP in a couple different ways:

  • Quick: Use the Virtual terminal in the Nexio Dashboard and use existing saved card tokens from your customers. This method requires no integration or product page.
  • Slow: Use the Nexio API integration as highlighted in the Recipe: Creating a product page that shows local currency and prices. This recipe shows how to create a webpage that requests a filterable list of products, get the current currency rates, and change the product prices (and currency symbol) based on the selection of a country.

For a general overview of the Convert product, see Convert (Convert) in the Getting Started section.

Best practices for multi-currency pricing (MCP)

The following are the best practices for presenting your website to your customers in their local currencies:

  • Set all of your base pricing for products on your website in the currency for the bank account where funds are deposited. This is known as the settlement currency of the merchant account.
  • The website should have one of the following:
    • A drop-down option for the customer to select their country or region, then display prices in local currency (if available).
    • Identify the country of the end-user using browser geo-location (not just IP only), and display in local currency (if available).
    • A combination of these two approaches where the website identifies the location automatically but you still provide an option for the customer to select their country or region.
  • For displaying different translations and local currency (if available), it can speed up your integration to use separate paths or files of product pages for each region or country (for example, a path of "en-us" or "fr-ca").
  • If the local and base currencies are different, use the rate lookup API to get the current conversion rate, and re-price the website accordingly.
  • Use something like the following list of currency mappings based on country, including currency symbol, ISO code, region, and how many decimal places are supported:

Next steps

When you are ready to implement this feature, do the following: