Dynamic Currency Conversion: How DCC Revenue Share Works, What You Must Disclose, and When It Costs Customer Trust

Dynamic currency conversion lets an eligible international cardholder choose to pay in a familiar cardholder or billing currency instead of the merchant’s local transaction currency. 

The convenience can carry an exchange-rate markup, and part of the economics may be shared among the DCC provider, acquirer, processor, and sometimes the merchant depending on the commercial agreement.

That choice is the defining feature of DCC. Visa requires merchants offering DCC to tell cardholders that the service is optional, avoid defaulting them into DCC, and obtain the cardholder’s express agreement. Mastercard similarly requires a clear, neutral offer and says DCC must not be applied without the cardholder’s consent.

For merchants, dynamic currency conversion can create another source of payment-related revenue while giving international customers immediate visibility into a familiar currency. 

It can also create complaints, disputes, refund problems, checkout abandonment, and lasting distrust when the local-currency option is difficult to find or the conversion margin is not presented clearly.

That makes DCC revenue share only one part of the decision. A successful DCC program also depends on cardholder currency choice, compliant disclosures, neutral checkout design, accurate receipts, properly configured refunds, strong reconciliation, and staff who understand that the customer—not the merchant—chooses the payment currency.

This guide explains how dynamic currency conversion for merchants works, how a foreign exchange markup split may create DCC merchant revenue, what current card-network guidance requires merchants to disclose, and how to decide whether DCC is improving the customer experience or undermining it.

What Is Dynamic Currency Conversion?

Dynamic currency conversion, usually abbreviated DCC, is a payment service that offers an eligible international cardholder the option to complete a cross-border transaction in the cardholder’s billing currency instead of the merchant’s local currency. 

Mastercard describes DCC as a service through which a cardholder can choose between the local transaction currency and the billing currency associated with the card.

Suppose a U.S. traveler purchases merchandise from a retailer in France. Without DCC, the retailer might submit a €100 transaction, after which the card issuer or card-network-related conversion process determines the dollar amount ultimately charged to the customer’s account.

With DCC, the checkout may instead identify the card as eligible and present two choices: pay €100 in the merchant’s local currency or pay a disclosed amount in U.S. dollars using the DCC exchange rate.

A typical point-of-sale currency conversion flow looks like this:

1. The customer presents an eligible card.
2. The terminal or ecommerce payment system determines whether DCC can be offered.
3. The system displays the merchant’s local-currency amount and the cardholder-currency alternative.
4. The applicable DCC exchange rate, markup, fees, and other required information are shown.
5. The customer actively selects a currency.
6. The transaction is submitted in the selected currency.
7. The receipt or confirmation records the relevant DCC information required for that transaction.

DCC eligibility should not be inferred simply from a traveler’s nationality, language, IP address, or physical location. Card eligibility, payment environment, network rules, processor configuration, currency support, card-product restrictions, and regional requirements can all affect whether the service may be offered.

Visa’s consumer guidance emphasizes that customers must be allowed to accept or decline conversion and that merchants or ATMs should not make that decision for them. Visa also says the local and cardholder currency amounts, exchange rate, and additional fees or markup should be displayed.

DCC vs Paying in Local Currency

The fundamental DCC decision is local currency vs home currency. When the customer chooses local currency, the merchant submits the transaction in the merchant’s transaction currency and the cardholder’s issuer generally handles the conversion needed for the cardholder’s account. 

Mastercard’s DCC guidance specifically contrasts DCC conversion by the merchant-side service with local-currency transactions where conversion is handled using the issuer’s exchange rate.

When the customer chooses DCC, the merchant-side DCC service establishes the presented cardholder-currency amount before authorization. That gives the customer greater certainty about the converted purchase amount shown at checkout, but it does not prove that the DCC rate is less expensive than the rate the issuer would otherwise apply.

Factor	DCC/Home-Currency Choice	Local-Currency Payment
Currency shown to cardholder	Merchant amount plus converted billing/home-currency amount	Merchant’s local transaction currency
Who performs conversion	Merchant-side DCC provider/acquirer arrangement	Generally issuer-side conversion after local-currency processing
Exchange-rate visibility	DCC exchange rate is shown before selection	Issuer conversion may not be known at merchant checkout
Possible markup	DCC markup or conversion margin may apply	Issuer/network conversion economics may apply instead
Possible issuer FX fee	May still apply depending on issuer terms	May apply depending on issuer terms
Customer certainty at checkout	Converted transaction amount is presented before payment	Final home-currency charge may depend on issuer processing
Merchant DCC revenue	May exist if contract provides revenue share	No DCC merchant revenue from the transaction

