Guide Β· For sellers and merchants

Gift Order Disputes: The Merchant Playbook


For sellers and merchants: a gift you shipped is being disputed by someone who did not buy it. The trap is identity β€” buyer, recipient, and cardholder are three different people, and the evidence pack differs for each. This guide routes by who is disputing and what the dispute claims, builds the right pack, states the refund-to-buyer-only rule, and names the traps that lose gift disputes. No outcome is promised: the card issuer decides every case.

By Muhammad Umer, founder of Chargeback Clock Β· Updated November 2026

Build your gift-order evidence pack first

Answer who is disputing, what the dispute claims, and what evidence you have β€” the pack builds itself.

The identity trap

One order, three people, three different disputes


Most evidence checklists assume the person who paid, the person who ordered, and the person who received are the same person. A gift order breaks that assumption in the open: the buyer pays, the buyer names a recipient, the parcel goes to the recipient's address. When a dispute arrives on that order, the first question is never "where is the tracking?" β€” it is "who is disputing, and what are they actually claiming?" A buyer disputing their own gift order asks why billing and shipping differ. A recipient complaining asks about a parcel they never paid for. A cardholder disputing asks whether they approved a charge for a parcel that went to a third person. Each question needs a different pack, and filing the wrong pack wastes the response window your processor gave you. Route first, build second β€” that order is the whole method of this guide, and of the Gift-Order Dispute Shield that builds the pack for you.

The buyer disputes: explain the gift, prove authorization

When the buyer disputes, the reviewer sees a billing address and a shipping address that do not match, and a ship-to name that is not the buyer's. Stripe's dispute guidance names this exact shape: if a customer provides a ship-to name that differs from their own, for example a gift purchase, be prepared to provide documentation explaining why they are different β€” and a ship-to address that does not match the verified billing address is common for gifts and an additional dispute risk. Your pack therefore leads with the explanation, not the tracking: the gift message in the buyer's own words, the order record showing the buyer chose the recipient address, and a one-paragraph cover note stating plainly that this was a gift, the buyer named the recipient, and the buyer chose that address. Then the authorization evidence: AVS result, CVC result, 3DS outcome if checkout used it, checkout IP, and any prior order history on the same card or account. Then the delivery evidence: carrier tracking with the delivered scan showing the full delivery address. The order matters β€” explanation first, authorization second, delivery third β€” because the reviewer reads the pack in that order and the explanation is what turns a mismatch into a gift.

The recipient complains: the refund goes to the buyer, never the recipient

When the recipient contacts you β€” confused by a parcel, unhappy with it, or asking for money back β€” the rule is simple and must be stated before anything else is discussed: the recipient did not pay, so the recipient cannot be refunded. Stripe's refunds guidance says refunds can only be sent back to the original payment method used in a charge, and cannot be sent to a different destination such as another card or bank account. So the conversation routes to the buyer: thank the recipient, explain the order was placed and paid for by the buyer as a gift, and ask them to raise return or refund questions with the buyer. Do not promise the recipient a refund, do not send the recipient money by another route, and keep a copy of the exchange. If a refund is then agreed with the buyer, it goes to the buyer's original payment method, coordinated through your processor. The recipient script in the shield's result covers this exchange word for word.

The cardholder disputes: authorization evidence is the core

The cardholder dispute is the hardest version of this trap, and the one where merchants most often file the wrong pack. The cardholder says they did not authorize the charge. The parcel went to a third person. A delivery signature proves the parcel arrived β€” it does not prove the cardholder approved the charge, and a reviewer deciding an unauthorized claim will read it exactly that way. So the core of this pack is authorization: AVS matches, CVC confirmations, 3DS authentication, a checkout IP address matching the verified billing address, and anything linking the cardholder to the buyer β€” prior clean order history on the same card or account, an account whose details match, a buyer message naming the recipient or discussing the gift. Delivery proof still goes in, but as supporting evidence, behind the authorization evidence, with the cover note tying the two together: the cardholder authorized the charge (state the results), the buyer chose the recipient address as a gift, and the parcel was delivered to that address. If you have no authorization evidence at all, say so in the cover note rather than padding the pack with delivery pages β€” a thin honest pack beats a thick irrelevant one.

When you do not know who is disputing: identify first, file second

Sometimes the notice does not make the disputer clear. Do not guess. Read the dispute notice your processor sent: it states the reason code and usually the party. If it still does not make it clear, ask your processor before you submit β€” a buyer pack filed on a cardholder dispute answers the wrong question. If the deadline is close and the identity is still unclear, file the pack you can defend β€” the order record, the gift evidence, and the carrier record β€” and say plainly in the cover note what is still unclear. An honest gap stated in the cover note is stronger than a guessed identity discovered by the reviewer.

