How to Prevent Unexpected FX Charges

How Merchants Can Reduce Unexpected FX Charges for International Customers

A customer sees €100. The statement shows €103. Who charged the extra €3?

A customer completes an international purchase.

Checkout says:

€100

The merchant's payment record says:

€100

The customer's statement later shows:

€100 + €3 foreign transaction fee

The customer says:

“You charged me more than the checkout price.”

The merchant says:

“We charged exactly €100.”

Both can be correct.

That is the central difficulty with unexpected FX charges.

The final economic result can involve several participants:

•merchant;

•payment provider;

•acquirer;

•DCC provider;

•card network;

•card issuer or bank.

Not every participant controls the same currency layer.

Not every extra amount is an exchange-rate markup.

And not every fee can be eliminated by the merchant.

So the merchant's job is not to promise:

“No FX fees.”

It is to make sure the customer knows what the merchant will charge, to eliminate unnecessary conversion where possible, and to know exactly where to look when the statement still differs.

“Unexpected FX charge” is not one charge

Customers can describe several different experiences as an “FX fee.”

They are not equivalent.

FX spread

A currency converter uses an exchange rate that differs from a reference or wholesale rate.

The economic cost is embedded in the rate.

Explicit conversion fee

A separate charge is attached to the conversion service.

Foreign transaction fee

The customer's issuer may assess a fee because of the international or foreign nature of the transaction.

This can be separate from currency conversion itself.

DCC markup

A Dynamic Currency Conversion service may incorporate a markup or other disclosed charges into the conversion from the merchant/local currency to the cardholder's billing currency. Visa currently requires DCC displays to show the exchange rate and additional fees or markup, and requires the customer to be able to accept or decline the conversion.

Currency mismatch

The merchant advertises or displays one currency but submits another transaction currency.

That may not create a separate “fee,” but it can create an unexpected conversion.

Double conversion

One participant performs a conversion and another participant subsequently converts again.

Mastercard's current DCC guidance describes double-conversion loss as a possible result when the cardholder's billing currency is misidentified.

Before solving an FX complaint, identify which of these actually occurred.

Start with a currency-control map

For every card transaction that produces an FX complaint, map these layers.

Layer

Question

Advertised currency

What currency did the customer first see?

Checkout currency

What currency appeared immediately before purchase?

Transaction currency

What currency was actually submitted for payment?

DCC currency

Was the customer offered a conversion into a cardholder billing currency?

Card/account currency

What currency is the customer's card or account denominated in?

Issuer conversion

Did the issuer convert the transaction?

Foreign transaction fee

Did the issuer separately assess a fee?

Settlement currency

In what currency did the merchant/provider receive the proceeds?

Payout currency

In what currency did the merchant ultimately receive funds?

The key diagnostic question is:

Where did the amount change, and who controlled that change?

The brief makes that participant-level tracing the article's primary practical framework.

Merchant-controlled conversion

The easiest FX surprise to prevent is usually one created inside the merchant's own pricing or payment flow.

Suppose the merchant keeps a USD base price but wants to sell in EUR.

The merchant or its provider could calculate:

USD base price

→ FX conversion

→ EUR transaction price

At that point the merchant needs to know:

•which rate source is used;

•when the rate is calculated;

•whether a spread or buffer is added;

•whether the rate is locked;

•whether the resulting EUR amount is only indicative;

•whether the payment is actually submitted in EUR.

If the merchant presents:

€100

but submits:

USD 108

then €100 was not the final transaction amount.

That does not automatically make the implementation wrong.

It does make disclosure important.

The merchant should distinguish:

approximately €100

from:

you will be charged €100.

Consistency matters more than simply showing a familiar currency

One of the strongest ideas in the original version should remain:

Do not create a local-currency promise on the product page and break it during payment.

A journey such as:

Product page: €100

Cart: €100

Checkout: €100

Payment submission: USD 108

creates a new question exactly when the customer expects the amount to become final.

The safer experience is to make the final transaction amount and currency explicit before authorization.

If a local amount is only an estimate, say so.

If the local amount is the actual transaction amount, preserve it through checkout unless the customer knowingly selects something different.

Issuer-controlled conversion is a different layer

Now consider a merchant that genuinely submits:

EUR 100

The customer's card account is denominated in USD.

The issuer or applicable card-processing chain may convert EUR into USD for billing.

That conversion is downstream from the merchant transaction.

The merchant may know that a conversion is likely.

It generally cannot promise the exact account-currency amount unless the payment product specifically supplies and guarantees that amount.

Mastercard's current materials make the distinction explicit: without DCC, a transaction in the merchant's local currency is converted using the card issuer's applicable exchange rate; with DCC, the conversion into billing currency uses the rate offered through the acquirer/DCC service.

That is why support teams need both:

transaction currency

and:

customer account currency

before diagnosing an FX complaint.

FX spread and foreign transaction fee are not the same thing

This distinction is critical.

An issuer can convert a foreign-currency transaction.

It can also assess a separate foreign transaction fee.

Those are different economic events.

For U.S. credit cards, CFPB Regulation Z interpretations expressly recognize foreign-transaction fees associated with purchases made in a foreign currency, outside the United States, or with a foreign merchant. The guidance even gives an example in which a consumer buys from a foreign merchant in U.S. dollars and the issuer still assesses a foreign-transaction fee.

That invalidates a common merchant promise:

