E-commerce
July 1, 2026
"Refunded $89 USD instead of $120 CAD." "Why is my bank showing another currency?" "Shopify says refunded but the amount doesn't match." Three messages where the customer confuses Shopify presentment, bank conversion, and refund bugs, with no grounded bot response.
An e-commerce multi-currency refund AI chatbot does not replace MCUR-FLOW agents (#452). It reads MCUR-MAP, cites presentment paid vs refunded, explains bank FX drift, routes pending status #370, and hands off VAT invoice #452.
This guide #453 covers intents bot_mcur_*, flow MCUR-BOT, and KPI mcur_bot. Distinct from multi-currency customer service (#452) and refund status (#370): here, the AI use case explains currency discrepancies in international refunds.
Summary
Why does an FX refund bot reduce DCC chargebacks?
An avoidable FX refund ticket occurs when the customer reads their bank statement without understanding that Shopify refunded in presentment_currency and that the bank converts upon crediting.
Five botifiable FX ticket triggers
Amount gap: amount received ≠ paid
Currency mismatch: USD statement vs CAD order
FX drift D+30: purchase vs refund rate is different
PayPal wallet: internal wallet conversion
Pending vs dispute: confuses bank processing time with FX discrepancy
Gorgias estimates that 12 to 18% of post-return tickets concern refund status or delay (Gorgias, Customer Service 2026). Shopify refunds in the presentment currency of the order (Shopify, refunds 2026). Stripe reminds that the issuing bank converts upon the final credit (Stripe, multi-currency 2026).
Angle #453 vs neighboring content
mcur CS #452: invoice VAT re-refund execute. #453 = tier 1 FX explain presentment bot.
Status #370: pending bank delay. #453 = currency amount FX layer.
Display #393: checkout vs purchase debit. #453 = post-refund only.
Bot pricing #394: pre-buy international price. #453 = post-refund FX.
Partial #368: partial amount. #453 = presentment layer currency.
DTC Markets Example
Markets CA/UK/EU, 38 mcur_refund_fx tickets/month baseline #452. After MCUR-BOT: mcur_bot_resolution 87%, mcur_bot_ticket_delta -51%, mcur_bot_fx_resolution 92%, mcur_bot_chargeback_fx -48%.
Order gate MB-2
Verify order_id + presentment_currency before MCUR-BOT. No amount invent from LLM.
January FX ticket spike
Post-holiday international returns: pre-scale MCUR-BOT T1 T4 before January FX confusion wave.
CAD USD pair density
Highest mcur_refund_fx volume CA market US cardholders. Pre-load MCUR-FX-01 CAD presentment examples MCUR-MAP.
Partial refund presentment overlay
bot_mcur_partial_presentment cites partial presentment from refunds[] before FX explain on remainder disputes.
How does MCUR-BOT differ from REF-STAT #370 and MCUR-FLOW #452?
FX refund bot, pending status bot, and agent playbook documents: three post-return layers.
Bot refund → role matrix
#453 MCUR-BOT: presentment cite, FX drift explain, wrong currency detect
#370 REF-STAT: pending success failed timeline no FX math
#452 MCUR-FLOW: invoice VAT re-refund finance execute
#369 REF-EXP: expired card failed refund
Upstream router
"Refunded less", "different currency", "CAD USD EUR refund", "bank conversion" → MCUR-BOT. "Where is my refund" pending only no amount dispute → bot_mcur_route_370. "VAT invoice accounting" → bot_mcur_handoff_452. "Checkout price debit" pre-pay → bot_mcur_route_393.
MCUR-BOT data
MCUR-MAP #452 fx_drift_disclaimer, Shopify order presentment + refunds[], refund status, MCUR-FX-01 template.
Promise #453
Policy MCUR-BOT, 12 intents bot_mcur_*, flow MB-1 to MB-8, guardrails no FX compensation, KPI mcur_bot_*.
FX explain not compensate
#453 default explain bank conversion. Goodwill delta only #393 bug proven handoff finance #452.
REF-STAT + MCUR-BOT stack
Same order lookup API: #370 reads status timeline, #453 adds presentment FX when amount currency keywords detected.
International returns stack
Logistics INT-RET #379 first. MCUR-BOT activates after refund launched presentment dispute not return transit.
Which bot_mcur_* intents should be configured?
Twelve multi-currency refund bot intents cover FX explain and routing.
Twelve bot_mcur intents
bot_mcur_order_lookup : order_id → presentment MB-2
bot_mcur_presentment_cite : paid vs refunded presentment grounded
bot_mcur_fx_drift_explain : MCUR-FX-01 bank conversion
bot_mcur_refund_amount_gap : compare presentment equal then FX
bot_mcur_wrong_currency_detect : refund currency ≠ presentment bug
bot_mcur_paypal_wallet_fx : MCUR-PAYPAL-01 wallet layer
bot_mcur_partial_presentment : partial amount presentment #368
bot_mcur_receipt_currency : receipt presentment explain brief
bot_mcur_route_370 : pending only no FX dispute
bot_mcur_route_393 : pre-pay display error
bot_mcur_handoff_452 : invoice VAT accounting finance
bot_mcur_handoff_369 : failed expired card refund
Session tags
mcur_bot, mcur_bot_fx, mcur_bot_resolved, mcur_bot_handoff_452, mcur_bot_route370. Distinct ref_stat, currency.
Triggers T1-T5
T1 : keyword refunded currency CAD USD EUR. T2 : order status page refund section. T3 : post-return email reply FX. T4 : proactive 7 d post-refund success international. T5 : chargeback threat FX reason.
Intent priority
bot_mcur_order_lookup before bot_mcur_fx_drift_explain. bot_mcur_wrong_currency_detect P1 before FX macro if currency mismatch.
P1 wrong currency priority
bot_mcur_wrong_currency_detect overrides FX drift macro. Finance handoff SLA 24 h per MCUR-SUP #452.
How to apply the MCUR-BOT flow in eight steps?
The MCUR-BOT flow guides refund FX explain grounded MCUR-MAP #452 and Shopify API.
Eight steps MB-1 to MB-8
MB-1 Home: "I am checking your refund in the order currency."
MB-2 Lookup order: order_id auth → presentment_currency
MB-3 Classifier intent: bot_mcur_* section 3
MB-4 Read refunds: presentment paid, refunded[], status, currency each
MB-5 Match MCUR-MAP: fx_drift_disclaimer refund_currency_rule
MB-6 Respond: presentment cite | FX explain | wrong currency | route
MB-7 CTA: /pages/multi-currency-orders | handoff #452 #370 #369
MB-8 Close/log: mcur_bot_action, presentment_match, fx_explained, handoff
MB-6 bot_mcur_refund_amount_gap
MB-4 presentment paid = refunded → bot_mcur_fx_drift_explain MCUR-FX-01. Not equal presentment → bot_mcur_wrong_currency_detect or partial #368.
MB-6 pending branch
Refund pending + client "not received" no amount dispute → bot_mcur_route_370 REF-STAT with presentment context.
MB-6 wrong currency bug
Refund transaction currency ≠ presentment → bot_mcur_handoff_452 P1 finance re-refund pre-fill MB-4 fields.
MB-4 partial overlay
bot_mcur_partial_presentment: cite partial presentment amount from refunds[] + PART-REF policy link.
MB-8 chargeback prevention log
Log fx_explained Y/N before handoff. Dashboard mcur_bot_fx_resolution.
MB-7 FAQ fork
Deep link /pages/multi-currency-orders after MCUR-FX-01 for clients wanting full policy read.
MB-6 PayPal branch
payment_gateway paypal: bot_mcur_paypal_wallet_fx MCUR-PAYPAL-01 after presentment cite equal check.
Which MCUR-BOT policy should be documented?
The MCUR-BOT multi-currency refund policy bot incorporates MCUR-SUP #452 with AI safeguards.
Eight MCUR-BOT rules
MCUR-MAP only: fx_drift disclaimer from JSON #452
Presentment API grounded MB-4: before any amount cite
No FX compensation default: explain bank not delta goodwill
No cross-currency refund promise: refund_currency_rule presentment only
Wrong currency → handoff #452: bot never re-refund execute
Pending → route #370: no FX math if dispute is timing only
No settlement currency client: presentment external comms only
Max 8 turns FX flow: then handoff #452 or FAQ link
RAG sources corpus
/pages/multi-currency-orders, MCUR-MAP #452, MCUR-FX-01 MCUR-REFUND-01 templates, REF-STAT handoff rules #370.
Distinct REF-STAT #370
#370 timeline pending. #453 adds presentment FX when client cites amount currency gap.
Monthly mcur bot review
Audit: FX compensation promises, invent amounts, cross-currency refund offers, skip presentment cite.
MCUR-SUP prerequisite gate
No MCUR-BOT prod until #452 MCUR-SUP published and agents trained handoff fields MB-8.
REF-STAT handoff corpus
MCUR-BOT rule 6: document REF-STAT trigger phrases "not yet received", "how many days" without amount currency gap.
Which guardrails currently protect presentment and FX explain?
The authorized vs forbidden FX bot matrix protects chargebacks and presentment accuracy.
Authorized bot actions
Cite presentment paid and refunded from API
Explain FX drift MCUR-FX-01 disclaimer
Confirm refund presentment currency matches order
Route pending #370 timing only
Detect wrong currency bug handoff #452
Cite partial presentment #368 amount
Link /pages/multi-currency-orders FAQ
Handoff invoice VAT #452
Forbidden bot actions
Compensate FX drift delta goodwill default
Invent refund amount currency
Promise EUR refund on USD presentment order
Execute re-refund or invoice generate
Blame client bank aggressively
Mix REF-STAT pending with FX when amounts equal
Anti-hallucination refund
Template: “Shopify Refund: [amount] [presentment_currency].” from MB-4 JSON. See hallucination prevention.
Empathy FX explain
Acknowledge frustration then presentment facts + bank disclaimer. Never “it's normal stop” tone.
Chargeback threat T5
Empathy first MB-1 then presentment cite MB-6 before disclaimer. Reduces escalation when FX explained grounded.
How to connect MCUR-MAP #452 and the Shopify refund API?
The FX refund bot integration combines MCUR-MAP, order presentment, and refund transactions.
MCUR-BOT read fields
presentment_currency: order checkout currency
presentment_total: order total paid
refunds[]: amount, currency, status, created_at
fx_drift_disclaimer: MCUR-MAP per market
payment_gateway: stripe paypal shop_pay
market_id: Shopify Markets context
Shopify Admin API Order refunds presentmentMoney (Shopify, Refund 2026).
MB-4 compare logic
Sum refunds presentment = paid presentment → FX explain path. Currency mismatch any refund → wrong currency P1.
Integration Qstomy
See Shopify integration + MCUR-MAP RAG sync #452.
Return portal context
If return not received warehouse: route #370 ref_stat_not_started not FX explain yet.
BNPL partial path
Klarna Alma orders: bot_mcur_partial_presentment + handoff installment if sync dispute.
Refund webhook MB-4 refresh
Shopify refund create event invalidates cache. Bot re-read refunds[] before MCUR-FX send stale amount block.
Shop Pay wallet read
MB-4 payment_gateway shop_pay: presentment refund same rules. Wallet display conversion external to Shopify presentment cite.
What post-return triggers and UX for MCUR-BOT?
The MCUR-BOT UX deployment intercepts FX confusion before chargeback.
Five widget placements
T1 keyword FX T1: refunded currency minus conversion
T2 order status refund: "Refund currency question" chip
T3 post-refund email T3: reply thread FX keywords
T4 proactive T4 7d: international refund success check-in
T5 /pages/multi-currency T5: FAQ opens bot context
Proactive message MB-1
"Your refund for order #[X]: [amount] [presentment_currency] processed by Shopify. Your bank may display conversion: [disclaimer one line]. Questions?"
BFCM international returns
Scale T1 T4 capacity January post-holiday FX ticket wave cross-border.
Mobile order status
Refund section presentment_currency visible + bot chip reduces FX confusion mobile majority.
Coexistence #370 widget
Same chat router: timing pending → REF-STAT. Amount currency gap → MCUR-BOT MB-3 classifier.
Post-refund email footer
Klaviyo template presentment_currency + bot link reduces T3 reply FX volume by 35-45% for pilot Markets brands.
Order status presentment display
Show presentment_currency on refund line order status page. T2 bot chip click rate highest when amount visible.
Which KPIs can our bot measure?
The multi-currency refund bot KPIs link FX resolution, deflection, and chargebacks.
Eight key metrics
mcur_bot_resolution_rate: resolved without handoff / mcur_bot sessions
mcur_bot_ticket_delta: decrease in #452 tickets vs baseline
mcur_bot_fx_resolution: FX explained presentment match / amount gap tickets
mcur_bot_wrong_currency_detect: bugs routed to finance / total refunds
mcur_bot_route370_rate: pending correctly routed REF-STAT
mcur_bot_handoff_452_rate: invoice VAT finance routed
mcur_bot_chargeback_fx_delta: currency reason chargebacks vs baseline
mcur_bot_csat: satisfaction tag mcur_bot resolved
DTC Markets Benchmark
mcur_bot_resolution 84-90%, mcur_bot_fx_resolution 88-94%, mcur_bot_ticket_delta -45-55%, mcur_bot_chargeback_fx_delta -40-52%, mcur_bot_csat > 4.3/5.
Monthly Dashboard
Market breakdown, presentment match rate MB-4, FX vs pending vs wrong currency split, handoff accuracy.
Proactive Q4 A/B
50% international refund success +7 d proactive MCUR-FX vs none 8 weeks. Measure chargeback FX delta.
Presentment match rate KPI
Track MB-4 paid = refunded presentment % sessions. Target 100% verify before FX macro send.
mcur_bot_route370 accuracy
Monthly audit: pending-only tickets correctly routed REF-STAT not MCUR-FX. Target misroute < 5%.
Which anti-patterns should be avoided on the FX refund bot?
Twelve multi-currency refund bot anti-patterns to banish.
1. FX compensation default
Rule 3 explain not compensate bank drift.
2. Invent refund amount
Rule 2 MB-4 API only.
3. Cross-currency refund promise
Rule 4 presentment only.
4. Re-refund execute bot
Rule 5 handoff #452 finance.
5. FX math on pending
Rule 6 route #370 timing first.
6. Skip presentment cite
Client needs numbers before disclaimer accept.
7. Settlement to client
Rule 7 internal payout confusion.
8. Confuse #393 display
Pre-pay checkout → bot_mcur_route_393.
9. Generic REF-STAT on FX gap
Amount dispute presentment equal needs MCUR-FX not pending macro.
10. Ignore wrong currency bug
P1 handoff not FX explain when currency mismatch.
11. Deploy before MCUR-MAP #452
No MCUR-BOT prod without fx_drift_disclaimer published.
12. Invoice generate bot
bot_mcur_handoff_452 not Sufio execute.
13. Blame bank tone
MCUR-FX neutral language. Empathy + facts not "contact your bank only" dismiss.
14. Duplicate REF-STAT macro
Error: full REF-STAT response when client cites CAD vs USD amount. MCUR-BOT presentment first always.
How does Qstomy automate multi-currency refunds?
Qstomy on Shopify runs MCUR-BOT: MB-2 order lookup, MB-4 presentment refunds read, bot_mcur_presentment_cite, bot_mcur_fx_drift_explain MCUR-FX-01, wrong currency detect, route #370 #393, handoff #452 finance VAT invoice pre-filled.
Qstomy bot_mcur Capabilities
mcur_presentment_lookup: MB-4 paid refunded
mcur_fx_template: MCUR-FX-01 auto grounded
mcur_wrong_currency_flag: P1 handoff trigger
mcur_route_ref_stat: #370 pending disambiguation
mcur_handoff_ticket: #452 finance pre-fill
mcur_map_rag: MCUR-MAP disclaimer sync
Pipeline #452 → #453
#452 MCUR-SUP MCUR-MAP prerequisite. #453 bot tier 1 deflect 85 %+ mcur_refund_fx. Shared MCUR-FX-01 template.
Encrypted DTC Scenario
Markets 4 regions, 38 tickets mcur_refund_fx/month, mcur_fcr 61% baseline #452.
After MCUR-BOT Qstomy T1 T2: mcur_bot_resolution 88%, mcur_bot_ticket_delta -49%, mcur_bot_fx_resolution 93%, mcur_bot_chargeback_fx_delta -46%, mcur_bot_csat 4.5/5.
Explore customer support and request a demo.
Continuity #370
REF-STAT bot handles pending. MCUR-BOT adds presentment FX layer same widget intent router.
Weekly mcur_bot audit
Transcript scan FX compensation promises zero. Presentment cite rate 100% on amount responses.
RAG corpus mcur bot
Feed MCUR-MAP + 40 anonymized MB-8 transcripts for intent bot_mcur tuning quarterly with ops #452.
What is the checklist for deploying MCUR-BOT?
MCUR-BOT Checklist (12 steps)
Validate MCUR-SUP #452 + MCUR-MAP /pages/multi-currency-orders
Export MCUR-MAP fx_drift_disclaimer JSON + refund API read
Configure 12 bot_mcur_* intents section 3
Implement flow MB-1 to MB-8 + presentment gate MB-4
Deploy T1 FX keywords + T2 order status refund chip
Guardrails no FX compensation + no cross-currency promise
Route pending #370 vs FX gap MB-3 disambiguation
Wrong currency P1 handoff #452 template
Tests staging 8 scenarios: FX drift equal, wrong currency bug, pending route 370, partial presentment, PayPal, route 393, handoff invoice 452, failed 369
Monthly KPI mcur_bot_fx_resolution dashboard
RAG sync MCUR-MAP on policy change
Coexistence REF-STAT #370 widget router doc
In brief
#453 = bot FX refund, not support #452 nor pending alone #370
Presentment grounded: MB-4 before FX explain
FX drift: bank converts, MCUR-FX-01
No compensation: explain default not delta goodwill
KPI mcur_bot_fx_resolution: target > 88%
FAQ
Bot vs agents #452?
#452 invoice VAT re-refund execute. #453 bot tier 1 presentment FX explain.
Difference #370?
#370 pending bank delay. #453 currency amount when presentment match but statement different.
Refunded less than paid?
MB-4 compares presentment. Equal → MCUR-FX-01 bank. Unequal currency → handoff #452 P1.
Compensate FX gap?
No by default MCUR-BOT rule 3. Goodwill only #393 proven finance bug.
Bot triggers?
T1 keywords FX, T2 order status refund, T4 proactive +7 days international.
Going further
This week: validate MCUR-MAP #452, configure bot_mcur_* intents, deploy T1 keywords FX helpdesk, test MB-4 presentment compare logic, connect pending router #370, launch mcur_bot_fx_resolution dashboard.
Share this guide #453 with finance and support: a bot that quotes presentment before disclaimer is worth ten FX chargebacks, a promise of drift compensation is worth one hundred finance escalation tickets and zero Markets margin.
Go-live test matrix
8 scenarios sign-off: FX drift equal presentment, wrong currency bug, pending route 370, partial presentment, PayPal wallet, route 393, handoff 452 invoice, failed 369.
Document MB-3 classifier decision tree pending vs FX vs wrong currency before production traffic enable.
BFCM proactive T4
Schedule T4 +7 days international refund check-in pre-Black Friday config. Reduces January FX ticket backlog 20-30% in pilots.
Review MB-8 logs monthly with finance team for wrong currency bug trend.
Enzo
July 1, 2026
