E-commerce
July 1, 2026
An international customer may see a price in euros, pay in another currency, and then notice a different amount on their bank statement. They may also change countries and see the price, taxes, or shipping costs change.
The chatbot can prevent a lot of misunderstandings if it explains the displayed currency, conversion, taxes, potential fees, and what the store genuinely controls.
This guide explains how to answer questions about currencies and international pricing with an AI chatbot, without unnecessary financial jargon.
Summary
Why do international prices create confusion?
The customer often compares the price displayed on the website with the amount debited by their bank. Between the two, there may be a conversion, a bank rate, taxes, international fees, or rounding.
If this difference is not explained, they may think that the shop changed the price at the last minute. The chatbot must therefore clarify what comes from the website and what comes from the payment method.
The right message does not simply say "it depends on your bank". It explains which line items can cause the final amount to vary.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
What information should be checked?
The bot must verify the country, the displayed currency, the payment currency, the shipping address, taxes, shipping fees, discounts, and the chosen payment method.
It must also distinguish between a price localized by the shop and a conversion made by the bank or the payment provider. The customer does not always have this difference in mind.
How do you explain the conversion?
The answer must remain simple: "The site displays the price in [currency]. If your card is in another currency, your bank may apply its conversion rate and sometimes fees."
The bot must not promise the exact rate if the bank decides it. It can explain where the customer will see the final amount before validation or on their statement.
What should be said about taxes and delivery fees?
The price may change after entering the address because taxes and shipping depend on the country. The bot must explain that the final total is calculated with the full context.
It can break down the amount: items, discount, shipping, taxes, and total. This breakdown is much more reassuring than a general answer about international prices.
It also helps identify the source of the discrepancy. The customer can see if the difference comes from more expensive shipping, a local tax, or an off-site conversion.
How to handle a dispute?
If the customer disputes an amount, the bot must ask for the relevant context: currency seen, country, order, checkout screenshot, and amount debited. It must avoid asking for full bank details.
If the discrepancy comes from a bank fee, it explains it. If the displayed price and the paid price seem genuinely inconsistent, it transfers to support.
Which flow to follow?
The flow must make the price legible.
Identify the country, the displayed currency, and the payment currency.
Break down the total: items, discounts, taxes, shipping, and visible fees.
Explain what depends on the store and what depends on the bank.
Compare with the screenshot or the order if the customer disputes it.
Transfer if the discrepancy seems to stem from a pricing or checkout error.
Which messages should be used?
For a conversion: "The price is displayed in [currency]. If your card uses another currency, your bank may apply its own rate."
For a change of country: "The total may change depending on the country because taxes and delivery are recalculated."
For a dispute: "I can verify the total displayed on the order, without needing your full bank details."
When to transfer?
The transfer is necessary if the price paid does not match the checkout, if the currency seems incorrect, if a discount disappears, or if the customer provides a conflicting screenshot.
The bot must forward the country, currency, order, shopping cart, any screenshot, and the disputed amount.
Which KPIs should be monitored?
Track currency-related questions, amount disputes, international drop-offs, conversion errors, bank fee inquiries, and support transfers.
These signals show whether international pricing display is clear enough before payment.
Which mistakes should be avoided?
Avoid promising a bank rate, mixing taxes and conversion, or asking for a full photo of a credit card.
The chatbot must explain the final price without exposing sensitive data.
How can Qstomy help?
Qstomy can use the customer, cart, and order context to answer clearly, then hand over sensitive cases with an actionable summary.
The chatbot simplifies complex questions without creating promises that the brand cannot keep.
Explore AI support, the AI sales agent, or request a demo.
CUR-BOT Checklist (12 steps)
Document policy CUR-DISP #393 + /faq-currency
Configure 12 intents bot_currency_* section 3
Write templates CB-1 to CB-8 EN/FR top markets
Connect order lookup presentment + refunds API
Activate guardrails no_fx_refund_promise hard block
Integrate reroute duties #65, pricing #247, REF-STAT #370
Configure triggers T1-T5 + proactive checkout cap
Staging tests 8 scenarios FX, duties, refund, VPN, scam
Handoff ticket 10 fields to FX-DISP agents
Weekly currency_bot KPI Dashboard
Audit 20 transcripts/month compliance
Correlate quarterly FX chargeback vs baseline #393
At a glance
#394 = bot explains currency, #393 = dispute/chargeback agents
CUR-BOT: order lookup → scope → explanation without FX promise
Grounded presentment: never an invented FX rate
Reroute: duties, pricing error, refund status
KPI currency_bot_resolution: target 70-78%
FAQ
Difference with #393?
#393 policy + FX-DISP agents + chargeback evidence. #394 bot automation standard CB-1 to CB-7.
Can the bot refund the FX difference?
No. CUR-DISP rule 3. Agent handoff if exceptional policy gesture.
Relation to #370 refund status?
#394 explains FX. #370 provides processor delay. CB-8 links the two.
Relation to #16 multilingual?
#16 UI language. #394 international currency and amount intents.
Pre-purchase vs post-purchase?
Bot_currency_pre_purchase without order. Display_charge requires CB-2 lookup.
Go further
Test staging: "my bank charged more" + order_id CAD, verify CB-5 presentment is cited, zero FX refund promise, handoff if screenshot ≠ order.
Share this guide #394 with support and finance: a good currency bot explains the order, not the bank conversion it does not control.
Enzo
July 1, 2026