“We charged you in your own currency, so your bank cannot add a foreign transaction fee.”

The merchant may have eliminated one conversion.

It has not necessarily made the transaction domestic from the issuer's perspective.

Local currency does not mean domestic transaction

These concepts are easy to collapse:

customer's familiar currency

card account currency

transaction currency

merchant location

acquiring location

domestic transaction

They are not synonyms.

A U.S. customer buying from an international merchant could conceivably be charged USD and still be dealing with a foreign merchant transaction for issuer-fee purposes. U.S. Regulation Z specifically contemplates that case.

So local-currency pricing can improve comprehension.

It can reduce some forms of conversion ambiguity.

It cannot universally guarantee:

•domestic processing;

•zero issuer fees;

•zero cross-border fees;

•zero FX activity elsewhere in the chain.

Dynamic Currency Conversion is another conversion path

DCC needs its own diagnosis.

Mastercard's current 2025 merchant guide describes DCC as a service through which an acquirer and its merchant or service provider can let the cardholder choose between the merchant/local transaction currency and the cardholder's billing currency. If the customer chooses local currency, issuer conversion applies; if the customer chooses billing currency through DCC, the conversion uses the rate offered through the acquirer.

Visa likewise says a DCC offer should display:

•the amount in local currency;

•the amount in the cardholder's currency;

•the exchange rate;

•additional fees or markup.

Visa also says customers must be able to accept or decline the conversion and the merchant or ATM must not make that choice for them.

The important merchant lesson is therefore not:

“DCC is always bad.”

It is:

DCC must be recognizable as a conversion offer whose economics and controlling party are visible before consent.

Do not make DCC the default

The original version was right to object to pre-selected or poorly disclosed DCC, and current card-network guidance supports making this stricter.

Mastercard's current DCC guide says no particular conversion method should be implemented as the default, the cardholder must not be required or encouraged to use DCC, the offer must be clear and neutral, and the customer's choice must be honored.

Visa similarly requires genuine accept/decline choice and says merchants should not use presentation techniques designed to influence which currency the customer chooses.

So avoid:

•pre-selecting DCC;

•making one currency visually dominant;

•calling one choice “recommended” without a defensible basis;

•hiding markup;

•presenting DCC as mandatory;

•applying it after the customer selected the other currency.

The merchant objective is informed choice, not steering.

In the EU, DCC transparency has a specific regulatory layer

Within the applicable scope of EU cross-border-payment rules, Regulation (EU) 2021/1230 requires currency-conversion charges for card-based transactions to be expressed as a percentage markup over the latest available ECB euro reference rate and disclosed before the payment is initiated.

It also requires a currency-conversion provider at the point of sale to show the amount in the payee's currency, the amount in the payer's account currency, and the possibility of paying in the payee's currency instead.

That is a useful regulatory example of the underlying principle:

the customer should be able to identify what is being converted and what the conversion costs before committing.

It should not be generalized outside the regulation's scope.

What is double conversion?

Double conversion means the payment value is converted more than once across the transaction path.

There is no value in using the phrase vaguely.

Map both conversions.

For example:

Merchant/local transaction currency: EUR

↓

A DCC service incorrectly identifies the customer's billing currency and converts:

EUR → USD

↓

The customer's actual account is in GBP, so another conversion occurs:

USD → GBP

Mastercard's 2025 DCC guide identifies inaccurate billing-currency identification as one possible cause of this type of double conversion.

The fix is not:

“Use a better exchange rate.”

The fix is:

prevent the unnecessary first conversion or correct the currency identification.

Another apparent “double conversion” can start in merchant pricing

A different two-stage path can look like:

merchant base price in USD

→ merchant converts to EUR transaction price

→ customer's account is denominated in GBP

→ issuer converts EUR to GBP.

Whether this should be described operationally as “double conversion” depends on the exact payment architecture: the first change may be merchant pricing rather than a payment-network conversion.

That distinction matters.

Support should not call every journey involving two currencies “double FX.”

Record what actually happened at each layer.

The FX Surprise Diagnostic

For every customer complaint, work through the questions in order.

•What currency was advertised?

Record the product-page or quoted price.

Example:

€100

•What currency appeared immediately before payment?

If this differs from the advertised price, the surprise may already have originated in checkout.

•What was the actual transaction currency?

This is one of the most important fields in the investigation.

Do not rely on screenshots of the storefront alone.

•Was DCC used?

If yes, record:

•original/local amount;

•DCC amount;

•currencies;

•rate;

•markup/fees;

•customer selection.

•What is the customer's account currency?

Do not infer it only from:

•IP address;

•country;

•billing address;

•browser language.

Ask or use authoritative transaction/card data where lawfully available.

•Did an issuer conversion occur?

Compare:

transaction currency

with:

account/statement currency.

•Was there a separate foreign transaction fee?

Do not classify that fee as an FX spread unless the issuer actually describes it that way.

•Did merchant-side settlement involve another conversion?

This may change merchant economics.

It usually does not explain why the customer statement changed unless that conversion somehow affected the transaction amount.

•Which amount changed?

Was the complaint about:

•original checkout amount;

•DCC amount;

•statement amount;

•separate statement fee;

•refund amount;

•subscription renewal?

•Who controlled that change?

Classify it as:

merchant-controlled

provider/acquirer-controlled

DCC-controlled

network/issuer-controlled

unknown—escalate

Only then decide what the merchant could have prevented.

FX Surprise Diagnostic table