The least expensive choice cannot be determined simply by asking whether DCC is offered. The customer would need to compare the actual DCC rate and markup with the issuer’s conversion terms and any foreign transaction fees associated with the card.

That comparison is especially important because the DCC markup is not the same thing as an issuer foreign transaction fee. DCC determines how the merchant-side conversion is priced. The issuer may separately apply charges under the cardholder agreement.

Merchants should therefore avoid checkout claims such as “pay in dollars to avoid foreign fees” unless the statement can actually be supported for that cardholder. In most merchant environments, the business has no reliable way to know the customer’s issuer pricing.

How DCC Revenue Share Works

DCC revenue share is the commercial arrangement through which some of the conversion economics generated on eligible DCC payments may be retained or distributed among parties supporting the service.

Conceptually:

DCC Conversion Revenue = FX/Conversion Margin Generated on Eligible DCC Transactions

An agreed portion of that economics may then be allocated according to contracts between the DCC provider, acquiring institution, processor, ISO or other payment intermediary, and merchant.

Potential participants can include:

• the DCC technology or currency-conversion provider;
• the acquiring bank;
• the payment processor;
• another contracted payment intermediary;
• the merchant.

There is no responsible universal statement such as “merchants receive X% of every DCC markup.” DCC revenue share depends on the processor or acquirer agreement, supported currencies, transaction environment, provider pricing, merchant size, network arrangement, regional rules, and other commercial terms.

A merchant may receive a percentage of an eligible conversion margin, a contractually defined share of DCC economics, a periodic incentive calculated from qualifying volume, or no direct DCC revenue at all. Merchants should read the actual agreement rather than assuming that enabling DCC automatically creates a new revenue stream.

It is also important to separate the cross-border transaction margin from the merchant’s ordinary sale proceeds. If a hotel sells a room for €300 and a DCC provider converts it to a disclosed cardholder-currency amount, the hotel’s room revenue and any separately calculated DCC revenue share are economically different items.

DCC revenue may also be reported independently from normal payment settlement. A merchant could receive the proceeds of the original sale through its regular settlement process while receiving DCC revenue share later in a separate settlement line, monthly statement credit, incentive report, or provider payment.

That reporting design matters to finance teams because a strong month for international card payments may not produce an immediately obvious increase in bank deposits attributable to DCC.

Foreign Exchange Markup Split

A DCC exchange rate typically starts with some reference or base FX rate established under the provider’s methodology. The DCC service then applies its commercial conversion pricing to create the rate presented to the cardholder.

The economic difference created by that pricing may be described contractually as a markup, margin, commission, conversion spread, or similar term. 

Mastercard notes that a DCC markup is a commercial arrangement and does not necessarily represent a comparison with a market rate, although regulations in some jurisdictions may require comparison with a central-bank benchmark.

This creates several concepts merchants should keep separate:

• Reference/base exchange rate: The underlying FX benchmark or provider reference used in the conversion methodology.
• DCC exchange rate: The actual rate used to calculate the cardholder-currency amount.
• DCC markup: The additional conversion pricing incorporated into or associated with the presented rate.
• Conversion margin: The economics resulting from the conversion pricing.
• DCC revenue share: The contractual portion, if any, allocated to the merchant or another participant.

The existence of a markup does not mean the entire amount goes to the merchant. A foreign exchange markup split can involve multiple parties, and the merchant may receive only the portion specified by its agreement.

Example of DCC Economics

Consider a fictional transaction solely for education. These numbers are not current market rates, recommended pricing, or representative industry percentages.

A retailer sells merchandise for €200.

Assume the DCC provider’s hypothetical reference rate is:

€1 = $1.1000

At that reference rate:

€200 × $1.1000 = $220.00

Now assume the customer-presented DCC exchange rate is hypothetically:

€1 = $1.1440

The DCC transaction amount would be:

€200 × $1.1440 = $228.80

In this simplified illustration, the difference between $220.00 and $228.80 represents $8.80 of conversion economics relative to the hypothetical reference rate.

If the merchant’s contract hypothetically allocated 20% of that particular calculated margin to the merchant, the merchant portion would be:

