Incorrect Currency Vs Currency Conversion Error: Who Bears The Cost?

Incorrect Currency A processing dispute caused by a transaction being submitted in the wrong currency. It is sometimes conflated with currency conversion errors, but the two problems have different root causes and different paths to liability and resolution.

Understanding the distinction matters when assigning responsibility and forecasting costs. An Incorrect Currency dispute arises when the transaction message itself carries the wrong currency code or the merchant submits a currency that the customer did not agree to. A currency conversion error, by contrast, occurs when a correct currency is converted using the wrong rate or the issuer/applier imposes an unexpected fee. Both can lead to chargebacks, but networks and processors treat them differently during investigation.

Key Differences

• Nature Of The Fault: Incorrect currency is a data/selection error (wrong ISO 4217 code); conversion error is a rate/fee discrepancy during settlement or refund.
• Point Of Failure: Incorrect currency usually originates at checkout or in the gateway message; conversion errors often occur at the issuer, intermediary, or DCC provider.
• Evidence Required: For incorrect currency, evidence must show what was displayed and what currency code was submitted. For conversion errors, proof of the rate and fees applied is required.

How Liability Is Typically Assigned

Assignment of liability depends on the payment flow and contract terms between merchant, acquirer, gateway, and card networks. Typical rules include:

• Merchant Responsibility: If the merchant’s checkout sent the wrong currency code or failed to disclose DCC, the merchant bears primary responsibility.
• Processor/Acquirer Responsibility: If the gateway or acquirer misrouted or converted funds without authorization, the processor can be liable under service agreements.
• Issuer/Network Role: Issuers may apply their own conversion rates and fees; when those differ from disclosed amounts, they often mediate with the merchant during dispute resolution.

How Card Schemes Handle These Cases

Visa, Mastercard, and other schemes assign dispute reason codes and timelines that determine whether representment is viable. Generally:

• Documentation Standard: The merchant must supply receipt images, checkout screenshots, and authorization messages showing the currency code submitted.
• Chargeback Grounds: If the issuer shows the cardholder saw a different charging currency than billed, the issuer may challenge under billing-dispute codes.
• Representment Success: Representment succeeds when transaction logs and settlement files support the merchant’s claim that the correct currency was presented and submitted.

Practical Examples

Example A — Incorrect Currency: A UK customer selects GBP, but an integration bug causes the gateway to submit EUR. The issuer bills the customer in EUR; the cardholder disputes and wins because the captured message shows EUR. The merchant loses the chargeback because the submitted message carried the wrong currency code.

Example B — Conversion Error: A merchant correctly submits USD for a US customer. The issuer converts the amount to the cardholder’s currency using an incorrect rate or adds an undisclosed fee. The cardholder disputes the amount on the statement. The issuer and merchant negotiate; responsibility depends on disclosures and who applied the conversion.

Who Ultimately Pays

Financial responsibility often follows the contractual relationship and evidence trail:

• Merchant Loses When: System logs or settlement files show the wrong currency was submitted or the merchant failed to disclose DCC.
• Processor/Acquirer May Pay When: Their system transmitted an incorrect currency code or unintentionally converted funds during settlement without merchant instructions.
• Issuer May Absorb Costs When: The conversion was applied on the issuer side with no merchant involvement and consumer protections require remediation.

Tips To Reduce Costs

• Clarify Contract Terms: Ensure acquirer and gateway contracts define who handles currency conversion and who bears errors.
• Log Everything: Store authorization request and response messages, including the currency code, to support representment.
• Offer Clear Pricing: Show both local and billing-currency prices and capture shopper consent when offering DCC.

In short, the Incorrect Currency dispute differs from a simple conversion error: one is a data/selection mismatch, the other is a rate/fee problem. Determine liability by tracing the data path, reviewing contracts, and producing the transaction evidence that card networks require.