What is dynamic currency conversion and why does it cause 12.3 chargebacks?

DCC lets a foreign cardholder pay in their home currency at conversion rates set by the DCC provider, usually with a markup. Visa rules require the cardholder to be offered a clear choice with the rate disclosed; skipping the choice or burying the markup makes the conversion non-compliant. Cardholders who spot the markup on their statement dispute it, and without proof of a compliant opt-in the merchant loses.

My site shows USD but settles in EUR. Is that a problem?

Yes, if the cardholder is charged in a currency they never agreed to. The cleared currency should match the currency presented at checkout, or the conversion must be disclosed and accepted before payment. This mismatch is common with offshore merchant entities, and beyond 12.3 exposure it generates surprise foreign-transaction fees that trigger broader disputes.

Does the cardholder get the whole transaction back under 12.3?

The dispute targets the currency error, and where only the conversion is at issue, the correction can be limited to the difference rather than the full sale. In practice issuers sometimes file for the full amount, so your representment should establish the underlying purchase's validity while addressing the currency delta. Refunding the disputed difference proactively often resolves the case cheaply.

Visa · Processing Errors

Reason code 12.3: Incorrect Currency

The transaction was processed in a currency different from the one the cardholder agreed to, or dynamic currency conversion was applied without the cardholder's informed choice. The dispute asserts a mismatch between the currency shown at the point of sale and the currency of the cleared transaction. DCC handled badly is the dominant real-world trigger.

Issuer filing window

120 days from the transaction processing date

Merchant response window

typically 20-30 days to respond, depending on the acquirer

Why 12.3 chargebacks happen

Dynamic currency conversion was applied automatically without offering the cardholder a genuine choice to pay in their home currency or the local one.
The checkout displayed prices in one currency but the gateway settled in another, a common misconfiguration on multi-currency storefronts.
A cross-border routing setup cleared the transaction through an entity whose settlement currency differed from the price the customer saw.
Staff at a terminal chose the conversion option on the customer's behalf to move through the line faster.
The DCC disclosure omitted the exchange rate or markup, invalidating the cardholder's consent.

How to fight a 12.3 chargeback

Provide the transaction receipt or checkout confirmation showing the currency the cardholder agreed to, matching the currency that cleared.
For DCC transactions, submit evidence of a compliant offer: the rate, the markup disclosure, and the cardholder's affirmative selection of the converted currency.
Show the checkout flow screenshots or order records demonstrating the displayed currency equals the settled currency.
If only the conversion is disputed rather than the purchase, note that the issuer's remedy is limited to the currency difference and present the underlying sale as valid.
Correct genuine mismatches with a partial refund of the difference before representment, then document that correction in your response.

How to prevent 12.3 chargebacks

Make DCC strictly opt-in with the rate and markup displayed before the cardholder chooses, and log the choice with the transaction.
Verify that every storefront locale settles in the currency it displays, and test this on each new geography launch.
If you route volume through offshore entities, keep pricing currency and settlement currency aligned per storefront, or disclose conversion terms explicitly at checkout.
Disable DCC entirely if the conversion revenue is not worth the dispute exposure.
Audit terminal and gateway DCC settings after every processor or hardware change, since defaults often re-enable auto-conversion.

Frequently asked questions

What is dynamic currency conversion and why does it cause 12.3 chargebacks?: DCC lets a foreign cardholder pay in their home currency at conversion rates set by the DCC provider, usually with a markup. Visa rules require the cardholder to be offered a clear choice with the rate disclosed; skipping the choice or burying the markup makes the conversion non-compliant. Cardholders who spot the markup on their statement dispute it, and without proof of a compliant opt-in the merchant loses.
My site shows USD but settles in EUR. Is that a problem?: Yes, if the cardholder is charged in a currency they never agreed to. The cleared currency should match the currency presented at checkout, or the conversion must be disclosed and accepted before payment. This mismatch is common with offshore merchant entities, and beyond 12.3 exposure it generates surprise foreign-transaction fees that trigger broader disputes.
Does the cardholder get the whole transaction back under 12.3?: The dispute targets the currency error, and where only the conversion is at issue, the correction can be limited to the difference rather than the full sale. In practice issuers sometimes file for the full amount, so your representment should establish the underlying purchase's validity while addressing the currency delta. Refunding the disputed difference proactively often resolves the case cheaply.

Related Visa codes