$8.80 × 20% = $1.76

Again, 20% is invented only to demonstrate the arithmetic. It is not a typical DCC merchant revenue share, benchmark, network requirement, or recommended contract term.

In a real program, the provider may calculate eligible margin differently, exclude certain transactions, account for refunds, use different reference-rate methodologies, settle revenue share periodically, or apply additional contractual conditions.

Why DCC Revenue Is Not Free Money

DCC merchant revenue can look attractive because it may monetize payment activity that the merchant is already processing. But increasing DCC acceptance at any cost can create larger losses elsewhere in the customer relationship.

Customers react negatively when they believe a currency conversion was forced on them, when the markup was difficult to identify, when the local-currency option appeared visually subordinate, or when employees implied that DCC would avoid all other foreign exchange fees.

The resulting costs may include:

• customer-service complaints;
• refunds or transaction reversals;
• disputes or chargebacks;
• negative hotel, restaurant, or retail reviews;
• lower repeat business;
• ecommerce checkout abandonment;
• additional staff time;
• processor or network remediation;
• compliance exposure.

Visa’s rules are especially relevant here. Visa requires merchants offering DCC to inform cardholders that it is optional, avoid language or procedures such as preselection that could cause DCC to be chosen by default, and ensure the cardholder expressly agrees.

Mastercard likewise states that DCC should not be the default, that customers must not be required or steered into using it, and that the offer must be presented neutrally.

These standards illustrate why the strongest DCC program is not necessarily the one with the highest acceptance rate.

Imagine two hotels. Hotel A has a moderate DCC acceptance rate because employees neutrally present the terminal and allow travelers to choose. Hotel B has an unusually high acceptance rate because employees routinely press the DCC option on behalf of guests.

Hotel B might generate more short-term DCC revenue. It may also create more disputes, more complaints, weaker reviews, and evidence that cardholder choice was not genuine.

The right objective is sustainable DCC performance, not maximum conversion.

What Merchants Must Disclose Before DCC Is Chosen

DCC disclosure requirements are central to cardholder consent because the customer needs enough information to understand the choice before the payment is finalized.

Visa’s consumer guidance says merchants and ATMs offering DCC should clearly display the transaction amount in both the local and cardholder currencies, the currency symbols, the exchange rate used, and additional fees or markup. 

Visa also states that the customer should be able to accept or decline the conversion without the merchant choosing on the customer’s behalf.

Visa’s formal rules require DCC to be optional and expressly agreed to by the cardholder.

Mastercard’s current DCC merchant guide similarly emphasizes:

• local and billing-currency amounts;
• the exchange rate;
• applicable fees and markups;
• a neutral choice of currencies;
• equivalent presentation of the options;
• required disclosure language in environments where the applicable standard calls for it.

Merchants should not copy disclosure wording from a blog, an old terminal, or another merchant. Exact requirements can vary by network, acceptance environment, jurisdiction, and provider certification.

Your acquirer or DCC provider should supply the certified screen design, disclosure logic, localization, receipt fields, and required wording for each supported environment.

DCC Must Be a Genuine Choice

A compliant DCC offer is not simply a screen that technically contains two currencies. The cardholder must actually be given a meaningful opportunity to select between them.

Merchants should not:

• preselect DCC where affirmative choice is required;
• hide the local-currency option below another screen;
• use a much larger button for home-currency payment;
• describe DCC as mandatory;
• imply that a bank requires the conversion;
• obscure the exchange rate or markup;
• select the currency for the cardholder;
• rush the customer past the choice;
• tell staff to maximize acceptance by recommending DCC.

Visa specifically prohibits procedures that cause DCC to be chosen by default and requires express cardholder agreement.

Mastercard’s guidance also warns against steering, biased presentation, default implementation, and DCC performed without consent.

A button marked “continue” for DCC and “decline” for local currency may also create a different psychological impression than two equally prominent currency options.

POS and Ecommerce DCC Disclosure

The principles behind DCC consent are similar across channels, but the user experience differs significantly between a physical terminal and an online checkout.

At a point of sale, the cardholder may have only a few seconds to read a payment terminal while an employee waits nearby. That makes display hierarchy, button labels, terminal positioning, and employee behavior especially important.

The POS should give the customer a clear opportunity to see both payment currencies and the applicable DCC information before authorization. Staff should hand control of the currency decision to the customer rather than pressing a button on the customer’s behalf.

