Evidence and data quality
Refund Evidence: Which Transaction Records Show Money Was Actually Returned?
Refund evidence should show a traceable payment credit linked to the challenged transaction, with the amount, currency, destination, dates, and actual provider status. A refund request, approval message, or internal accounting entry can explain intent but does not by itself establish that the payment provider completed the credit.
Prepare the exhibit around the actual transaction record. Keep merchant initiation, provider completion, and customer bank posting distinct. The merchant may have reliable evidence of the first two without being able to confirm exactly how the credit appears in the customer’s account.
Separate refund intent from payment events
List the relevant records and classify what each represents. A support promise is a commitment. A refund action log can show an instruction. A provider transaction shows the status of that instruction. A customer acknowledgment may confirm visible receipt, but its absence does not automatically negate the provider record.
Shopify Payments documents refund processing and tracing. Shopify Payments refunds.
Use the actual status exposed by the provider. Do not convert pending or submitted into completed for a stronger caption. If the status is unclear, request verification and label the uncertainty. A payment record created on a date does not necessarily establish that the credit completed on that date.
Check whether the transaction is a refund or another event such as an authorization reversal. Both may affect what the customer sees, but they should not be mislabeled. The exhibit should describe the actual event and its relation to the original payment.
Match the credit to the original transaction
Record the original payment reference and the refund reference, then identify the provider’s link between them. Matching an amount and customer name is weaker than a direct transaction relationship. If several credits exist, show each relevant amount and status separately.
Shopify guidance includes refund-transaction evidence. Shopify response guidance.
Reconcile the refunded scope. A 30-unit credit does not prove a promised 80-unit refund was completed. If several partial credits sum to the relevant amount, show the calculation and references. Keep any unrelated goodwill credit separate so it is not accidentally counted twice.
For mixed-payment purchases, identify the actual destination of each credit. A refund to a gift balance or expressly agreed store credit is different from a credit to the card transaction. The exhibit should not imply that money returned to one destination necessarily settled a claim about another without an appropriate explanation.
Use a completed-credit exhibit template
The following reusable template organizes the facts needed to describe an actual refund record. It does not instruct staff to issue a refund.
| Field | Evidence to include |
|---|---|
| Original payment | Provider reference, amount, and currency |
| Refund transaction | Unique credit reference |
| Linkage | Provider record connecting credit to original payment |
| Refunded amount | Amount and currency of this credit |
| Destination | Verified method with limited identifying detail |
| Initiation date | Actual merchant or provider instruction time |
| Current status | Exact provider status and retrieval date |
| Completion or trace detail | Available provider-confirmed information |
| Scope | Items or agreed adjustment covered |
In a hypothetical case, the merchant promised a 90-unit refund and has three provider records: a 30-unit completed credit, a 60-unit failed attempt, and a later 60-unit completed credit. The exhibit should include the two completed amounts and explain the failed attempt where it is relevant to the chronology. Counting all three records would incorrectly imply 150 was returned.
If only the failed attempt and support promise existed, the merchant should not label the exhibit proof of completed reimbursement. The evidence must follow the actual payment state.
Make the record readable and bounded
Use a cover note stating the original transaction, relevant completed amount, and attached provider record. Explain any partial-credit sequence so the reviewer does not need to perform the reconciliation unaided. Keep the provider’s status labels visible in the underlying evidence.
Where a trace reference is available, include it with an explanation of its source and purpose. Do not invent a reference or imply every payment method uses the same tracing mechanism. If the provider cannot supply one, state the available completion evidence without suggesting a missing code proves failure.
Redact unrelated transactions and unnecessary account information. Preserve the identifiers and amounts needed to verify the credit. A large payout export can expose irrelevant financial data while still failing to show the original-payment relationship clearly.
Check the exhibit against the response narrative before submission. The narrative should not claim the customer saw the credit on a particular date unless that is separately supported. It should not call a requested refund completed or a store-credit balance a card refund.
Supply the records through the available Shopify or provider route and retain the submitted version. This preparation establishes what the payment evidence actually shows; it does not independently decide whether a credit was due or whether the formal dispute will close. Those questions need the actual claim and provider process.
Keep the dispute reason, amount and response deadline visible in Lower Chargeback while you prepare your response in Shopify or with your provider.
Related reading in this collection:
- Link a Chargeback to the Correct Shopify Order and Payment Record
- Credit Not Processed Chargebacks: Show Whether a Refund Was Due or Completed
- Find and Explain 3D Secure Authentication Records in Dispute Evidence