E-commerce
July 1, 2026
"My return is accepted, when will the credit appear on my gift card?" "The refund is on a new card, not the one I used." "I wanted cash, not a gift card credit." Three tickets where a poorly explained gift card refund generates mistrust and financial escalation.
The e-commerce gift card refund support covers post-return credit, balance delay, new card vs. original card, and cash vs. gift card choice. Distinct from general refund (REFUND): here, credit is refunded to a store gift card.
This guide #993 deploys policy GCREFUND-SUP, flow GR-1 to GR-8, and matrix GCREFUND-MAP. Partner of the future CS gift card refund bot (#994).
Summary
Why do gift card refunds generate tickets?
The customer returns an item paid for with a gift card or credit card. The store credits the refund to a gift card according to policy. Without GCREFUND-MAP, the agent does not state the balance processing time, confuses a new card with the original card credit, or promises cash contrary to policy.
Five typical gift card refund points of friction
Balance processing time: customer does not see the credit after the return is accepted
New vs original: refund code ≠ card used for purchase
Cash option denied: customer wanted a bank refund
Partial refund: amount credited ≠ expected return amount
Balance not found: where to check balance post-refund
Example DTC active returns fashion
Fashion brand default gift card refund, 9 gcref_ tickets/month. After GCREFUND-MAP: gcref_resolution_rate 84%, gcref_delay_cite_rate +28% in 5 weeks.
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
GCREFUND #993 vs REFUND, GCPLUS #991, GIFTCARD, STORECREDIT and bot #994
Seven gift card refund contents, seven distinct angles.
Quick Matrix
#993 GCREFUND: refund credited to gift card delay balance new card
REFUND: general cash refund distinct from gift card credit
GCPLUS #991: split refund on existing mixed order distinct from new return credit
GIFTCARD: gift card usage balance expiration distinct from post-return refund
STORECREDIT: store credit distinct from purchased gift card
Bot #994: tier 1 bot delay balance widget
GCPLUS = split refund on already placed mixed order. #993 = new gift card credit issued after return.
Promise #993
Policy GCREFUND-SUP, tree GCREFUND-GATE, 8 macros, gift card refund registry, KPI gcref_resolution_rate.
Which gcref_* typologies to classify?
Action-oriented classifier: delay ≠ new card ≠ cash choice ≠ partial ≠ balance.
Eight GCREFUND-MAP typologies
gcref_refund_to_card: refund credited to gift card policy
gcref_delay_status: delay of balance appearance after accepted return
gcref_new_vs_original: new card issued vs original card credit
gcref_partial_refund: partial refund of the amount credited to the card
gcref_balance_check: check balance after gift card refund
gcref_cash_vs_card: choice of cash refund vs gift card
gcref_return_process: return steps with gift card refund
gcref_ops_flag: ops sync policy flag for gift card refund
Tags: gcref, gift_card_refund, refund_to_card, return_credit. GCREFUND-MAP-GROUNDED: refund_to_card_policy_copy refund_delay_copy from registry only.
Policy GCREFUND-SUP: agent rules and gift card refund register
The GCREFUND-SUP policy sets gift card refund responses without inventing delays outside of the map.
Six GCREFUND-SUP Rules
GCREFUND-REGISTRY-FIRST: check GCREFUND-MAP before refund response
RETURN-VERIFY: lookup return_ref order_ref live return status
REFUND-POLICY-CITE: cite refund_to_card_policy_copy map
DELAY-CITE: cite refund_delay_copy map if delay is cited
NO-CASH-PROMISE: no cash promised if gift card only policy map
Handoff #994: brief chatbot on gift card refund widget
Minimum gift card refund registry
gcref_id: gift card refund policy line identifier
refund_to_card_policy_copy: gift card credit rules text for agents
refund_delay_copy: timeframe for balance to appear post-return map
new_card_vs_credit_copy: new card vs original credit map
partial_refund_rules_copy: partial refund to card map
cash_vs_card_choice_copy: choice of cash or gift card if applicable map
balance_check_steps_copy balance_check_url: check balance post-refund
return_process_copy staff_brief_url: gift card return and refund steps
Flow GR-1 to GR-8: gift card refund ticket processing
Eight steps: intake return lookup verify classify respond delay balance escalate log close.
Flow GR-1 to GR-8
GR-1 Intake: gcref_* intent + return_ref order_ref email quoted
GR-2 Return lookup: RETURN-VERIFY live refund return status
GR-3 Policy lookup: GCREFUND-REGISTRY refund_to_card map
GR-4 Gift card verify: gift card issued credit balance admin live
GR-5 Classify: delay newcard partial balance cash choice
GR-6 Respond: macro GCREFUND grounded refund policy delay
GR-7 Escalate: ops finance if cash demand or dispute amount
GR-8 Log: KPI gcref + brief registry correction
SLA: gcref_delay_status refund_delay_copy provided in one interaction if map exists.
Eight GCREFUND-* macros ready to paste
Gift card refund macros without invented delay outside the registry.
GCREFUND-* Library
GCREFUND-POLICY-01: "Gift card refund: {{refund_to_card_policy_copy map}}."
GCREFUND-DELAY-01: "Balance delay: {{refund_delay_copy map}}. Return {{return_ref}} status {{statut}}."
GCREFUND-NEWCARD-01: "Refund card: {{new_card_vs_credit_copy map}}."
GCREFUND-PARTIAL-01: "Partial refund: {{partial_refund_rules_copy map}}. Amount {{montant}}."
GCREFUND-BALANCE-01: "Check balance: {{balance_check_steps_copy map}}. {{balance_check_url}}."
GCREFUND-CHOICE-01: "Refund choice: {{cash_vs_card_choice_copy map}}."
GCREFUND-RETURN-01: "Return process: {{return_process_copy map}}."
GCREFUND-DONE: "Ticket summary {{id}}. Resolution: {{résolution}}."
GCREFUND-GATE tree and support finance coordination
Decision tree before promising ad hoc cash or invented delay.
GCREFUND-GATE
Return or order cited? → lookup GR-2 return verify
Gift card refund policy? → POLICY-01 refund_to_card_policy
Balance delay? → DELAY-01 refund_delay_copy
New card or original? → NEWCARD-01 new_card_vs_credit
Partial amount? → PARTIAL-01 partial_refund_rules
Check balance? → BALANCE-01 balance_check_steps
Cash request? → CHOICE-01 cash_vs_card or escalate finance
Split existing mixed order? → reroute GCPLUS #991
Refund policy sync ritual Day-0
Finance publishes GCREFUND-MAP: refund_to_card_policy validated, refund_delay_copy shared with support. Bot #994 sync go-live.
KPI, QA and handoff to bot #994
Measuring GCREFUND detects poorly quoted delays and improvised cash promises.
Five GCREFUND KPIs
gcref_resolution_rate: tickets resolved without delays invented ad hoc
gcref_delay_cite_rate: % of DELAY-01 tickets with refund_delay provided
gcref_balance_cite_rate: % of BALANCE-01 tickets with balance steps provided
gcref_cash_escalate_rate: cash demand tickets routed to finance
gcref_delay_invent_violation: invented delays outside the map, target 0
Handoff #994
Export GCREFUND-MAP to bot: gcref_delay_status gcref_balance_check gcref_refund_to_card high priority. Guardrail DELAY-CITE brief #994: bot quotes refund_delay_copy refund_to_card_policy map only.
Edge cases: cash requested, store credit, mixed split, expired card
Four cases outside the standard refund flow for gift cards.
Customer demands cash refund
CHOICE-01 cash_vs_card_choice_copy. If gift card only policy: escalate to finance, no ad-hoc cash promise.
Boutique store credit confusion
STORECREDIT reroute store credit vs refund if credit is store credit, not a gift card.
Order paid with gift card + credit card returned
GCPLUS reroute #991 if split refund on existing mixed order.
Gift card expired before refund
GIFTCARD alignment gift card expiration + goodwill gesture if policy permits.
Agent training: 20 minutes GCREFUND
Module: GCREFUND-REGISTRY, distinguish REFUND GCPLUS STORECREDIT RETURN bot #994.
Exercises
Ticket A: balance delay → DELAY-01 refund_delay_copy
Ticket B: new card → NEWCARD-01 new_card_vs_credit
Ticket C: check balance → BALANCE-01 balance_check_steps
Ticket D: cash request → CHOICE-01 escalate finance
How Qstomy structures GCREFUND in your stack
Qstomy on Shopify: gcref_* route, gift card refund registry sync, POLICY DELAY BALANCE CHOICE macros, and handoff #994 delay policy grounded gate.
Three bricks
Routing: intent gift_card_refund vs refund_cash vs gcplus_split
Gift card refund registry: policy delay newcard balance choice
Bot #994: tier 1 delay balance widget
Scenario: DTC mode 9 gcref_/month tickets. Registry D-0. gcref_resolution_rate 84%, delay_cite_rate +28%.
Explore AI support and request a demo.
FAQ and GCREFUND deployment checklist
FAQ
Promise out-of-policy turnaround times?
No. DELAY-01 cites refund_delay_copy map only.
Difference with REFUND guide?
Guide = general cash refund. #993 = post-return gift card credit.
Difference with GCPLUS #991?
#991 = split refund for mixed existing orders. #993 = new gift card credit issued.
Difference with STORECREDIT?
Store credit = return credit for boutique. #993 = gift card issued or gift card credit.
Difference with #994?
#993 = agents verify escalate finance ops. #994 = bot tier 1 delay lookup widget.
GCREFUND Deployment Checklist (8 steps)
GCREFUND-SUP + GCREFUND-MAP: gift card refund registry template
refund_to_card_policy_copy: approved by finance & legal
refund_delay_copy: lookup delay documented for ops
new_card_vs_credit_copy: new card vs original shared
balance_check_url: post-refund balance page tested
cash_vs_card_choice_copy: choice documented if applicable
Sync bot #994: DELAY-CITE
20-min Training: section 10 exercises
Linking
Enzo
July 1, 2026