A restaurant or retailer should also consider whether customers can comfortably read the terminal before making a selection. A technically compliant screen provides little practical value if the terminal remains behind the counter where the customer cannot see it.

Ecommerce DCC Disclosure

Ecommerce DCC requires the same basic commitment to customer choice, but the checkout flow must communicate the information without a cashier present.

Mastercard’s compliant ecommerce example shows two clearly presented currency options, the exchange rate, both local and billing-currency amounts, the margin, and a required cardholder disclosure statement.

A well-designed ecommerce implementation should make the following visible before the payment is submitted:

• the merchant’s local transaction amount;
• the offered cardholder-currency amount;
• the DCC exchange rate;
• applicable markup or fees required to be disclosed;
• two clear currency choices;
• any required network disclosure;
• the customer’s active selection.

The order confirmation should also preserve enough information for the customer to understand which currency was selected.

Geolocation may help a merchant localize a website or display relevant content, but it should not be treated as proof that a card is eligible for DCC. Eligibility is fundamentally a payment-program question that the processor or DCC platform must determine using the applicable network and card data.

What Should Appear on a DCC Receipt?

Receipts matter because they create a record of the amount, currency, conversion, and cardholder choice after the transaction.

Visa’s current public rules list required receipt content for DCC transactions. The requirements include transaction amounts with currency symbols in the merchant’s local currency and the transaction currency, the currency conversion rate, conversion commission, fees, markup or margin over the applicable reference rate, and a visible statement that the cardholder was offered a choice of currencies and expressly agreed to the transaction. 

Visa also requires a statement identifying the merchant, branch, or ATM acquirer as conducting the DCC conversion.

Visa’s consumer DCC guidance likewise states that the local and cardholder-currency amounts, exchange rate, and additional fees or markup should appear on screens and receipts.

Mastercard’s DCC guide contains separate examples for acceptable POS receipts, ATM receipts, advice slips, and unacceptable receipt presentations. It stresses that pertinent transaction information should be displayed to the cardholder and provides network-specific receipt guidance.

For merchant operations, a DCC receipt record will commonly need to preserve relevant fields such as:

• merchant-local transaction amount;
• converted transaction amount;
• each currency;
• exchange rate;
• applicable markup or fee information;
• indication of the cardholder’s selected currency;
• identifiers needed to link the transaction to refunds and disputes.

Do not create your own substitute wording for required network statements. The acquirer or certified DCC provider should configure network-specific receipt content.

Receipt accuracy is also operationally important. When a traveler contacts support weeks later, the receipt may be the clearest evidence showing what currency was presented and selected.

DCC and International Cardholder Trust

Dynamic currency conversion succeeds or fails at the intersection of economics and trust.

For some travelers, seeing a purchase immediately expressed in a familiar billing currency is genuinely helpful. The customer does not need to mentally estimate the value of a hotel room, restaurant bill, or retail purchase, and the converted purchase amount is displayed before authorization.

That convenience is real, but so is the customer’s sensitivity to conversion pricing.

A traveler may become frustrated if the DCC exchange rate appears materially less favorable than expected. The reaction can be stronger when the local-currency option was hard to identify or the merchant appeared to push the converted amount.

The problem is not limited to the transaction itself. Customers frequently interpret payment behavior as part of the merchant’s broader honesty and service quality.

A guest who feels pressured into DCC at hotel checkout may not describe the experience as a technical foreign-exchange issue. The guest may instead conclude that the property inserted a hidden fee into the bill.

That perception can lead to:

• negative reviews;
• requests to reverse the transaction;
• complaints to the issuer;
• disputes about consent;
• reduced willingness to return;
• distrust of future payment prompts.

The risk is especially significant for hospitality and travel businesses because international customers may already be navigating unfamiliar taxes, deposits, exchange rates, gratuities, and local payment customs.

DCC therefore works best when it is treated as a transparent optional service.

When DCC Can Improve the Customer Experience

DCC can deliver legitimate convenience when the customer:

• wants to see an immediate converted amount;
• prefers budgeting in the billing currency;
• finds the local currency unfamiliar;
• understands the exchange rate and markup shown;
• is given enough time to compare the alternatives;
• voluntarily chooses the converted currency.

A traveler with a fixed travel budget may prefer knowing the presented cardholder-currency purchase amount at checkout instead of waiting for issuer processing.