Complaint

First evidence to inspect

Likely controlling layer

Merchant action

“Checkout showed one currency, card was charged another”

Order + transaction currency

Merchant/provider

Fix or disclose mismatch

“I paid in my currency but got an extra bank fee”

Statement fee + issuer terms

Issuer

Do not promise absence; disclose possibility

“The conversion rate was unexpected”

DCC flag / issuer conversion

DCC provider or issuer

Identify conversion party

“I never chose this conversion”

DCC consent evidence

Acquirer/DCC/merchant

Escalate improper DCC

“My payment converted twice”

Currency path

Multiple participants

Identify both conversions

“My refund is lower than expected”

Original + refund transaction currencies

Provider/network/issuer

Trace refund currency and rate

“My subscription costs more this month”

Recurring transaction + account conversion

Merchant price or issuer FX

Identify whether merchant price or FX changed

What merchants can actually prevent

The original version's practical section is worth retaining, with tighter boundaries.

•Keep advertised and transaction currency consistent

If the customer sees:

€100

and the merchant intends to submit:

EUR 100

preserve that through the checkout.

If a currency change is necessary, show the new currency and amount before authorization.

Do not bury the actual transaction currency in terms and conditions.

•Clearly distinguish an estimate from a charge

If a merchant shows:

Approximately £82

but will transact in EUR, label that £82 amount as indicative.

Do not imply it is a fixed merchant charge.

Conversely, if the transaction really will be:

GBP 82

say so clearly.

•If the merchant controls conversion, document the rate policy

Internally preserve:

•source currency;

•target currency;

•rate source;

•timestamp;

•spread or buffer;

•rounding;

•amount before conversion;

•final transaction amount.

This makes support and reconciliation possible later.

Without that record, the merchant may be unable to explain its own conversion.

•If DCC is offered, make it genuinely optional

Show the relevant currencies, amounts, exchange rate and markup/fee.

Give the customer an equal, neutral choice.

Do not preselect the conversion.

Those principles align with current Visa and Mastercard DCC requirements.

•Warn carefully about issuer-controlled charges

The original version suggested language such as:

“Your bank may apply an additional foreign transaction fee.”

That can be useful when appropriate, but the wording should not imply that a fee definitely applies.

A more defensible message is:

“Your card issuer or bank may apply its own currency-conversion or international-transaction charges depending on your account and the transaction.”

For U.S. credit cards, current CFPB rules demonstrate why that qualification matters: an issuer fee can be triggered by the foreign nature of the transaction even when the purchase is denominated in U.S. dollars.

•Do not promise that local currency eliminates bank fees

Local currency can remove the need for issuer currency conversion when the transaction currency matches the account currency.

But it does not universally make an international transaction domestic.

Therefore avoid:

“Pay in your currency to avoid all foreign transaction fees.”

Unless the merchant can prove that statement for the defined payment product and customer population, it creates false certainty.

•Preserve currency evidence for support

Store enough information to reconstruct:

order currency

→ transaction currency

→ DCC status

→ provider transaction ID

→ settlement currency

→ refund currency

Where permitted and available, also preserve the relevant card-country/account-currency indicators needed for diagnosis without storing prohibited sensitive card data.

Refunds require special care

The original article proposed refunding at the original effective rate where supported.

That advice needs to be narrowed.

For DCC transactions

Mastercard's current DCC standards are specific. They say refunds should be handled through a reversal, a credit matching the original DCC currency and amount, or a DCC credit using the exact exchange rate from the original transaction. Mastercard explicitly frames this as preventing a second currency-conversion loss.

That is a network-specific DCC rule, not a universal refund formula.

For other foreign-currency transactions

The merchant should normally preserve the original transaction currency according to its provider/network rules.

But if the customer's issuer converted that currency into an account currency, the value the customer sees after a later refund can depend on the applicable payment-system and FX mechanics at the time.

The merchant should not automatically promise:

“You will receive exactly the same home-currency amount shown on your original statement.”

The dedicated Refunds and Currency Conversion article should own those mechanics.

Subscription FX surprises are different again

Suppose a merchant bills:

USD 20 every month.

The merchant price never changes.

The customer's account is in another currency.

The customer's statement value can therefore move as the issuer-side exchange rate changes.

The merchant did not change the subscription price.

The customer's economic debit still changed.

That is a different problem from a merchant maintaining a fixed:

€18.99/month

local subscription price.

In the first model, the customer bears more visible account-currency fluctuation.

In the second, the merchant may assume more pricing/FX exposure depending on its settlement and cost structure.

This article should flag the distinction, while Subscription Billing in Multiple Currencies owns the full strategy.

Do not confuse merchant settlement conversion with customer FX

Suppose the customer pays:

EUR 100.

The merchant later receives a USD payout.

There may be a merchant-side conversion between transaction settlement and payout.

That can affect:

•merchant proceeds;

•treasury;

•FX costs;

•accounting.

But it does not automatically mean the customer was charged in USD.

This is why:

customer transaction currency

and:

merchant settlement/payout currency

must be kept separate.

The cluster's dedicated Presentment Currency vs Settlement Currency article should own the deeper architecture.

Customer support needs a diagnostic script, not a generic apology

A support agent receiving:

“Why did you charge me an FX fee?”

should not immediately answer:

“That was your bank.”

It may not have been.

Nor should support automatically issue a refund before understanding the transaction.

A better workflow is:

