Dispute reason responses
Incorrect Currency Chargebacks: Separate Checkout Currency from Statement Conversion
An incorrect-currency dispute requires the merchant to identify the currency accepted at checkout and the currency submitted in the payment transaction. Keep those facts separate from the currency used for the merchant’s payout or the customer’s bank statement conversion.
A customer can see a different numerical amount on a statement without the merchant having submitted a different transaction currency. Conversely, a familiar order total does not prove the payment used the currency the customer accepted. Reconstruct the sequence with currency labels on every relevant amount before choosing a response.
Identify the currency the customer accepted
Locate the purchase-time order and final payment record shown to the customer. Use explicit currency codes where possible. A symbol such as a dollar sign can be ambiguous across markets, so do not infer the intended currency from a symbol alone when better records are available.
Visa includes incorrect-currency dispute conditions. Visa public rules.
Check the selected market or customer-facing currency only as context. The decisive question is the currency associated with the accepted transaction, not the store’s default currency today. A current storefront screenshot cannot establish what was presented for an older order.
If the merchant lacks a historical checkout image, use legitimate order and payment records and describe their source accurately. Do not recreate a screenshot and label it as the customer’s original checkout. A reconstruction can explain a sequence, but it must remain visibly a reconstruction.
Trace authorization, capture, and settlement labels
Compare the transaction currency in the processor’s authorization and capture records where available. Identify whether the challenged entry relates to the same payment and amount. If the provider uses separate presentment and settlement fields, ask the provider to confirm their meaning before interpreting them.
Mastercard’s guide includes currency-related processing disputes. Mastercard Chargeback Guide.
The merchant’s payout currency is a different layer. A payout converted into the merchant’s local currency does not by itself establish that the customer was charged in that currency. Keep payout records out of the core response unless they help explain a specific confusion and their role is clearly labeled.
Likewise, the customer’s statement may reflect an issuer conversion. Do not calculate or attribute an exchange-rate difference without the relevant records. The merchant can state the amount and currency it submitted and identify the bank-statement amount as customer-provided information, with any unverified conversion explanation qualified.
Use a currency-layer worksheet
The following reusable worksheet prevents amounts from different layers being compared as though they were the same event.
| Layer | Amount and currency | Source | Question answered |
|---|---|---|---|
| Accepted checkout | Explicit amount and currency | Purchase-time record | What did the customer accept? |
| Authorization | Provider amount and currency | Authorization record | What was authorized in the payment system? |
| Capture or submission | Provider amount and currency | Captured transaction | What did the merchant submit? |
| Merchant settlement | Payout amount and currency | Settlement record | What did the merchant receive? |
| Customer statement | Reported amount and currency | Relevant customer or issuer record | What is the customer seeing? |
In a hypothetical example, the customer accepts an order in EUR, the processor records the capture in EUR, and the merchant receives a payout in GBP. The customer’s USD statement displays a converted amount. The merchant should show the accepted and submitted EUR transaction and avoid presenting its GBP payout as the customer’s charge currency.
In another hypothetical example, the accepted record says EUR but the submitted transaction says USD. The merchant must investigate that inconsistency with the processor. It should not explain the difference away as ordinary issuer conversion when the merchant-side records themselves conflict.
Write the response within verified boundaries
Lead with the currency accepted and the currency submitted, each linked to its source. If they agree, explain that agreement and address the statement-related confusion only to the extent the available records support it. If they differ, identify the mismatch and obtain provider verification before asserting a defense.
Do not turn this response into a guide to configuring Shopify Markets or calculating foreign-exchange fees. The reviewer needs the actual transaction path. Technical background is useful only when it explains a field that would otherwise be misunderstood.
Check the case’s live response options, deadline, and applicable network conditions. Some processing questions require information held by the acquirer or processor rather than the merchant’s order screen. Ask a specific question and supply the transaction reference so the provider can verify the relevant currency fields.
Where a supported response is available, submit the concise worksheet and relevant records through the actual provider channel, then verify status. Where the records confirm a currency error and no permitted defense applies, follow the appropriate resolution route. The completed analysis should make every currency layer explicit and keep unverified bank-conversion assumptions out of the merchant’s factual claims.
Keep the dispute reason, amount and response deadline visible in Lower Chargeback while you prepare your response in Shopify or with your provider.
Related reading in this collection:
- How to Respond to a Fraudulent Chargeback on Shopify
- Counterfeit Merchandise Chargebacks: How to Build an Authenticity Response
- No Authorization Chargebacks: Which Payment Records Support a Defense?