That does not mean the transaction is cheaper. It means the customer values immediate currency certainty enough to select the DCC option after seeing the relevant information.

When DCC Costs Customer Trust

DCC becomes a customer-experience problem when revenue objectives start shaping the currency choice.

Warning signs include:

• high markups paired with weak disclosure;
• employees selecting DCC automatically;
• local currency displayed less prominently;
• statements that DCC is “required”;
• promises that DCC avoids all foreign transaction fees;
• inconsistent receipts;
• refunds in a different currency;
• customer-support staff unable to explain what happened.

The key distinction is merchant revenue share vs customer savings. A merchant receiving DCC revenue does not mean the customer saved money.

Merchants should never use revenue-share economics as evidence that DCC is financially better for the traveler.

DCC and Foreign Transaction Fees

One of the most common DCC misunderstandings is the belief that choosing the cardholder’s home currency automatically eliminates the issuer’s foreign transaction fee.

It does not.

A foreign transaction fee is generally established by the card issuer under the customer’s cardholder agreement. An issuer may base the fee on factors beyond whether a currency conversion occurred at the merchant, including the international nature or location of the transaction.

That means a cardholder could select DCC, pay the merchant-side DCC markup, and still encounter a separate issuer charge depending on the issuer’s policies.

Conversely, a cardholder whose card does not impose a foreign transaction fee may have different economics when comparing local-currency processing with DCC.

Merchants generally do not know enough about the individual card account to promise either outcome.

The safest customer-facing approach is to explain only what the merchant controls:

• the local transaction amount;
• the DCC amount;
• the presented exchange rate;
• the disclosed DCC markup or fee;
• the ability to choose either currency.

If a customer asks whether the issuing bank will charge another fee, staff should recommend checking the cardholder agreement or asking the issuer.

For merchants trying to understand the broader cost of accepting cards issued abroad, Host Merchant Services’ overview of international processing fees provides additional background on international card-processing costs, although specific network pricing should always be verified against current processor and network documentation.

DCC vs Multi-Currency Pricing and Multi-Currency Settlement

Dynamic currency conversion is sometimes confused with multi-currency pricing because both can expose customers to prices in different currencies. Operationally, however, they solve different problems.

DCC typically begins with a transaction denominated in the merchant’s local currency. When an eligible international card is presented, the checkout offers a conversion into the cardholder’s billing currency.

Multi-currency pricing, by contrast, can allow a merchant to establish or display product prices in multiple currencies as part of its pricing and ecommerce strategy before the payment-card DCC decision arises.

A global ecommerce business might, for example, operate storefront pricing in U.S. dollars, euros, and pounds based on the shopper’s chosen storefront. That is not automatically a DCC transaction.

Visa’s rules treat DCC and Multi-Currency Pricing as distinct payment concepts and specify separate requirements for each.

Merchants should therefore ask their processor whether an international checkout feature is actually DCC, multi-currency pricing, another currency-presentment service, or a combination.

DCC vs Multi-Currency Settlement

Customer payment currency is also different from merchant settlement currency.

A shopper might pay in a cardholder currency while the merchant ultimately receives settlement in a separate configured currency. Alternatively, a merchant may accept transactions in several currencies and maintain settlement accounts in those currencies.

DCC answers the customer-facing question: Which currency does the cardholder choose for this payment?

Multi-currency settlement answers a merchant treasury question: Which currencies can the merchant receive, hold, or settle?

The two can interact, but one does not automatically determine the other.

This distinction matters for accounting because a merchant that sees a DCC payment in dollars should not assume the acquiring bank will deposit dollars into the merchant’s account.

Ask your acquirer to document authorization currency, clearing currency, settlement currency, FX treatment, and DCC revenue-share reporting separately.

DCC for Hotels, Restaurants, Retailers, and Ecommerce Merchants

DCC implementation should reflect the merchant’s operating environment. A payment flow that works for a simple retail purchase may need additional controls for hospitality authorizations, restaurant tips, delayed charges, or ecommerce refunds.

Hotels should pay particular attention to how DCC interacts with preauthorizations, deposits, final folios, incremental authorizations, delayed charges, no-show transactions, and refunds.

Not every transaction type or stage should be assumed to be DCC eligible. The acquirer should provide specific instructions for each hotel payment workflow.