•Confirm merchant order amount and currency.

•Confirm actual payment transaction amount and currency.

•Check whether DCC occurred.

•Ask the customer to distinguish the transaction line from any separate fee line.

•Determine the account/statement currency where necessary.

•Identify whether the amount difference came from merchant/provider conversion, DCC, issuer conversion, or a separate issuer fee.

•Escalate only the layer the merchant/provider controls.

This protects the customer while avoiding false explanations.

Example: merchant is responsible

Checkout displays:

€100

Payment is actually submitted:

USD 110

There was no clear disclosure of the switch.

The customer subsequently sees a USD-to-EUR conversion.

The first problem originated in the merchant/payment flow.

Merchant response:

Fix the checkout mismatch and investigate affected orders.

Example: issuer is responsible for the extra fee

Checkout:

EUR 100

Transaction:

EUR 100

Card account:

EUR

Statement:

EUR 100 + separate foreign transaction fee

If the issuer's product permits that fee for the particular international transaction, merchant FX conversion is not the cause.

The merchant can explain:

“Our transaction was EUR 100. The additional amount appears as a separate issuer charge.”

The merchant should not claim the bank acted incorrectly without evidence.

U.S. rules specifically recognize foreign-transaction fees involving foreign merchants even when a transaction is denominated in dollars, illustrating why denomination alone is not decisive.

Example: DCC is responsible for the conversion

Merchant/local amount:

EUR 100

DCC offer:

USD 118

Customer selects USD after seeing:

•EUR amount;

•USD amount;

•exchange rate;

•markup.

The transaction is then submitted in the selected DCC currency.

That is a DCC conversion rather than issuer conversion.

The merchant should be able to identify it from the transaction/provider data and the customer's recorded choice.

Current Mastercard rules require the transaction to preserve the DCC conversion data needed to identify the original and converted amounts.

Example: double conversion

Merchant:

EUR 100

DCC incorrectly converts:

EUR → USD

Actual card billing currency:

GBP

Issuer then converts:

USD → GBP

There are two conversions.

The diagnosis is not:

“FX rates changed.”

It is:

“The first conversion targeted the wrong billing currency.”

Mastercard explicitly identifies inaccurate billing-currency identification as a cause of this DCC failure mode.

What merchants should measure

The brief appropriately makes operational complaints part of the measurement framework rather than claiming an unsupported universal dispute rate.

FX-related support-ticket rate

FX/currency-related support contacts

÷ relevant completed international orders

Track reason codes separately.

Suggested reasons:

•statement amount differs;

•issuer fee;

•DCC complaint;

•wrong currency;

•refund difference;

•subscription amount;

•unexplained conversion.

Currency mismatch rate

transactions submitted in a different currency from the explicitly confirmed checkout currency

÷ relevant transactions

Ideally this should approach zero unless the switch is intentional and disclosed.

DCC complaint rate

DCC-related complaints

÷ DCC transactions

Separate:

•did not consent;

•rate/markup concern;

•wrong billing currency;

•refund problem;

•other.

Customer currency-switch rate

Track how often customers override an automatically selected currency.

This can expose poor defaulting logic.

Double-conversion incidents

Count only cases where two actual conversion events can be traced.

Do not infer from the mere presence of three currency codes.

Dispute/chargeback rate related to currency

Use actual reason/evidence categories rather than assuming every unfamiliar statement amount became a chargeback.

Mastercard's current DCC guidance does identify a chargeback right in a specific DCC refund scenario where incorrect currency processing causes conversion loss, showing why DCC-related dispute exposure deserves monitoring.

The FX Surprise Diagnostic as an operational control

The ideal outcome is not:

zero currency conversion.

It is:

zero unexplained currency conversion.

A healthy transaction should let the merchant reconstruct:

what the customer saw

→ what the customer agreed to

→ what currency was submitted

→ whether DCC occurred

→ whether the issuer converted

→ whether the issuer added another fee

→ what the merchant settled

→ what happened if the transaction was refunded

When that chain is reconstructable, support can explain what happened.

When it is not, the merchant has a data problem as well as a customer-experience problem.

Final recommendation

The first version of this article began with the right instinct:

A customer who sees a different economic result on their statement may associate the surprise with the purchase—even when the merchant itself did not create the extra amount.

The solution is not to promise that international commerce can be made free of FX.

And it is not simply:

“Charge everybody in local currency.”

That may solve one conversion while leaving a separate issuer fee untouched. U.S. consumer-credit rules explicitly demonstrate that a foreign-transaction fee can arise from the international nature of a transaction even when no foreign currency appears at checkout.

The merchant should instead know:

What currency did we advertise?

What currency did we submit?

Did we perform a conversion?

Was DCC offered?

Which currency did the customer choose?

Did the issuer convert again?

Was there a separate foreign-transaction fee?

What happened when we refunded the transaction?

Then separate the result into two categories.

Merchant-controllable surprise

Fix it.

Examples:

•undisclosed checkout currency switch;

•unclear merchant FX conversion;

•automatic DCC;

•incorrect DCC currency;

•missing DCC markup disclosure;

•wrong refund currency.

Issuer- or account-controlled cost

Explain it accurately.

Do not promise it away.

That is how merchants reduce unexpected FX charges without claiming control over parts of the payment system they do not own.

The standard is not “no FX.”

The standard is “no unexplained FX.”

Troubleshooting FAQ