The cover note: one paragraph, four facts, no adjectives

Every pack opens with a one-paragraph cover note, and the cover note follows the same shape whatever the disputer: who placed the order, who paid, who the gift was for, where it was shipped, and what the carrier record shows. Example shape, with your own facts substituted: "Order [number]: [buyer name] placed this order on [date] and paid with [card type ending]. The order was a gift for [recipient name], shipped to [full recipient address] as chosen by the buyer at checkout. The gift message read: [message]. Carrier [name], tracking [number], shows delivery to that address on [date]. AVS [result], CVC [result], 3DS [result]." Keep it to facts on the order record. Do not claim intent you cannot show, do not invent a gift message the buyer never wrote, and do not describe the buyer or recipient in adjectives β€” the reviewer trusts records, not character references.

The refund-to-buyer-only rule, in full

Refunds can only go back to the original payment method used in a charge. That sentence, from Stripe's refunds guidance, decides three common gift-dispute mistakes at once. First, never refund the recipient: the recipient did not pay, and a refund to the recipient is a refund to a different destination, which the rule forbids. Second, never refund a different card the buyer nominates afterwards: the refund goes to the card that paid, and if that card has been replaced, the issuer routes it β€” that is the issuer's job, not a reason to pick another destination. Third, coordinate any refund through your processor while a chargeback is open: refunding separately risks paying twice, once as a refund and once as a lost chargeback amount. If you decide to refund rather than fight, refund the buyer, through the original payment method, through your processor, and keep the record.

Submit through your processor, and read its notice first

Representment is a submission through your acquirer or processor, which forwards it to the card network and the issuer. It is not a message to the cardholder's bank, and it is not a conversation with the cardholder. Your processor's notice states the reason code and the response deadline, and that deadline is the binding one β€” processor deadlines can be shorter than network windows, so this guide states no day-count: read your own notice and diary the deadline first, then work backwards. Submit in the processor dashboard, confirm receipt, and keep a timestamped copy of everything you sent. Once a chargeback has posted, do not try to settle it by contacting the cardholder directly about it, and never pressure anyone to withdraw a dispute. Ordinary order communication with the buyer β€” a delivery question, a gift-note correction β€” is a different thing from dispute contact; when in doubt about contact, follow your processor's notice. And the limit that belongs on every gift-dispute result: the issuer decides the case. A complete pack improves the submission; it does not decide it.

Traps that lose gift disputes

Refunding the recipient, because the recipient is the person complaining β€” the refund rule forbids it, and the money is then gone twice over if the chargeback also lands. Filing delivery proof on an authorization claim, because delivery proof is the evidence you have ready β€” it answers the wrong question. Filing authorization proof on a not-received claim, for the same reason in reverse. Inventing a gift explanation the order record does not support β€” a reviewer who catches one invented line discounts the rest of the pack. Contacting the cardholder directly about a posted chargeback, or pressuring anyone to withdraw β€” the formal route is the processor submission. And guessing the disputer when the notice is unclear, instead of asking the processor β€” a wrong-identity pack is a wasted response window. Gift orders cluster around holidays, which is when this trap appears most; no holiday statistic is claimed here, because none was verified for this guide.

Build your pack now

Answer who is disputing, what the dispute claims, and which evidence you have β€” gift message, separate ship-to address, delivery proof, order notes β€” and the shield builds the evidence pack, the missing-items list, and the next steps for your exact case.

Open the Gift-Order Dispute Shield

Sources (verified November 4, 2026): Stripe dispute evidence guidance β€” if a customer provides a ship-to name that differs from their own (for example, a gift purchase), be prepared to provide documentation explaining why they are different; a ship-to address that does not match the verified billing address is common for gifts and is an additional dispute risk; for a fraudulent dispute, prove the legitimate cardholder was aware of and authorized the transaction (AVS matches, CVC confirmations, 3DS authentication, IP address matching the verified billing address); for a merchandise purchase, provide proof of shipment and delivery that includes the full delivery address, not just city and postal code; Stripe does not decide the outcome of a dispute β€” the card issuer ultimately reviews the case and makes the final decision. Stripe refunds guidance β€” refunds can only be sent back to the original payment method used in a charge; you cannot send a refund to a different destination, such as another card or bank account. Representment practice β€” a chargeback response is submitted through your acquirer or processor, not directly to the issuer, and the processor's notice states the response deadline. Your processor, the card network rules, and your account agreement are the final word.

General information only β€” not legal advice. This guide gives a general read of gift-order disputes against processor and network guidance as checked on November 4, 2026. It does not predict whether an issuer will rule in your favour. Your processor's notice and your account agreement control your specific case.

← Back to homepage