E-commerce
July 1, 2026
"Send me an invoice in euros for my accounting." "My receipt shows CAD but I paid in USD." "Refunded $89 instead of the $120 CAD paid." Three post-order messages where the customer needs multi-currency documents or a refund, without a dedicated customer service playbook for receipt invoice refund.
Multi-currency e-commerce purchase customer support covers receipt confirmation, VAT invoice accounting, bank statement reconciliation, and order currency refund, distinct from checkout displayed price errors or simple refund pending status.
This guide #452 covers policy MCUR-SUP, flow MCUR-FLOW, and KPI mcur. It completes displayed currency (#393) with receipt, invoice, and refund. Distinct from the upcoming multi-currency refund bot (#453): here, customer service playbook for multi-currency order documents and refunds.
Summary
Why are multi-currency refund receipt invoices increasing?
A post-order multi-currency ticket concerns a receipt, accounting invoice, or refund on an order where the presentment_currency differs from the customer's bank currency or documentary expectations.
Five typical customer pain points
Missing invoice: VAT business accounting need
Currency receipt: confirmation email ≠ bank statement
Refund FX drift: amount refunded ≠ paid
Currency refund: refunded in EUR vs paid in USD
Reconciliation: accountant requests PDF in the exact currency
Shopify records presentment_currency and presentment_total on each Markets order (Shopify, Markets pricing 2026). Shopify refunds are processed in the order's presentment currency (Shopify, refunds 2026). Stripe notes that the issuing bank may convert upon final credit (Stripe, multi-currency 2026).
Angle #452 vs neighboring content
Displayed currency #393: checkout price vs charge error. #452 = post-order receipt invoice refund.
Refund status #370: bank pending delay. #452 = refund currency amount explain.
Partial #368: partial amount policy. #452 = currency layer on partial or full.
International #100: global view language delivery. #452 = documents refund currency.
Bot #453: future automation FX refund. #452 = agent playbook.
DTC Markets Example
CA/UK/US/EU fashion brand, 68 mcur tickets/month, of which 41% relate to invoice receipt, 35% to refund FX. Without MCUR-SUP: mcur_fcr 59%, FX refund chargebacks 12/month. After playbook: mcur_ticket_rate -46%, mcur_fcr 83%, mcur_csat 4.4/5.
Post-order not pre-checkout
Display charge mismatch pre-pay → route #393 FX-DISP. Receipt invoice refund post-pay → MCUR-FLOW #452.
B2B accounting seasonality
Q4 invoice request spike: pre-scale mcur_invoice_sla capacity and finance queue before year-end closing.
Black Friday cross-border spike
Pre-load MCUR-FX-01 macros and finance queue capacity before BFCM international order wave.
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
How does MCUR-SUP differ from CUR-DISP #393 and REF-STAT #370?
Multi-currency documents, checkout display error, and pending refund status: three distinct support layers.
Scenario → process matrix
#452 MCUR-FLOW: receipt, invoice, refund FX explain, PDF resend
#393 FX-DISP: displayed price vs purchase charge, Markets bug
#370 REF-STAT: refund initiated? bank pending delay
#369 REF-EXP: expired card routing
#379 INT-RET: international logistics return
Four MCUR-TYPEs
mcur_document: receipt invoice PDF resend
mcur_refund_fx: currency amount refund explain
mcur_reconcile: accounting bank statement match
mcur_vat_invoice: intra-EU B2B VAT invoice
Multi-currency customer service stack
Shopify order presentment fields, Sufio/Order Printer Pro invoice app, MCUR-MAP refund FX copy, Gorgias tags mcur_*, Klaviyo resend receipt template.
Promise #452
MCUR-SUP policy, MCUR-MAP matrix, 12 mcur_* typologies, MCUR-FLOW flow, MCUR-* macros, mcur_* KPI.
Presentment vs settlement
Presentment = customer currency checkout. Settlement = merchant account payout currency. MCUR-FLOW cites presentment to client, settlement internal finance only.
Shopify Markets order fields
MF-4 reads presentment_money shop_money separately. Client comms presentment only per MCUR-SUP rule 1.
Which mcur_* typologies should be mapped?
Twelve multi-currency post-order ticket typologies for consistent routing.
Twelve mcur scenarios
mcur_receipt_resend: resend PDF email confirmation
mcur_receipt_wrong_currency: currency received ≠ customer expectation
mcur_invoice_request: invoice request for accounting
mcur_invoice_vat: intra-EU B2B VAT number
mcur_invoice_currency: specific currency invoice requested
mcur_refund_amount_gap: refund amount ≠ paid amount received
mcur_refund_fx_drift: rate drift purchase vs refund D+30
mcur_refund_wrong_currency: refund currency ≠ presentment order
mcur_statement_reconcile: matching accounting statement
mcur_accounting_export: multi-currency company CSV export
mcur_paypal_wallet_fx: PayPal Shop Pay conversion refund
mcur_route_393: display error pre-order not document
Helpdesk tags
mcur, mcur_invoice, mcur_receipt, mcur_refund_fx, mcur_vat, mcur_resolved. Distinct currency (#393), ref_stat (#370).
MF-1 intake data
order_id, presentment_currency, presentment_total, refund_transactions[], customer VAT number if B2B, masked PAN statement screenshot, invoice app status.
Prioritization
P1: mcur_refund_wrong_currency bug verify. P2: mcur_invoice_request, mcur_refund_fx_drift. P3: mcur_receipt_resend FAQ, mcur_accounting_export.
Mining mcur verbatims
90 days export for "invoice", "receipt", "invoice", "refunded less", "currency", "CAD USD EUR", "accounting". Distinct "checkout displayed price" → #393.
P1 wrong currency refund
MF-4 refund transaction currency ≠ presentment: finance re-refund SLA 24 h mandatory escalation path.
Which MCUR-MAP matrix should be documented?
The MCUR-MAP multi-currency matrix lists the refund policy, invoice app, FX copy, and SLA documents.
MCUR-MAP Columns
market_id: CA, UK, EU, US Shopify Markets
presentment_currency: CAD, GBP, EUR, USD
invoice_app: Sufio, native, Order Printer Pro
vat_rules: B2B reverse charge, OSS, none
refund_currency_rule: always presentment, never convert
fx_drift_disclaimer: bank conversion standard copy
receipt_resend_sla: 24 h email + PDF link
accounting_contact: finance@ for export requests
Example CA market mcur_refund_fx
presentment CAD 120 $, refund CAD 120 $ Shopify, statement USD 89 $ bank FX: fx_drift_disclaimer cites bank conversion not merchant shortchange.
Example EU B2B mcur_invoice_vat
vat_rules reverse charge valid VAT ID, invoice_app Sufio generate, SLA 48 h with presentment EUR order total.
Publication /pages/multi-currency-orders
FAQ MCUR-MAP: currency receipt, invoice request, refund FX drift, difference #393 display error.
Refund always presentment
Shopify rule: refund in order presentment_currency. MCUR-MAP refund_currency_rule documents no manual EUR refund on USD order exception policy.
Cross-link partial #368
Partial refund amount in presentment: MCUR-REFUND-01 cites presentment_total and partial line from Shopify refund API.
Order Printer PDF template
Template must show presentment_currency prominently. MCUR-RCPT-01 links Order Printer PDF not settlement internal.
How to write the MCUR-SUP policy in eight rules?
The MCUR-SUP multi-currency policy governs documents, refund FX explanation, and finance escalation.
Eight MCUR-SUP rules
Presentment grounded MF-4: cite order presentment_currency total before explain
Refund presentment only: refund_currency_rule no manual cross-currency
FX drift disclaimer: bank conversion MCUR-MAP before admitting merchant fault
Invoice via app SLA: invoice_app workflow not agent invent PDF
VAT validate B2B: VIES check VAT ID before reverse charge invoice
Route display #393: pre-pay charge mismatch not MCUR document
Route status #370: pending only no amount dispute → REF-STAT
Log finance escalations: MF-8 accounting_export tag finance queue
No refund delta FX goodwill
MCUR-SUP default: explain FX drift not compensate bank rate unless Markets misconfiguration proven #393 bug tier N3.
Invoice SLA
mcur_invoice_request P2: MCUR-INV-01 within receipt_resend_sla 24-48 h via invoice_app generate resend.
Wrong currency refund bug
mcur_refund_wrong_currency P1: MF-4 verify refund transaction currency = presentment. If mismatch → finance + re-refund within 24 h.
VIES validation gate
MCUR-SUP rule 5: invalid VAT ID → standard B2C invoice with VAT not reverse charge promise.
How to apply the eight-step MCUR-FLOW?
The MCUR-FLOW framework structures post-order multi-currency ticket processing.
Eight steps MF-1 to MF-8
MF-1 Intake: order_id, document type, refund claim if any
MF-2 Classifier mcur_*: typology section 3, route #393 if pre-pay display
MF-3 Match MCUR-MAP: market refund rule invoice app FX copy
MF-4 Read order Shopify: presentment, transactions, refunds[], invoice status
MF-5 Explain: macro MCUR-* grounded MF-4
MF-6 Decide: resend doc | generate invoice | explain FX | escalate finance bug
MF-7 Execute: resend email, Sufio invoice, note order, re-refund if bug
MF-8 Document: mcur_action, presentment cited, finance_flag Y/N
MF-6 mcur_refund_fx_drift
Compare presentment paid vs presentment refunded Shopify equal. MCUR-FX-01 explain bank conversion fx_drift_disclaimer. Link #370 if pending not received.
MF-6 mcur_invoice_vat
Collect VAT ID, VIES validate, MCUR-INV-VAT-01 generate via invoice_app presentment currency order.
MF-6 mcur_receipt_resend
MCUR-RCPT-01 resend Shopify order confirmation + PDF link Order Printer if configured.
MF-2 route #370 only pending
Client asks "where is refund" no amount dispute → REF-STAT handoff with presentment context pre-filled.
MF-7 re-refund bug
Verified wrong currency refund transaction: finance executes correct presentment refund + note order chargeback prevention.
MF-4 refund transaction parse
Read refunds[].amount presentment_currency from Shopify Admin API before MCUR-FX-01 or bug escalation.
Which MCUR-* macros and touchpoints should be configured?
Eight multi-currency multi-device agent macros and post-purchase touchpoints.
MCUR-RCPT-01 (resent receipt)
« Order #[X]: [presentment_total] [presentment_currency]. Confirmation resent to [email]. PDF: [link]. Order currency = Shopify billed currency. »
MCUR-INV-01 (standard invoice)
« Invoice #[X]: [presentment_total] [presentment_currency] within 48 hours to [email]. VAT number received: [VAT] validated. »
MCUR-FX-01 (refund FX drift)
« Shopify refund: [refund_amount] [presentment_currency] (= presentment amount paid). Your bank may convert on credit: [fx_drift_disclaimer]. Statement USD/EUR conversion = issuing bank. »
MCUR-REFUND-01 (refund presentment confirm)
« Refund initiated [date]: [amount] [presentment_currency]. Status: [pending/success]. Bank processing time 5-10 business days: [link #370]. »
MCUR-RECON-01 (accounting reconciliation)
« Presentment order [$120 CAD]. Internal merchant settlement [EUR] ≠ your statement if bank converts. Accounting documents: [presentment_currency] invoice attached. »
MCUR-ROUTE-393 (display error)
« Price discrepancy checkout vs debit purchase: [link FX-DISP #393]. Post-order documents: continuing MCUR-FLOW receipt/invoice. »
Touchpoints
Order status page "Download invoice" link
/pages/multi-currency-orders FAQ MCUR-MAP
Post-purchase email footer presentment_currency note
Helpdesk snippet MCUR-FX-01 on refund FX keywords
Finance queue tag mcur_accounting_export
MCUR-PAYPAL-01 (wallet FX)
« PayPal internal conversion possible. Shopify refund [presentment]. PayPal balance shown may differ according to PayPal wallet settings. »
Helpdesk auto-tag mcur_refund_fx
Keywords refund less currency CAD USD → queue mcur with MCUR-FX-01 snippet pre-loaded.
Which PayPal, B2B, and international return cases should be processed?
Special multi-currency cases require MCUR-MAP extensions and routing neighbors.
PayPal Shop Pay wallet
mcur_paypal_wallet_fx : MCUR-PAYPAL-01 + presentment refund cite. Handoff PayPal support if wallet hold not merchant.
B2B VAT intra-EU
mcur_invoice_vat : VIES validation mandatory. Reverse charge note on invoice. Invalid VAT → standard VAT invoice presentment.
International return + refund
Logistics INT-RET #379. Refund FX layer MCUR-FX-01 after return received. Both tags on ticket.
Partial refund #368
Partial in presentment : MCUR-REFUND-01 + partial amount from PART-REF #368 note Shopify.
Store credit vs refund
Client wants refund CAD not store credit EUR : cite avoir vs remboursement policy presentment.
Markets misconfig refund goodwill
Proven #393 bug double conversion : finance N3 delta goodwill documented separate from normal FX drift.
Enterprise accounting export
mcur_accounting_export : route finance@ MCUR-MAP accounting_contact. Not agent CSV manual export without policy.
Shop Pay installment FX
Installment refund presentment same rules. Handoff paiement fractionné if BNPL sync dispute.
Which KPIs should be measured?
Multi-currency support KPIs link SLA documents, refund FX resolution, and chargebacks.
Eight key metrics
mcur_ticket_rate: mcur tickets / 100 international orders
mcur_fcr: resolved at 1st contact / mcur tickets
mcur_invoice_sla: invoices within SLA / requests
mcur_fx_explain_resolution: FX drift explained no escalation / mcur_refund_fx
mcur_refund_bug_rate: wrong currency refunds / total refunds
mcur_chargeback_fx: currency-related chargebacks / month
mcur_route_393_rate: misclassified display vs document
mcur_csat: satisfaction tag mcur_resolved
DTC Markets Benchmark
mcur_fcr 78-85%, mcur_invoice_sla > 95%, mcur_fx_explain_resolution > 88%, mcur_chargeback_fx -40-55% post MCUR-SUP, mcur_csat > 4.2/5.
Monthly dashboard
Market breakdown UK EU revenue, typology invoice vs refund FX, refund bug count, route accuracy #393 #370.
Finance crossover
Align mcur_refund_bug_rate with Shopify payout reconciliation finance monthly review.
mcur_invoice_sla tracking
Timestamp invoice request tag → PDF sent. Target 97%+ within MCUR-MAP receipt_resend_sla window.
Which anti-patterns should be avoided on multi-currency tickets?
Twelve multi-currency support anti-patterns to banish.
1. Refund cross-currency manual
Rule 2 presentment only. EUR refund on USD order breaks reconciliation.
2. Compensate normal FX drift
Rule 3 explain bank not shortchange unless #393 bug proven.
3. Invent invoice PDF
Rule 4 invoice_app generate only.
4. Confondre display #393
Rule 6 pre-pay charge → FX-DISP not MCUR receipt.
5. Skip presentment cite
Rule 1 MF-4 before any amount explain.
6. Promise refund EUR on CAD order
Client preference ≠ policy. MCUR-FX-01 presentment rule.
7. VAT invoice without validation
Rule 5 VIES mandatory B2B reverse charge.
8. Route pending to FX dispute
Rule 7 #370 if pending only no amount gap.
9. Settlement currency to client
Internal payout EUR confuses client. Presentment only external comms.
10. Ignore refund wrong currency bug
P1 re-refund within 24 h verified mismatch.
11. Generic refund macro no currency
MCUR-REFUND-01 always presentment_currency amount.
12. Agent manual accounting export
Rule 8 finance queue mcur_accounting_export.
13. Mix REF-STAT and MCUR-FX
Error: MCUR-FX on pending not received. Route #370 first if refund not credited bank yet.
How does Qstomy help with receiving invoices and handling multi-currency refunds?
Qstomy on Shopify runs tier 1 mcur: MF-4 presentment read, MCUR-FX-01 refund drift explain, MCUR-RCPT-01 resend guide, MCUR-INV-01 invoice steps, route #393 display vs #370 pending, handoff agents #452 complex VAT accounting.
Qstomy mcur Capabilities
mcur_order_lookup: presentment transactions refunds
mcur_fx_template: MCUR-FX-01 auto grounded
mcur_receipt_resend_guide: MCUR-RCPT steps
mcur_route_393_370: display vs pending disambiguation
mcur_handoff_finance: bug wrong currency pre-fill
mcur_map_rag: MCUR-MAP fx_drift disclaimer
Pipeline #393 #452 #453
#393 display checkout errors. #452 post-order documents refund. #453 bot FX refund automation tier 1 deflect.
Encrypted DTC Scenario
Markets 4 regions, 68 mcur tickets/month, mcur_fcr 59% baseline.
After MCUR-SUP + Qstomy: mcur_ticket_rate -44%, mcur_fx_explain_resolution 91%, mcur_invoice_sla 97%, mcur_chargeback_fx -52%, mcur_csat 4.5/5.
Explore customer support and request a demo.
Continuity bot #453
MCUR-MAP + MCUR-FX-01 corpus sync bot multi-currency refunds pre-launch #453.
Weekly mcur transcript audit
Scan cross-currency refund promises count zero. Presentment cite rate 100% on amount macros.
What checklist is needed to deploy MCUR-SUP?
MCUR-SUP Checklist (12 steps)
Inventory markets presentment currencies % international orders
Document MCUR-MAP per market invoice app FX copy
Draft MCUR-SUP policy 8 rules
Publish /pages/multi-currency-orders FAQ
Configure invoice app Sufio or Order Printer + VAT rules
Create MCUR-* macros distinct FX-DISP #393
Train agents MCUR-FLOW 45 min (MF-4 presentment, route #393 #370)
mcur_* tags + dashboard KPI section 9
Finance queue mcur_accounting_export + refund bug SLA
Tests 8 scenarios: receipt resend, invoice VAT, FX drift, wrong refund bug, partial #368, PayPal, route 393, pending 370
Order status page invoice link deploy
Sync MCUR-MAP → bot #453 future corpus
In short
#452 = refund invoice receipt, not checkout display #393
Presentment always: order currency = refund document
FX drift: bank converts, MCUR-FX-01 explain
Invoice app: no hand-made agent PDFs
KPI mcur_fx_explain_resolution: target > 85 %
FAQ
Difference #393?
#393 price display error vs purchase debit. #452 post-order refund invoice receipt.
Refunded less than paid?
MF-4 compares presentment paid vs refunded. If equal → MCUR-FX-01 bank conversion. If bug → re-refund P1.
Invoice in another currency?
Invoice in order presentment_currency. No manual conversion except policy finance exception.
Invoice VAT number?
MCUR-INV-VAT-01 VIES validate + reverse charge rules MCUR-MAP.
Bot #453 vs agents #452?
#453 bot FX refund explain. #452 playbook documents VAT accounting execute.
Going further
Expired card (#369)
This week: document MCUR-MAP by market, publish /pages/multi-currency-orders, configure invoice app + VAT, deploy MCUR-FX-01 helpdesk snippet, train agents MF-4 presentment quote, connect dashboard mcur_refund_bug_rate.
Share this guide #452 with finance and support: a grounded presentment macro is worth ten "incomplete refund" chargebacks, a manual cross-currency refund is worth an impossible accounting reconciliation and zero trust in Markets.
Go-live test matrix
8 scenarios sign-off: receipt resend, B2B VAT invoice, FX drift explain, wrong refund bug, partial presentment, PayPal wallet, route 393, handoff 370 pending.
Enzo
July 1, 2026
