Gift-Order Dispute Shield: a Gift You Shipped Is Being Disputed

The identity trap: one order, three people, three different packs

A gift order breaks the assumption most evidence checklists are built on — that the person who paid, the person who ordered, and the person who received are the same person. In a gift order they are three different people, and each dispute shape asks a different question. When the buyer disputes, the question is why the billing and shipping addresses differ, and the answer is the gift itself: the gift message, the order record showing the buyer chose the recipient address, and the authorization evidence showing the buyer approved the charge. When the recipient disputes or complains, the question is different — the recipient never paid, so the recipient cannot be refunded, and the conversation runs through the buyer. When a cardholder disputes, the question is harder still: did the cardholder approve a charge for a parcel that went to a third person? Delivery proof proves arrival, not approval, so authorization evidence — AVS, CVC, 3DS, checkout IP, prior order history — becomes the core of the pack, and delivery proof becomes supporting evidence. Filing a delivery pack on an authorization dispute, or an authorization pack on a delivery dispute, answers the wrong question and wastes the response window. That is why this tool routes first and builds second.

The gift message and the separate shipping address are the explanation

Stripe's dispute guidance states the rule plainly: 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. The gift message is that documentation in the buyer's own words: it is the one item that turns "billing and shipping do not match" from a fraud signal into a visible gift. The order record showing the separate ship-to address the buyer chose does the same work from the merchant's side. And for a not-received claim, Stripe's guidance asks for proof of shipment and delivery that includes the full delivery address, not just city and postal code — a city-and-postal-code-only record is weaker than a full-address record, so the pack insists on the full address. Gift orders cluster around holidays, which is when this trap appears most — but no holiday statistic is claimed here, because none was verified for this build.

The refund-to-buyer-only rule

The most expensive mistake in a gift dispute is refunding the wrong person. Stripe's refunds guidance says refunds can only be sent back to the original payment method used in a charge — they cannot be sent to a different destination, such as another card or bank account. That means a refund on a gift order goes to the buyer's card or account, never to the gift recipient, even if the recipient is the one complaining, and never to a different card the buyer nominates afterwards. It also means a refund must be coordinated through your processor: refunding separately while a chargeback is open risks paying twice — once as a refund, once as a lost chargeback. 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 not a message to the cardholder's bank. It is a submission through your acquirer or processor, which forwards it to the card network and the issuer, and the issuer decides the case. 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 no day-count is stated on this page: read your own notice. 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 is a different thing from dispute contact; when in doubt about contact, follow your processor's notice. And the honest limit stays on every result this tool produces: a complete pack improves the submission, it does not decide the case.

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.

← Back to homepage