A French customer pays €89, then sees a USD charge on her bank statement and disputes it as fraud. Nothing went wrong. Her bank converted the amount, and the statement shows a different figure. Multi-currency orders create this ticket type constantly, and single-currency stores almost never see it.
Key takeaways
- Multi-currency tickets are mostly explanation work: the order is usually correct, the statement looks different.
- Shopify refunds the presentment amount the customer paid, not a recalculated one.
- Four ticket types cover most Markets volume; three can be closed with order lookups and a refund.
- Fraud disputes cost more than a refund, so answer fast.
Why do Shopify Markets orders create tickets that single-currency stores never see?
Shopify Markets lets customers pay in their local currency, but the bank settles in another one. Two amounts now exist for one order: the presentment amount the customer saw and the settlement amount you receive. Customers compare the wrong pair, and a support ticket follows.
In the stores we see, a typical Markets store has a ticket mix that looks roughly like this. Treat these as rough working ranges, not a benchmark:
- Order status (WISMO): the largest share, as in any store.
- Charge-amount questions: a small but distinct slice that only appears with multiple currencies.
- Refund-amount questions: often the most heated, because the customer expects a specific number back.
- Tax and price display questions: spikes after a new market launches.
The key point: these tickets are rarely errors. They are expectation gaps, which makes them well suited to a clear playbook.
What does multi-currency change in the refund workflow?
A refund in Shopify Markets is issued in the currency the customer paid in. If a customer paid €89, the refund is €89, even if the exchange rate moved by 3% since the order. The customer's bank then converts it again, so the final amount on their statement can differ from the original charge.
This changes the workflow in three ways:
- Always quote the presentment amount. Say '€89.00 refunded' and never the USD equivalent.
- Warn about bank conversion. Customers paying with a card in another currency may see a slightly different figure.
- Set timing expectations. Refunds typically take 5 to 10 business days to appear, depending on the bank.
Your own books carry the exchange rate risk, not the customer. That is the rule Shopify enforces, and it is the one customers find hardest to believe.
What exchange rate refund rules does Shopify enforce versus what customers expect?
Shopify refunds the amount charged in the customer's currency and does not adjust for rate movements. Customers often expect either the original rate or today's rate, whichever favors them. Neither is available. The refund equals the original presentment amount, which is the only number your store controls.
Citation capsule: In Shopify Markets, a refund is issued in the presentment currency, meaning the currency the customer saw at checkout. A customer who paid €89 receives €89 back, regardless of exchange rate changes between purchase and refund. The store absorbs any gain or loss between presentment and settlement currencies. The customer's bank may then apply its own conversion if the card is denominated in another currency, which can make the statement amounts differ by a few percent. This is not a store error and cannot be corrected from the Shopify admin. The practical reply to a customer is simple: confirm the refunded amount in their checkout currency, explain that the bank's conversion happens after the refund, and suggest they check the bank's own exchange rate for the transaction dates.
A short template helps: state the refunded amount, name the currency, explain the bank step, and give the 5 to 10 day window. Four sentences, no apology spiral.
Should you issue a Markets-region refund or store credit?
Issue a refund to the original payment method by default. Offer store credit only when the customer prefers it or when conversion loss is their main complaint. Store credit in a single currency avoids a second bank conversion, which can save the customer 2% to 4% in card fees.
Use this decision guide:
| Situation | Best option |
|---|---|
| Customer disputes the charge amount | Refund to original method |
| Customer worries about conversion loss | Offer gift card or store credit as an option |
| Customer will reorder in the same market | Store credit, with a small bonus if margin allows |
| Chargeback already opened | Refund first, then reply |
Never push store credit on a customer who has opened a bank dispute. It reads as stalling. With Heylio, the AI can issue a refund or a gift card through its Shopify tools, so the choice you set in your refund playbook is applied the same way each time.
How do you handle 'I was charged twice in two currencies' reports?
Most double-charge reports are one real charge plus one pending authorization shown in a different currency. Authorizations usually drop off within 3 to 7 days. Check the order in Shopify first: if only one successful payment exists, explain the authorization and give the expected drop-off window.
Follow this sequence:
- Look up the order and count successful payments.
- If one payment exists, explain the pending authorization and when it should disappear.
- If two payments exist, refund the duplicate immediately and confirm the amount.
- Ask for a statement screenshot only if the numbers still do not match.
Speed matters here. A customer who thinks they were defrauded will open a bank dispute quickly, and that costs you the order value plus a fee. A reply within minutes often prevents it.
Why do VAT-inclusive and VAT-exclusive prices confuse customers?
Prices shown with VAT in the EU and without tax in the US can make the same product look different across markets. A customer who sees €89 at checkout but remembers a lower figure from a US-based ad feels overcharged. Shopify can show tax-inclusive prices per market, but the setting must match local expectations.
Common triggers:
- A customer compares the cart total against a screenshot from another region.
- Duties and import taxes arrive at delivery for markets where you do not collect them.
- Rounding rules change the displayed price by a few cents.
The fix is mostly upstream: show tax-inclusive pricing where law or habit expects it, and say so in your knowledge base. Then support can answer in one line: the price includes VAT at the customer's local rate.
Which multi-currency tickets can Heylio's AI close on its own?
Heylio's AI can close tickets that need an order lookup, a clear policy, and at most one Shopify action. It escalates cases involving open bank disputes or ambiguous payment records. Handing a conversation to a human is never billed, so only the tickets the AI resolves and the drafts you approve are charged.
| Ticket type | Resolution path | Heylio can close autonomously? |
|---|---|---|
| Charge amount differs from checkout | Look up order, explain bank conversion | Yes |
| Refund amount differs from expectation | Confirm presentment refund, explain bank step | Yes |
| Charged twice in two currencies | Check payments; refund duplicate if confirmed | Yes for the explanation; refund when a duplicate exists, per your playbook |
| VAT or price display confusion | Explain tax-inclusive pricing for the market | Yes, if the KB states the policy |
Bank-opened fraud disputes sit outside this table. Those go to a person.
Pricing is billed in euros per ticket resolved by the AI: €0.49 each, or prepaid monthly packs from 100 resolutions (€39). A Markets store with a few dozen currency tickets a month stays well under the 100-resolution pack.
What should you do next?
Write one playbook for each of the four ticket types above, with the exact refund wording and the 5 to 10 day timing. Add your per-market tax display rules to your knowledge base. Then test them on your last 20 multi-currency tickets. Heylio on a small volume is enough to run that test.