Root Cause Diagnosis
The issuing bank refuses because the DCC markup is not its fee: the merchant or ATM operator (via its acquirer) converted the amount at its own marked-up rate (typically 3-12% above the network rate) before the transaction reached the card network, so the issuer only sees a valid authorization in your home currency. The markup is embedded in the exchange rate rather than itemized, so first-line support finds no “fee” to reverse. The dispute is only winnable when reframed as a card-network rule violation by the merchant (no disclosure or no cardholder choice), not as a bank fee complaint.
Quick Fix
Send this through your bank’s in-app secure message or dispute form. It uses the wording that routes the case to the chargeback team instead of general support.
Subject: Dispute - transaction processed in incorrect currency without cardholder consent (DCC)
Transaction: [merchant name], [date], [posted amount + currency]
Merchant-currency amount: [local amount + currency]
I did not give informed consent to Dynamic Currency Conversion. The terminal/
merchant did not disclose the exchange rate, markup, and that the conversion
was optional before processing in my billing currency.
Please open a dispute under the network's incorrect-currency / DCC rules
(Visa 12.3 / Mastercard 4834 or current equivalent) and provisionally credit
the difference between the billed amount and the amount at the network
exchange rate.
Step-by-Step Resolution
1. Quantify the markup
Pull the local-currency amount from the receipt and the posted amount from your statement. Get the network rate for the transaction date from the Visa or Mastercard public currency calculator.
local_amount = 250.00 # amount in merchant's currency (receipt)
posted_amount = 3180.00 # amount billed to you (statement)
network_rate = 12.10 # network rate: home currency per 1 unit local, on txn date
fair_amount = local_amount * network_rate
overcharge = posted_amount - fair_amount
markup_pct = (posted_amount / fair_amount - 1) * 100
print(f"Fair amount: {fair_amount:.2f}")
print(f"Overcharge: {overcharge:.2f}")
print(f"Markup: {markup_pct:.2f}%")
Include the overcharge figure in every message from here on. A specific amount is harder to dismiss than “I was overcharged.”
2. Collect evidence of non-compliance
- Itemized receipt or card slip showing both currencies, the rate, and whether a markup line is present.
- Statement line showing the posted amount and currency.
- Proof of how the choice was presented (photo of the terminal screen, or your own written account with date, time, and location).
- For cards used at hotels, car rentals, or restaurants: the signed folio or slip. Check for pre-ticked DCC consent text.
Network rules require the merchant to disclose that DCC is optional, the amount in both currencies, the rate, and any markup or commission, and to obtain active cardholder consent. Missing disclosure is your dispute basis.
3. Ask the merchant to reverse the conversion
Request a refund and re-charge in local currency, or a DCC reversal through their acquirer. Do this in writing (email), keeping the reply. A refusal or no response within 7-10 days becomes supporting evidence for the dispute. Note that cardholders cannot trigger this reversal themselves, so it must come from the merchant.
4. File the formal dispute with the issuer
Do this inside the dispute window, which is generally 120 days from the transaction date under both Visa and Mastercard rules. Verify the current limit with your issuer because it varies by region and card product.
- Request a written dispute reference number.
- State the reason code framing from the Quick Fix. Do not call it a “fee dispute.”
- Ask whether a provisional credit will be issued while the merchant responds.
5. Escalate inside the bank
If the first-level agent rejects it:
- Ask for the case to be reviewed by the chargeback / disputes department.
- Send a written complaint to the bank’s grievance/complaints officer (the address is on the bank’s regulatory disclosures page), quoting the dispute reference number.
- Request the written rejection reason. Regulators require one.
6. Escalate externally
Use the regulator for your jurisdiction once the bank’s internal complaint window has lapsed or the bank issues a final rejection:
| Jurisdiction | Body | Typical precondition |
|---|---|---|
| India | RBI Integrated Ombudsman (cms.rbi.org.in) | Complaint to bank first; no satisfactory reply within 30 days |
| UK | Financial Ombudsman Service | Final response from bank, or 8 weeks without one |
| US | CFPB complaint portal; state regulator | Prior attempt with the bank is expected |
| EU | National financial ombudsman / ADR body | Varies by country |
Attach the markup calculation, evidence, dispute reference number, and the bank’s written rejection.
Why This Fails for Some Users
- Documented consent exists. If the slip has a signature, PIN confirmation, or an “I accept the conversion rate” line, the merchant can represent the chargeback and win. Markup alone does not invalidate valid consent.
- Dispute window expired. After about 120 days, network chargeback rights end. Only a regulator complaint or the merchant’s goodwill remain.
- Unattended or pre-selected flows. Online checkouts, card-on-file bookings, and unattended kiosks can default to DCC. Disclosure disputes are harder here, though a pre-selected default without an explicit opt-in can still violate network rules.
- ATM withdrawals. DCC at ATMs is a cash disbursement, not a merchant purchase, so the dispute category differs and issuers are often less receptive. Dispute with the ATM operator first.
- Separate bank charges. Many issuers apply a cross-border or foreign-transaction fee based on the merchant’s country, not the billing currency. That fee is the bank’s own charge and is usually not refundable on DCC grounds, though you can contest it as a double conversion cost.
- Network and card type differences. Rules and reason codes differ for Amex, Discover, and domestic schemes such as RuPay. Codes are updated periodically, so confirm the current equivalents with the issuer.
- Provisional credit withheld. Some issuers hold the credit until the merchant responds. This is normal and not a rejection, but get the timeline in writing.