I charged the customer in their local currency. Why did they still receive a foreign transaction fee?

Because transaction currency and issuer fee policy are different things. Depending on the card product and transaction, an issuer may treat an international or foreign-merchant transaction as subject to a foreign-transaction fee even when the currency matches the customer's account currency. U.S. Regulation Z expressly recognizes this possibility.

Is an FX spread the same as a foreign transaction fee?

No. An FX spread is embedded in a conversion rate. A foreign transaction fee can be a separate issuer charge.

Is DCC the same as issuer currency conversion?

No. With DCC, an acquirer/DCC arrangement converts the transaction into the customer's billing currency after the customer chooses that option. If the customer instead pays in the local transaction currency, an issuer may perform the later conversion.

Can merchants automatically choose DCC for customers?

Current Visa and Mastercard guidance requires customer choice rather than automatic merchant selection.

How can a merchant diagnose double conversion?

Trace the original transaction currency, any DCC or merchant conversion, the customer's actual billing currency, and the issuer conversion. Mastercard documents incorrect DCC billing-currency identification as one possible cause.

Should a refund always use the original exchange rate?

Do not generalize that rule. Mastercard has specific DCC refund requirements that preserve the original DCC currency/amount or rate in defined ways; other transaction types should follow the applicable provider/network refund mechanics.

Can a merchant guarantee that the statement amount will equal the checkout amount?

The merchant can guarantee only the amount and currency it controls. If an issuer conversion or issuer fee applies afterward, the account result may differ.

The first version improves this article substantially because it already had the right operational instinct: the goal is not to eliminate every FX cost; it is to stop customers from discovering a currency cost they did not understand after committing to the purchase. I’ve kept that framing, but made participant control the organizing principle, as the new brief requires.

The main improvement from the first version is that the article can now tell a merchant what it can fix, what it can only disclose, and what evidence support needs before blaming either the bank or the payment flow. That is much stronger than positioning local-currency pricing as a universal cure for FX surprises.

Editorial package

Concise interpretation of the brief

Customer problem:

The customer sees one price during purchase but later sees a different amount, conversion, or fee on the card or bank statement and cannot tell why.

Unique evidence anchor:

The merchant can control some currency costs and disclosures, but not every fee that ultimately appears on a customer's statement.

Unique thesis:

Preventing FX surprises requires a currency-control map, not a promise of “no FX fees.”

Editorial position:

Merchants should eliminate avoidable currency ambiguity, make the transaction currency explicit, disclose merchant- or DCC-controlled conversion clearly, and avoid promising that issuer-controlled charges will disappear simply because checkout uses a familiar currency.

Common assumption challenged:

“If we charge the customer in local currency, the customer cannot receive a foreign transaction fee.”

Merchant decision:

Determine which participant controls each conversion or fee, remove the surprises the merchant can control, disclose those it cannot, and make support teams capable of tracing the rest.

Selected format:

FX surprise diagnostic.

Structural rationale:

Open with a transaction in which the merchant and customer can both truthfully report different outcomes, then trace every possible currency layer until the party controlling the unexpected amount becomes identifiable.

Proposed architecture

•Customer and merchant can both be right

•“FX charge” is not one thing

•Build the currency-control map

•Merchant-controlled conversion

•Issuer/network-controlled conversion

•Foreign transaction fees

•DCC

•Double conversion

•FX Surprise Diagnostic

•What merchants can actually prevent

•Subscription and refund edge cases

•Customer-support diagnostic

•Measurement

Final recommendation

SEO metadata

How to Prevent Unexpected FX Charges for Customers

H1:

How Merchants Can Reduce Unexpected FX Charges for International Customers

Meta description:

Learn where unexpected FX charges come from, how DCC, issuer conversion and foreign transaction fees differ, and what merchants can control, disclose and diagnose.

URL slug:

/how-to-prevent-unexpected-fx-charges

how to prevent unexpected FX charges

Secondary keywords:

unexpected foreign exchange fees; foreign transaction fees ecommerce; FX charges online payment; avoid currency conversion fees; ecommerce foreign currency fee; DCC foreign exchange charges; card foreign transaction fee; cross border payment FX fees

Related entities:

foreign exchange; FX; foreign transaction fee; Dynamic Currency Conversion; DCC; transaction currency; billing currency; issuer; acquirer; currency conversion; double conversion; settlement currency

Article excerpt:

A merchant can charge exactly the checkout amount while a customer still sees an extra foreign-transaction fee or conversion on their statement. This guide shows merchants how to identify who controls each FX layer, prevent avoidable currency surprises, and explain the charges they cannot control.

Suggested structured data:

Article plus FAQPage if the troubleshooting FAQ remains visible.

Internal-link plan

The brief prioritizes three cluster links.

Dynamic Currency Conversion Explained

Anchor: how Dynamic Currency Conversion works

Presentment Currency vs Settlement Currency

Anchor: the difference between customer transaction and merchant settlement currency

Why Customers Prefer Local Currency

Anchor: why price certainty matters to international customers

Useful secondary links:

Multi-Currency Pricing Explained

For merchant-controlled currency conversion and local transaction pricing.

Subscription Billing in Multiple Currencies

For renewal FX behavior.

Refunds and Currency Conversion

For the complete post-purchase FX lifecycle.

Authoritative source recommendations

Visa — DCC guidance