Guests also need consistency. If an initial hotel authorization occurs in one currency but the final transaction is offered differently, staff should understand exactly what the terminal is doing before describing it to the guest.

Restaurants face another challenge: gratuity.

Depending on the local payment flow, the tip may be entered before or after the currency choice. Merchants need a processor-approved configuration so that the amount shown, conversion, authorization, receipt, and final transaction remain consistent.

Retailers tend to face a different problem: speed.

At a busy store, employees may be tempted to press through currency prompts to shorten the line. That is exactly when cardholder currency choice can be compromised.

Retail training should make one rule unmistakable: when the DCC choice appears, turn the terminal toward the customer and allow the customer to select.

Ecommerce merchants must instead focus on interface clarity, eligibility logic, explicit selection, order-confirmation details, refund behavior, and customer-service records.

A shopper’s IP address can help localize content, but it should not independently trigger an assumption about billing currency or DCC eligibility.

Refunds and Chargebacks on DCC Transactions

DCC refunds require special attention because currency conversion can turn a routine return into a customer complaint.

Mastercard’s current DCC guide states that refunds should be processed in the same currency used for the original transaction. Its refund guidance discusses reversals, credits matching the original DCC currency and amount, and certain credits using the original transaction’s exchange rate.

The operational takeaway is straightforward: do not improvise a refund by choosing whatever currency happens to be convenient on the terminal.

A merchant should be able to retrieve the original transaction and process the refund according to the acquirer’s network-compliant DCC workflow.

Exchange-rate movement can make refunds particularly confusing. The customer may compare the amount received later with the original payment and assume any difference reflects merchant misconduct.

Merchants should not promise that every later refund will always produce exactly the same account-level outcome in the customer’s billing currency unless their processor and applicable rules support that claim.

DCC and Chargebacks

Poor DCC consent can also contribute to disputes.

Visa’s dispute rules address situations in which a cardholder says DCC was applied without agreement or the cardholder was not allowed to pay in the merchant’s local currency. Visa’s rules indicate that the acquirer may need evidence that the cardholder expressly agreed to DCC.

That makes documentation important.

For each DCC payment, merchants should preserve whatever transaction evidence their processor makes available, including currency-choice data, receipts, timestamps, exchange-rate information, terminal or checkout records, and transaction identifiers.

Do not create your own chargeback reason-code guidance unless it comes from current network or processor documentation. The correct dispute category and evidence package depend on the network and circumstances.

For a broader introduction to dispute management, merchants can review this verified guide to understanding and handling chargebacks. Specific DCC disputes, however, should be handled using the latest network and acquirer rules.

DCC Reconciliation and Accounting

DCC adds another data layer to international card payments. Finance teams should be able to connect the original sale, currency conversion, processor settlement, refunds, and any DCC revenue-share payment.

At minimum, consider retaining or reconciling:

• original merchant-local amount;
• local currency;
• DCC cardholder-currency amount;
• DCC currency;
• exchange rate;
• markup or conversion information;
• transaction ID;
• authorization or processor reference;
• settlement amount;
• refund or reversal status;
• revenue-share amount;
• DCC provider or processor report.

A conceptual DCC revenue reconciliation flow is:

DCC Transaction → Conversion Margin → Provider/Acquirer Calculation → Merchant Revenue Share → Settlement/Statement → Accounting

The important point is that each arrow may represent a different report or timing cycle.

The original sale could settle on the merchant’s normal schedule while the DCC revenue share is calculated after the fact. Refunds may then reduce qualifying DCC volume or create adjustments in a later statement.

Finance teams should therefore avoid estimating revenue share simply by multiplying total international sales by a percentage.

Instead, reconcile the provider’s definition of:

• eligible DCC transactions;
• accepted DCC transactions;
• reversals;
• refunds;
• excluded card products;
• conversion margin;
• merchant share;
• adjustments;
• payment date.

For accounting purposes, many businesses may choose to track DCC-related income separately from merchandise, room, restaurant, or service revenue so management can evaluate the economics independently. The appropriate classification depends on the organization’s accounting policies and professional guidance.

This article does not provide individualized accounting or tax advice.

How to Measure DCC Performance

DCC acceptance rate is useful, but it should never be the only metric.

A merchant should measure both financial performance and customer outcomes.

Useful metrics can include:

