Gift card chargebacks can involve two different value transfers: the purchase of the gift card and the later redemption of stored value. The merchant should preserve both. A delivery email proves only that a code or card was sent; redemption records show whether the value was later used, by which merchant account/order reference, and what balance remained.
Treat physical and digital gift cards differently where the records differ. Build the case from original payment, issuance, delivery, activation, redemption, balance adjustments, refunds, and any customer report that the card was missing or compromised.
Identify the original gift-card purchase
Save order ID, amount, currency, purchaser details retained by the merchant, payment transaction ID, gift-card identifier in a masked/safe form, and whether the card was physical or digital. If multiple cards were purchased in one order, list each face value separately.
Do not publish or submit a live redemption code in a dispute packet unless the processor explicitly requires a secure form. Use masked identifiers where possible.
Prove issuance and delivery
For digital cards, retain send timestamp, destination email/account, delivery event if available, and activation. For physical cards, use fulfillment and carrier records plus activation status.
An email sent event is weaker than a verified redemption history, but it still helps establish that the merchant created and delivered the purchased instrument.
Trace redemption event by event
List each redemption date, amount, order or location, and remaining balance. If the card was partially used, do not summarize it as simply 'redeemed.' Show the ledger.
Where the gift card funded a later purchase, link that purchase to its own fulfillment or service record if relevant to the live dispute.
Handle theft or unauthorized redemption carefully
A customer may acknowledge buying the card but claim someone else used it. Redemption records can show where and when value moved, but they do not automatically prove who controlled the code.
Avoid overclaiming IP, device, or account signals as identity proof. Present them only as corroboration if lawfully retained and relevant.
Reconcile refunds and balance restoration
Check whether support replaced the card, restored balance, refunded the original payment, or issued another credit. Keep each remedy separate with amount and timestamp.
A merchant can lose twice if it restores value and also refunds the original card without linking the cases.
Improve gift-card controls
Flag high-value, rapid redemption, repeated failed delivery, or unusual purchase/redemption patterns according to the merchant's risk tolerance without blocking legitimate gifts by default.
Most importantly, keep a durable issuance-and-redemption ledger so future disputes can be reconstructed without exposing the gift card secret itself.
Example: a digital gift card is delivered and redeemed twice
A $100 digital gift card is emailed to the address supplied at checkout and later redeemed in two orders totaling $100. Those records can establish delivery and use of the gift-card value, but they do not prove the named cardholder personally controlled the email account or made the redemptions.
Link purchase, delivery event, activation, redemption timestamps, related order IDs, and remaining balance using safe identifiers. Avoid putting the full gift-card code in a dispute packet. Use redemption as corroborating transaction evidence, not as a shortcut to an identity claim.
Protect sensitive gift-card data in the evidence packet
Gift-card systems often expose codes or tokens that function like stored value. Redact or omit the full credential and use safe last characters, internal gift-card ID, order ID, redemption order IDs, and timestamps instead. The reviewer needs the lifecycle, not a reusable secret.
Investigate suspicious redemption separately from the chargeback response. If the code was compromised after delivery, redemption records may show value was consumed without showing who consumed it, and the merchant should avoid overstating what those logs establish.
Protect the gift-card audit trail without exposing redeemable secrets
A gift-card dispute begins with two assets: the original payment and the stored-value instrument created from it. Link the purchase transaction to the gift-card ID or token in a way that does not expose the full redeemable code. Preserve amount, purchase date, delivery method, recipient information where appropriate, and activation status. If the card was emailed, distinguish message sent from successful access where the system can support that distinction.
Trace redemption event by event. Record date, order, amount redeemed, channel, and remaining balance. For partial use, show the running balance. If the gift card was transferred or used by multiple orders, avoid claiming that redemption identifies the cardholder personally. The evidence establishes use of the stored-value instrument in the merchant's system, not necessarily the identity of the person who entered the code.
Unauthorized-redemption claims need a security review. Check whether the code was exposed in email, support logs, screenshots, or account pages; whether the customer reported theft before redemption; and whether the merchant can freeze or restore value under its policy. Do not include the full gift-card code in a dispute packet. Redact or mask credentials so evidence cannot itself become a way to steal remaining value.
Reconcile remedies carefully. If the merchant refunds the original card and also restores gift-card balance, it may create double compensation unless that is intentional. If a redeemed balance was reversed, show the adjustment. Track gift-card disputes by delivery channel, fraud pattern, code exposure, and redemption timing. Stored-value products need their own fraud and evidence controls because payment, delivery, and consumption occur in separate systems.
Separate gift-card purchaser, recipient, and redeemer roles
Gift cards often involve three people: the purchaser who funded the card, the intended recipient, and the person who later redeems it. Preserve those roles where the product collects them, but do not assume they are the same person. A redemption by a recipient can be legitimate even though the purchaser's account never logs in again.
This distinction is important in fraud narratives. The merchant can prove issuance, delivery, and redemption events without claiming the redeemer was the cardholder. Role-aware records make the transaction story clearer and reduce overclaiming.
Preserve delivery evidence for physical gift cards separately from digital codes
Physical gift cards need a shipping or pickup trail in addition to activation and redemption, while digital cards need email/account delivery evidence. Do not use a redemption record to skip the delivery question if the dispute is that the purchaser never received the gift card. Conversely, a delivered physical card can later be stolen or redeemed by another person. Keeping delivery and redemption as separate stages makes the evidence fit both product types.
Gift card cases should separate the purchase transaction from the later stored-value lifecycle. Preserve issuance, delivery method, recipient information when available, activation, redemption events, remaining balance, and any transfer or replacement. For digital cards, save the delivery event without assuming email delivery proves the purchaser used the code. For physical cards, preserve shipment and activation separately. If the card was fully redeemed before the dispute, identify when and where that happened but avoid presenting redemption as conclusive identity proof. This layered record helps the reviewer see whether the merchant delivered the purchased value and also helps fraud teams detect whether abuse occurred at purchase, delivery, account access, or redemption.
VERIFY CURRENT RULES
Primary references
Processor interfaces, reason-code mappings, filing windows, and network rules can change. Check the active dispute notice and current official documentation before submitting.