Use for current cardholder DCC disclosure and choice requirements. Visa says DCC offers should show both relevant amounts, currency symbols, exchange rate, and additional fee/markup and should allow the customer to accept or decline without merchant selection.

Mastercard — 2025 DCC Performance Guide

Use for:

•issuer conversion versus acquirer/DCC conversion;

•neutral customer choice;

•DCC transaction data;

•double-conversion examples;

•billing-currency identification;

•DCC refund handling.

The 2025 guide explicitly distinguishes issuer conversion when local currency is chosen from acquirer-provided conversion when DCC is chosen.

CFPB / Regulation Z

Use as a U.S.-specific authoritative example showing that foreign-transaction fees are not synonymous with currency conversion and may include transactions involving foreign merchants even in USD.

EUR-Lex

Use the currently codified Regulation (EU) 2021/1230—not the superseded 2019 amending regulation—as the current EU source for relevant currency-conversion transparency requirements.

Supporting visual

FX Surprise Diagnostic

START: customer says “I was charged more”

↓

•Advertised amount

Currency: ___

Amount: ___

↓

•Checkout confirmation

Currency: ___

Amount: ___

↓

•Actual payment transaction

Currency: ___

Amount: ___

Different from checkout?

Yes → merchant/provider currency mismatch investigation

No ↓

•DCC used?

Yes → record local amount + DCC amount + rate + markup + customer consent

No ↓

•Does transaction currency match customer account currency?

No → issuer/network conversion may occur

Yes ↓

•Separate foreign-transaction fee?

Yes → issuer/account fee investigation

No ↓

•Was there another conversion?

Yes → map both conversions → double-conversion investigation

Final classification

Merchant controlled

DCC/acquirer controlled

Issuer controlled

Multiple parties

Unknown — escalate

Visual callout

Do not ask “Was there an FX fee?”

Ask “Where did the amount change?”

Image alt text

FX Surprise Diagnostic tracing advertised currency, checkout currency, transaction currency, DCC, customer account currency, issuer conversion, foreign transaction fees and double conversion to identify which party controlled an unexpected charge.

Proposed author and reviewer model

Author:

Payments operations specialist:

[Named reviewer]

Card/payments expert:

[Named reviewer]

Customer support lead:

[Named reviewer]

Treasury reviewer:

[Named reviewer]

Compliance/legal reviewer:

[Named reviewer for jurisdictional claims]

Last reviewed:

[Publication date]

Recommended first-hand contribution

The strongest addition would be one approved, anonymized case such as:

•customer charged exactly the merchant amount but received an issuer fee;

•DCC applied in the wrong billing currency;

•checkout currency differed from transaction currency;

•double conversion caused a support escalation;

•refund currency created a dispute;

•support diagnostics identified which participant controlled the amount.

Do not invent the case.

Currency-support fact-check items

Verify:

•advertised currencies;

•transaction currencies;

•card-processing currencies;

•local payment-method currency support;

•payment-method fallback behavior;

•card/account currency fields available;

•merchant project configuration;

•refund currency support;

•recurring currency support.

FX fact-check items

For every stated FX cost verify:

•source currency;

•destination currency;

•conversion party;

•reference rate;

•applied rate;

•markup;

•explicit fee;

•rate timestamp;

•authorization/clearing treatment where relevant.

Never use “the exchange rate” without identifying which rate.

DCC fact-check items

Verify:

•DCC provider/acquirer;

•eligible transactions;

•billing-currency identification;

•exchange rate;

•markup;

•additional fees;

•customer consent;

•equal presentation;

•opt-out;

•receipt requirements;

•ecommerce implementation;

•refund handling;

•applicable network rules;

•jurisdictional disclosure requirements.

Country-pricing fact-check items

This article should not become a country-pricing guide.

Where a country example is used, verify:

•relevant consumer-protection rules;

•card-network requirements;

•common currencies;

•local payment-method compatibility;

•DCC regulatory treatment.

Settlement fact-check items

Verify:

•transaction currency;

•settlement currency;

•merchant balance currency;

•payout currency;

•merchant-side FX conversion;

•conversion rate;

•FX charge;

•reporting/reconciliation.

Do not use merchant settlement conversion to explain a customer statement difference unless the transaction itself was affected.

Subscription fact-check items

Verify:

•recurring transaction currency;

•customer account currency;

•whether price is fixed locally;

•whether price is FX-derived;

•renewal conversion;

•change notification;

•stored-payment-method compatibility.

Refund fact-check items

Verify:

•original transaction currency;

•original DCC status;

•refund currency;

•refund amount;

•provider/network rule;

•conversion rate;

•customer statement result;

•merchant settlement adjustment.

Mastercard's DCC-specific rules should not be generalized to all payment methods.

Conversion/incrementality fact-check items

The article does not own the full conversion case, but merchants should track whether the controls reduce:

•FX-related support contacts;

•currency complaints;

•DCC complaints;

•unexplained currency changes;

•currency-related disputes.

Do not claim:

“Reducing FX surprises increases conversion by X%”

without an actual merchant experiment.

Regulatory and consumer-protection fact-check items

Immediately before publication verify:

•current Visa DCC rules;

•current Mastercard DCC rules;

•applicable domestic payment law;

•FX disclosure requirements;

•cardholder-choice requirements;

•pricing disclosure;

•refund rules.

For EU transactions within scope, current Regulation (EU) 2021/1230 contains currency-conversion transparency requirements including markup disclosure against ECB reference rates.

Disclaimer:

