← Full guide: Dynamic Currency Conversion: Why Paying in INR Abroad Can Cost More

Use a receipt-level comparison

For “Use a receipt-level comparison”, check. DCC transaction. Local-currency transaction. Conversion decision. Made at merchant/ATM.

Start here

For “Use a receipt-level comparison”, check. DCC transaction. Local-currency transaction. Conversion decision. Made at merchant/ATM. Handled later by network/issuer. Rate visibility. DCC rate should be disclosed before acceptance. Final converted amount appears through issuer processing. Merchant-side markup. May be included/disclosed. No DCC markup because DCC was declined. Issuer fees. Check card terms. Check.

What applies to this exact problem

CheckDCC transactionLocal-currency transaction
Conversion decisionMade at merchant/ATMHandled later by network/issuer.
Rate visibilityDCC rate should be disclosed before acceptanceFinal converted amount appears through issuer processing.
Merchant-side markupMay be included/disclosedNo DCC markup because DCC was declined.
Issuer feesCheck card termsCheck forex/international transaction terms.

Check these first

  • Check: DCC transaction.
  • Conversion decision: Made at merchant/ATM.
  • Rate visibility: DCC rate should be disclosed before acceptance.

Fix it in this order

  1. Check: DCC transaction.
  2. Conversion decision: Made at merchant/ATM.
  3. Rate visibility: DCC rate should be disclosed before acceptance.
  4. Merchant-side markup: May be included/disclosed.
  5. Issuer fees: Check card terms.
  6. Check DCC transaction Local-currency transaction Conversion decision Made at merchant/ATM Handled later by network/issuer.
  7. For “Use a receipt-level comparison”, check.

Evidence to keep

  • Issuer statement and current outstanding — keep it with the evidence for “Use a receipt-level comparison”.
  • Payment/refund reference and bank debit/credit proof — keep it with the evidence for “Use a receipt-level comparison”.
  • Merchant or payment-channel confirmation — keep it with the evidence for “Use a receipt-level comparison”.
  • Complaint/ticket number and written response — keep it with the evidence for “Use a receipt-level comparison”.

Do not make it harder

  • Paying repeatedly without preserving the first reference For “Use a receipt-level comparison”, that can hide whether the underlying issue is actually resolved.
  • Assuming a merchant refund means the card issuer has posted it For “Use a receipt-level comparison”, that can hide whether the underlying issue is actually resolved.
  • Ignoring the due date while a dispute is open For “Use a receipt-level comparison”, that can hide whether the underlying issue is actually resolved.

How you know it is fixed

  • The official record and your real-world result agree for “Use a receipt-level comparison”.
  • You have enough written evidence to prove the issue is finished if it returns later for “Use a receipt-level comparison”.

If this still isn't resolved

  1. Issuer grievance officer or nodal officer State the unresolved issue explicitly: “Use a receipt-level comparison”.
  2. Payment-system complaint route where relevant State the unresolved issue explicitly: “Use a receipt-level comparison”.
  3. RBI CMS for an eligible unresolved complaint against a regulated entity State the unresolved issue explicitly: “Use a receipt-level comparison”.

Parent-guide references

These references support the parent guide and escalation context. Verify provider-, model-, policy-, or jurisdiction-specific details before an irreversible step.

Need the complete context?

This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.

Open the full guide