• number of eligible international transactions;
• DCC offer rate;
• successful offer rate;
• customer DCC acceptance rate;
• DCC sales volume;
• conversion revenue;
• merchant revenue share;
• average DCC revenue per accepted transaction;
• refund rate;
• complaint rate;
• chargeback or dispute rate;
• checkout abandonment rate for ecommerce;
• staff-related DCC complaints;
• receipt or disclosure defects.

No universal “good” acceptance percentage should be assumed. Results vary by customer mix, geography, currencies, card products, merchant category, markup, staff behavior, channel, and seasonality.

Customer Acceptance Rate Is Not the Only KPI

An extremely high acceptance rate can actually be a signal worth investigating.

If one store accepts DCC on 40% of eligible offers and another accepts it on nearly every transaction, the second location may have exceptionally receptive customers—or employees could be making the choice for them.

Review:

• complaint data;
• mystery-shopper results;
• terminal logs;
• transaction videos where lawfully available;
• employee practices;
• currency-choice records;
• unusual location-level acceptance patterns.

A sustainable program should optimize for informed choice rather than maximum conversion.

Compare the additional DCC merchant revenue with the value of refunds, disputes, customer-service labor, negative reviews, and lost repeat business.

That is the more complete measure of cross-border transaction margin performance.

Staff Training for DCC Payments

Employees are often the most important control in a card-present DCC program because they stand between the terminal and the customer.

Training should explain what DCC is without turning staff into foreign-exchange advisers.

Employees should know how to:

• explain that the terminal is offering two currency choices;
• identify which amount is the merchant-local amount;
• let the customer read the exchange-rate information;
• hand or turn the terminal toward the cardholder;
• avoid selecting a currency for the customer;
• avoid saying DCC is mandatory;
• avoid saying DCC is cheaper;
• avoid promising there will be no issuer foreign transaction fee;
• explain where relevant receipt information appears;
• follow the processor’s DCC refund workflow;
• escalate questions they cannot answer.

Training should also address incentives.

If employees receive bonuses tied directly to DCC acceptance, the merchant should consider whether that compensation structure could encourage steering.

Managers should periodically observe real checkouts and review complaints rather than relying solely on completion of an online training module.

Role-playing can help. Have one employee act as a traveler who asks, “Which one should I choose?” The trained response should direct the traveler to the displayed currencies, rate, and charges without making unsupported claims about the customer’s bank.

For hotels and restaurants, training should include realistic scenarios involving deposits, incremental authorization, gratuity, split payments, final folios, and refunds.

The objective is consistency. A cardholder should receive the same neutral currency choice regardless of which employee is working.

Common DCC Compliance and Customer-Experience Mistakes

Most serious DCC problems are not caused by complicated exchange-rate mathematics. They result from basic failures in customer choice, disclosure, configuration, and operations.

Common mistakes include:

• preselecting the home-currency option;
• hiding or visually minimizing local currency;
• failing to display the applicable exchange rate;
• omitting required markup or fee information;
• pressing a currency button on behalf of the cardholder;
• suggesting that DCC is required by the bank;
• promising that DCC is always cheaper;
• promising that DCC eliminates issuer FX fees;
• offering DCC on transactions or card products that are not eligible;
• producing incomplete receipts;
• issuing refunds through the wrong currency workflow;
• failing to retain evidence of consent;
• failing to reconcile revenue-share adjustments;
• measuring success only by acceptance rate.

Visa’s public materials are particularly clear that cardholders should receive the relevant currency amounts, exchange rate, and fee or markup information and should not have the choice made for them.

Mastercard similarly requires a clear and neutral currency choice and prohibits automatic DCC without consent.

The most effective control is to make compliant behavior the easiest behavior. Terminals should present the right information automatically, ecommerce screens should require an active selection, receipts should be system-generated, and refunds should retrieve the original transaction details instead of asking staff to reconstruct them manually.

Merchant DCC Checklist

Use this checklist with your processor or DCC provider before launch and during periodic compliance reviews.

Area	What to Verify
Card/network eligibility	The system offers DCC only when the card and transaction qualify
Local-currency option	Merchant-local currency remains clearly available
DCC currency option	Cardholder-currency amount is accurately presented
Exchange-rate display	The applicable DCC exchange rate is visible before selection
Markup disclosure	Required markup, margin, fee, or commission information is shown
Explicit consent	Customer actively chooses the DCC currency
Receipt	Network-required DCC information appears correctly
Refund workflow	Refunds follow the processor’s network-compliant DCC procedure
Staff training	Employees understand neutral currency presentation
Revenue-share reporting	Provider supplies transaction-level DCC revenue data
Complaint monitoring	Customer-service and dispute trends are reviewed