This article provides general information and does not constitute legal, regulatory, tax, financial, or accounting advice. Merchants should verify current requirements with qualified advisers, payment providers, acquirers, card networks, banks, and relevant authorities.

Amber-flag claims

“Unexpected FX charges are usually a checkout design problem.”

Too strong.

Some are merchant-created; others are issuer-, network-, account-, DCC-, or provider-controlled.

“Local-currency pricing removes FX charges.”

Incorrect as a universal statement.

“If customers pay in their currency, their bank cannot charge a foreign transaction fee.”

Incorrect. U.S. Regulation Z expressly contemplates foreign-transaction fees on purchases involving foreign merchants even when the transaction is denominated in USD.

“DCC always gives a worse rate.”

Do not publish as a universal rule.

Discuss the specific DCC rate, markup and alternative rather than presuming the comparison.

“DCC should always be declined.”

Too categorical for a merchant guide.

The correct merchant responsibility is transparent, neutral choice.

“Merchant's presentment currency determines the final statement amount.”

Not necessarily.

Account conversion and issuer fees can intervene.

“Foreign transaction fee = FX spread.”

Incorrect.

“Settlement currency determines what the customer pays.”

Incorrect.

“Refund at the original exchange rate.”

Only make this claim where the applicable provider/network rules establish that treatment. Mastercard does so for certain DCC refund paths.

“FX confusion causes frequent chargebacks.”

Requires merchant or industry evidence with defined reason codes.

Do not infer prevalence.

The first version's final paragraph should not be published as written without internal verification.

•Smart Checkout is publicly described as showing relevant payment options with localized prices and local language.

Before making a product-specific FX claim, verify internally:

•Current supported transaction currencies.

•Currency support by payment method.

•Merchant-controlled conversion capabilities.

•Rate source.

•FX markup/spread.

•Rate-lock behavior.

•Smart Checkout currency behavior.

•Localized-price behavior.

•DCC support, if any.

•DCC provider/network.

•Customer consent behavior.

•Cardholder billing-currency identification.

•Foreign-transaction-fee messaging.

•Settlement currencies.

•Payout currencies.

•Transaction-to-settlement conversion.

•Merchant FX fees.

•Refund currencies.

•DCC refund handling.

•Subscription currency handling.

•Reporting fields needed for the FX Surprise Diagnostic.

•FX-support reason codes.

•Current approved market/payment-method counts.

Moment Treasury

Do not publish that paragraph until an internal product owner confirms:

•current product name;

•availability;

•FX functionality;

•treasury functionality;

•merchant eligibility;

•supported currencies;

•settlement capabilities.

Until the internal FX configuration is confirmed, a publishable version could read:

Suggested CTA

Provider/network verification questions

•What amount and currency does the customer first see?

•What amount and currency are submitted?

•Does the provider perform conversion?

•What rate source is used?

•What spread or markup applies?

•When is the rate fixed?

•Is DCC supported?

•Who provides DCC?

•How is billing currency identified?

•What DCC disclosures appear?

•Is DCC ever preselected?

•How is consent stored?

•Can issuer conversion still occur?

•Can a foreign-transaction fee still apply?

•Which transaction fields identify cross-border status?

•What data can support use to diagnose the customer's statement?

•Can double conversion occur?

•What controls prevent it?

•How are DCC refunds processed?

•How are ordinary foreign-currency refunds processed?

•How are recurring transactions handled?

•What settlement conversion occurs?

•Which FX amounts appear in reporting?

•Which party handles customer complaints about conversion?

Cluster sameness-audit fields

Field

This article

Title

How Merchants Can Reduce Unexpected FX Charges for International Customers

Opening device

€100 checkout versus €100 + issuer fee

Customer currency problem

Customer cannot explain why statement differs from checkout

Main currency layer

Participant control across transaction and account

Primary geography

Global with U.S./EU network examples

Primary format

FX surprise diagnostic

Unique evidence anchor

Merchant controls some costs/disclosures, not every statement charge

Editorial position

Remove controllable ambiguity; disclose uncontrollable uncertainty

Assumption challenged

Local-currency charge guarantees no foreign fee

Merchant decision

Identify and control each FX layer

Original framework

FX Surprise Diagnostic

Primary metric

FX-related support rate

Secondary metrics

Currency mismatch, DCC complaints, double-conversion incidents

Central distinction

Merchant control versus issuer control

Secondary distinction

FX spread versus foreign transaction fee

Conclusion

Prevent unexplained FX, not all FX

CTA

Build traceable currency/payment configuration

Closing element

Troubleshooting FAQ

Original-version inclusion and correction audit

Retained

Customer sees a different statement result and blames the merchant.

Retained as the opening scenario, but presented as a possible customer experience rather than universal behavior.

“This isn't about eliminating FX costs.”

Retained as the article's philosophical center.

DCC as a major potential source of surprise.

Retained and strengthened with current Visa/Mastercard requirements.

Presentment/transaction mismatch.

Retained.

Issuer foreign-transaction fees.

Retained and made much more technically precise using CFPB guidance.

Subscriptions.

Retained as a boundary case.

Refund FX.

Retained, but narrowed by transaction type.

Keep checkout and charge currency consistent.

Retained.

Warn customers about possible issuer fees.

Retained with more careful wording.

Corrected

“Unexpected FX surprises are mostly checkout problems.”

Removed. Control can sit with merchant, DCC provider, network or issuer.

