Multi-Currency Checkout: Pricing in Your Shopper's Currency
How multi currency checkout really works: who pays conversion markups, why refunds can cost you, and what Shopify and other platforms support.
Photo: Pixabay
On this page 7 sections
Key takeaways
- If you charge a shopper in their own currency, you take on the conversion markup and the exchange-rate risk on refunds. Without it, the shopper carries both.
- A foreign card is still a cross-border transaction whatever currency you charge in, so changing the currency won't fix international declines on its own.
- On Shopify, only Shopify Payments or Adyen can charge in local currency. Orders through other gateways go through in the store's default currency.
- Before launch, place a test order in each currency and refund it. That shows you the real conversion numbers in your reporting.
A multi currency checkout means a shopper in Toronto or Berlin doesn't have to do exchange-rate math, but the term covers two different setups. In the first, the shopper sees converted prices and the card is still charged in U.S. dollars. In the second, the card is charged in the shopper's own currency and the money is converted to dollars on your side. That moves the conversion cost and the refund risk from the shopper to you.
Which one you can run depends on your platform and processor, not on a theme setting. On Shopify, for example, local-currency charging requires Shopify Payments or Adyen. With any other provider, every customer pays in the store's default currency.
Two Kinds of Multi-Currency Checkout
Display conversion shows an estimated local price. The card is charged in USD, and the shopper's card issuer converts the charge at its own rate. Many cardholder agreements add a foreign transaction fee on top. The number on the shopper's statement rarely matches the number your site showed.
True multi-currency charging authorizes and captures the payment in the shopper's currency, which is called the presentment currency. The charge matches the displayed price. Your processor then converts the funds into your settlement currency before depositing them. For a U.S. business that is almost always USD.
| Display Conversion | True Multi-Currency Charging | |
|---|---|---|
| Currency the card is charged in | USD | Shopper's local currency |
| Who converts | Shopper's card issuer | Your processor or gateway |
| Statement matches displayed price | Rarely | Yes, for the charge amount |
| Who bears the conversion markup | Shopper | You, unless it's built into prices |
| Setup | Theme widget or app | Gateway and processor must support each currency |
| Exchange-rate risk on refunds | Shopper's | Yours |
Display conversion is cheap to add. The catch is the gap between the price shown and the price charged, which brings "you overcharged me" emails and the occasional dispute.
Dynamic currency conversion (DCC) is a separate product, used mostly at in-person terminals. The cardholder chooses at the terminal whether to pay in their home currency. Card network rules govern how that choice is offered and disclosed.
Charging in Euros Doesn't Make the Sale Domestic
This is the rule merchants most often get wrong. Card networks decide whether a transaction is cross-border by geography: the country where the card was issued compared with the country of the merchant and its acquirer. Currency doesn't change that. A U.S. store charging a French card in euros through a U.S. acquirer is processing a cross-border transaction, just as it would in dollars.
That means issuer fraud models still see a foreign merchant, so local pricing alone won't fix international declines. Network cross-border assessments apply in both models, and network fee schedules can treat a USD transaction differently from a foreign-currency one. Before you decide, ask your processor to price the same foreign card both ways.
Other tools do more for approvals. 3-D Secure authentication for card-not-present payments gives the issuer stronger evidence that the real cardholder is buying. Local or cross-border acquiring arrangements, where available and approved through underwriting, change how issuers view the transaction far more than currency does. If good customers abroad are still being turned away, start with why legitimate customers get falsely declined.
Where local pricing helps is trust. An unfamiliar currency makes the final cost unclear, and an unclear total loses carts. If international visitors drop off between cart and payment, test currency alongside local payment methods by country and the other payment fixes that recover abandoned checkouts.
Who Pays the Currency Conversion Cost
Somebody always pays for conversion. Whoever converts, the issuer or your processor, uses a rate less favorable than the mid-market rate, and that spread is its margin. Two other costs sit on top. Network cross-border assessments reach your statement through your processor's pricing. The issuer's foreign transaction fee lands on the cardholder's statement. Some issuers charge that fee only when the transaction is in a foreign currency. Others charge it on any purchase from a foreign merchant, even one billed in the cardholder's home currency.
With display conversion, the shopper absorbs the issuer's rate and fee, and you pay normal processing costs plus any cross-border pass-throughs. With true multi-currency charging, you also pay the processor's conversion markup each time money moves between currencies. The usual answer is to build that markup into your local prices.
Worked example (illustrative numbers, not any provider's actual rates). Assumptions: a U.S. store sells a jacket for $80, lists it at a fixed €75 for euro shoppers, and settles in USD. On the day of the sale, the processor's effective rate after its markup is $1.056 per euro.
- The shopper pays €75, and you receive €75 × 1.056 = $79.20, before normal processing fees.
- That's $0.80 less than your USD price. If the euro strengthens, the same €75 could net you more than $80.
The shopper's price stays fixed, but your dollar proceeds move with the exchange rate.
Refunds Are Where Local-Currency Charging Bites
With true multi-currency charging, you refund in the original presentment currency. To continue the example: three weeks later the shopper returns the jacket. The processor's effective rate for converting dollars back into euros is now $1.08 per euro, so refunding €75 costs you €75 × 1.08 = $81.00. You collected $79.20 and paid out $81.00. That's a $1.80 exchange-rate loss, on top of any processing fees you don't get back. (Our article on whether processing fees come back when you refund covers that second part.) Rates can also move in your favor. Either way, the risk is yours.
With display conversion, you refund $80 in USD and have no currency exposure. The shopper's issuer converts the refund at that day's rate, so they can get back fewer euros than they paid even though you refunded in full. That gap leads to complaints and sometimes a dispute.
Chargebacks work the same way, because disputed amounts are converted at a later date than the sale. Receipts that show the charged currency head off "amount differs" disputes. For the rest, see our guide to winning chargebacks from shoppers abroad.
State in your refund policy which currency refunds are paid in, and consider offering store credit for international returns. Record exchange-rate gains and losses on their own line so they don't confuse deposit reconciliation. Ask your accountant how to book them. This is general information, not tax or accounting advice.
Set Local Prices on Purpose
Automatic conversion produces prices like CA$107.38, which look machine-made and change whenever rates move. A better approach is fixed local prices for your two or three biggest markets (€75, not €74.62) and automatic conversion with rounding rules for each currency in the rest. Fixed prices look native, but you need to review them when rates shift. A small buffer in your local prices can absorb conversion markups and normal rate swings. Size it from your own margins and your provider's actual markup, not a rule of thumb.
Price endings (.99, .95 or whole numbers) vary by market, and shoppers in much of Europe expect displayed prices to include tax. Confirm your tax obligations with a qualified tax professional. Restate a "free shipping over $100" offer as a round local amount. Apparel sellers should say whether duties are collected at checkout or on delivery, because international shoppers compare the landed cost. For the margin math, read how to show local prices without losing margin.
What Shopify, WooCommerce, BigCommerce and Magento Support
Shopify has the strictest limits. Its guidelines for selling in local currencies say only Adyen and Shopify Payments support selling in local currencies. Orders through other third-party providers go through in the store's default currency. Showing local-currency prices and setting manual exchange rates also require Shopify Payments. Shopify warns that some currency apps show a converted price that switches back to the default currency at checkout. Payouts are a separate question. According to Shopify's Multi-Currency Payouts page, stores on the Basic, Grow or Shopify plan can sell in multiple currencies, but their payouts are converted to the domestic currency.
So a Shopify store using a third-party gateway, including a Shopify store integration through MannyPay, charges in its default currency. The most it can offer is app-based display conversion. Whether that trade-off is worth it comes down to cost, and our breakdown of Shopify Payments vs. a third-party gateway walks through the math.
On WooCommerce, multi-currency comes from plugins. The plugin controls what shoppers see, but your gateway decides whether the charge is actually processed in that currency. BigCommerce has built-in multi-currency settings, but charging in a local currency requires a gateway that supports each currency you turn on. Magento (Adobe Commerce) separates a base currency from display currencies, set by store scope. Refunds and reporting follow the currency the order was captured in. Features change, so check the current documentation for your plan and gateway on all three.
Picking Your Model
Let your own order data decide:
- International orders are a small, scattered share of sales. Use display conversion, or none at all, with a clear note at checkout that cards are charged in USD.
- One or two countries bring steady volume, and you have margin to absorb the markup. Charge in local currency, with fixed prices in those markets.
- Your return rate is high. Run the refund numbers from the worked example against your own return rate and build the result into your buffer before you choose local charging.
- You're on Shopify with a third-party gateway. Native local-currency charging isn't available, so this is a choice of processor, not a setting.
Before you turn anything on, get written answers from your provider on four points:
- Which currencies you can present and settle in.
- The conversion markup, and whether statements show it separately.
- Whether the rate locks at authorization, capture or settlement.
- What rate applies to refunds and chargebacks.
Then place a test order in each currency and refund it, so you see the real numbers in your reporting. If you plan to market abroad, warn your processor before a sales spike, because a sudden jump in international volume can trigger a review.
For the processing side, MannyPay's international payment processing covers multi-currency acceptance, cross-border acquiring paths, a review of USD or local-currency settlement, and documentation support. Eligibility depends on underwriting. Send your current statement and the countries your orders come from through a free quote request, and a MannyPay specialist will respond within one business day.
Sources
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