Also test the program after terminal software upgrades, payment-gateway changes, network certification updates, or changes to the DCC provider.

Card-network rules can change. The merchant agreement should specify who is responsible for updating terminal logic, ecommerce screens, disclosure wording, card-range eligibility, and receipts when requirements change.

For primary reference material, review Visa’s DCC consumer guidance, the current Visa Core Rules and Visa Product and Service Rules, and Mastercard’s Dynamic Currency Conversion Performance Guide.

Questions to Ask a Processor or DCC Provider

Before enabling dynamic currency conversion at checkout, merchants should request precise answers to the following questions.

1. Which cards, networks, and currencies are eligible?
   Ask for current supported card products, billing currencies, merchant currencies, countries, acceptance environments, and known exclusions.
2. Who sets the DCC exchange rate?
   Identify the DCC provider and understand how often rates are updated.
3. What markup is presented to the customer?
   Ask how the markup is calculated and how it appears on POS and ecommerce screens.
4. How is the merchant revenue share calculated?
   Request the contractual formula rather than a marketing summary.
5. Which transactions generate DCC merchant revenue?
   Confirm whether refunds, reversals, specific cards, currencies, or transaction types are excluded.
6. When is revenue share paid?
   Determine whether it appears with normal settlement, on a statement credit, or as a separate periodic payment.
7. What network disclosures are required?
   Request certified screen examples for every supported card network.
8. How is cardholder consent recorded?
   Determine what evidence exists if a customer later disputes the currency choice.
9. Can DCC be declined easily?
   Review both the physical terminal and ecommerce interface.
10. What appears on the receipt?
    Confirm local amount, DCC amount, exchange rate, applicable markup information, and required consent statements.
11. How are refunds handled?
    Ask for workflows covering full refunds, partial refunds, reversals, delayed refunds, and unavailable original cards.
12. How are DCC-related chargebacks handled?
    Ask what transaction records the processor provides to support a dispute response.
13. How does DCC appear in settlement reports?
    Request sample transaction-level and monthly reporting.
14. Are ecommerce and card-present configurations different?
    Confirm channel-specific disclosure and consent requirements.
15. What happens when network rules change?
    Define who updates software, disclosures, certification, card eligibility, and merchant training.

A provider that cannot explain these fundamentals may not be ready to support a transparent DCC program.

Frequently Asked Questions

Conclusion

Dynamic currency conversion can be useful when it does exactly what its name implies: gives an eligible international customer a clear opportunity to choose how a transaction is converted.

For merchants, DCC may also create additional commercial value through a DCC revenue-share agreement. That opportunity should be evaluated carefully because the foreign exchange markup split, merchant share, eligibility rules, settlement process, and reporting model differ from one provider and acquiring arrangement to another.

The central compliance principle is cardholder choice.

Visa requires DCC to be optional, prohibits default procedures such as preselection, and requires express agreement. Mastercard similarly requires a neutral offer, prohibits automatic DCC without cardholder consent, and provides detailed guidance for compliant screen, receipt, and refund behavior.

Merchants should therefore evaluate a DCC program on more than conversion revenue.

Look at customer complaints, refunds, disputes, receipt accuracy, staff behavior, ecommerce abandonment, reconciliation accuracy, and repeat-business effects alongside DCC acceptance and revenue share.

When implemented transparently, dynamic currency conversion at checkout can give travelers useful home-currency visibility while giving merchants another way to monetize eligible international card payments.

When implemented aggressively, it can turn a few dollars of conversion margin into a much larger customer-trust problem.

Before enabling DCC, ask the processor who sets the exchange rate, how the markup is disclosed, how the merchant share is calculated, how consent is recorded, how refunds work, and how current Visa and Mastercard requirements are kept up to date.

The merchant’s goal should not be to make every eligible customer choose DCC. It should be to make every eligible customer understand the choice.

This article is provided for general informational and payment-services education purposes only. Card-network rules, processor requirements, commercial agreements, regional regulations, exchange-rate practices, accounting treatment, and issuer fees can change or vary by transaction. Merchants should confirm current requirements with their acquirer, processor, DCC provider, card networks, legal counsel, and accounting professionals before implementing or changing a DCC program.