“DCC usually uses a worse rate.”

Removed from the core article. The merchant article should expose the actual markup and comparison rather than assert a universal outcome.

“Local currency removes customer-side conversion ambiguity.”

Qualified. It can remove currency conversion but may not remove international-transaction fees.

“Refund at the original effective rate.”

Restricted to applicable product/network behavior. Mastercard has explicit DCC refund rules, but the instruction is not universal.

“Unexpected FX charges frequently become chargebacks.”

Removed as an unsupported prevalence claim. Specific DCC conversion-loss scenarios can carry dispute rights, but prevalence requires data.

Removed pending current internal verification and alignment with current canonical company figures.

Moment Treasury claim.

Held for internal product verification.

Publication note — August 2026

The intellectual center should remain the brief's control problem:

The merchant can control some currency costs and disclosures, but not every fee that appears on the customer's statement.

Current Visa and Mastercard guidance strongly supports the article's neutral-choice treatment of DCC, while current U.S. consumer-credit rules provide an especially useful demonstration that local denomination and absence of issuer fees are not the same thing.

This piece should stay distinct from the cluster's DCC article, currency-layer architecture article, subscription article and refund article. Its job is diagnostic:

Customer says the amount changed.

Find the exact layer where it changed.

Then identify who controlled that layer.

v1

How to Prevent Unexpected FX Charges

A customer who gets charged a different amount than what they saw at checkout doesn't usually blame their bank first — they blame the merchant. Unexpected FX charges are one of the more avoidable sources of chargebacks, support tickets, and lost repeat business, because in most cases the surprise is a checkout design problem, not an unavoidable cost of selling internationally.

This isn't about eliminating FX costs — cross-border commerce almost always involves currency conversion somewhere in the chain. It's about making sure the customer never encounters that conversion as a surprise after they've already committed to a purchase.

Where Unexpected FX Charges Actually Come From

Dynamic Currency Conversion (DCC) offered without clear disclosure. DCC lets a customer pay in their home currency instead of the merchant's presentment currency, but it usually comes with a worse exchange rate than the customer's own card network would apply. When DCC is opted into by default, pre-selected, or presented without a clear comparison to paying in the original currency, customers frequently don't realize they've agreed to a worse rate until the statement arrives.

Presentment currency that doesn't match what the customer expects. If checkout displays a price in the merchant's currency but the customer's card statement shows a different amount after their own bank's conversion, that gap — even if it's just normal cross-border processing — reads as an unexplained charge.

Cross-border fees layered on top of FX conversion. Card issuers often apply a separate cross-border or foreign-transaction fee in addition to the FX spread itself. Customers frequently don't distinguish between the two and attribute both to the merchant.

Subscription and recurring billing in a currency that shifts over time. A subscription charged consistently in one currency can still produce a different amount on the customer's statement from cycle to cycle as exchange rates move, even when the price itself hasn't changed. Without a heads-up, that variability looks like inconsistent billing.

Refunds processed at a different rate than the original charge. A refund converted at the current exchange rate rather than the original transaction's rate can return a different amount than the customer paid — a frequent source of "why didn't I get my full refund back" disputes that have nothing to do with the merchant's actual refund policy.

What Merchants Can Actually Do About It

Price and charge in the customer's local currency wherever possible. The most reliable way to prevent an unexpected FX charge is to remove the conversion step from the customer's side of the transaction entirely — showing a price in their local currency and settling that same amount removes the ambiguity that causes disputes.

If DCC is offered, make it genuinely optional and comparably disclosed. Show both options — pay in the merchant's currency or pay in the customer's currency via DCC — with the effective rate visible for each, rather than defaulting to whichever option is more profitable for the acquirer. A customer who chooses DCC with the trade-off visible has no basis for a surprise later.

Keep presentment currency consistent with what's charged. Avoid situations where the checkout page shows one currency and the actual charge processes in another without an explicit note. If a mismatch is unavoidable for a specific market, disclose it at the point of payment, not just in fine print in the terms.

Warn customers up front that their bank may apply its own fee. Merchants can't control a customer's card-issuing bank, but a simple note — "your bank may apply an additional foreign transaction fee" — shifts responsibility for that specific line item to where it actually belongs, before the customer is surprised by it.

Keep subscription billing currency stable and flag rate-driven changes. If a subscription is billed in a currency that's subject to conversion, consider whether locking the local-currency price (rather than the underlying settlement currency) produces more predictable statements for the customer, and communicate proactively if a renewal amount will differ from the last cycle.

Refund at the original transaction's effective rate where the payment stack supports it. This avoids the awkward experience of a customer receiving back less than they paid due to rate movement between the original charge and the refund.

Why This Is Worth Fixing

Unexpected FX charges show up as chargebacks and "unrecognized transaction" disputes more often than merchants assume, because customers experiencing a confusing charge often dispute first and ask questions later. Each of the fixes above is a checkout and billing configuration decision, not a cost the merchant has to absorb — the goal is making sure any FX-related cost the customer does pay was visible before they paid it, not after.

Local currency pricing and settlement across 190+ markets and 200+ local payment methods is designed to let merchants charge customers in their own currency in the first place, removing the ambiguity that drives most FX-related disputes. For merchants managing multi-currency settlement and treasury operations, Moment Treasury is built to handle the underlying currency management on the back end, so the customer-facing charge can stay simple and predictable regardless of how conversion is handled behind the scenes.