# Chargeback records retention timeline | SourceX

Canonical: https://refer.sourcex.si/guides/preserve-chargeback-evidence-assembly-records
Last updated: 2026-11-04

Before a dispute platform renewal, inventory the submitted response files, the records each response file was built from, the analyst notes, and the card-issuing bank's decision, and note when each one would disappear. Links from cases to orders and tickets usually fade first, then notes and outcomes; response files and order history tend to last longest. For each record, write the system, the years covered, the documented deletion or access-end date, and who must approve keeping it. Record only dates a contract or setting confirms.

This retention timeline is part of the [chargeback evidence assembly guide](/guides/workflow-chargeback-evidence-assembly). It is for payments operations consultants whose retailer client is about to renew, renegotiate or replace its dispute platform.

## Why a renewal can quietly break the dispute history

A renewal or vendor switch tends to keep the response file and lose the context around it. The response file is a file; the context is a set of links, notes and outcome fields that live in the platform's database.

Each case is a fixed snapshot. Stripe's documentation says a retailer usually has 7 to 21 days to respond after a card dispute is created, depending on the card network, and that the card-issuing bank usually takes 60 to 75 days to decide. Stripe forwards the response to the issuing bank immediately, and the retailer cannot edit it or add files afterward. So every case has three dated parts: the claim, the evidence chosen under a deadline, and a verdict that arrives two months later. A history is only useful while all three stay attached.

## The timeline: what fades first

Retention periods are set by the retailer's contract, plan and settings, not by any general rule, so the order below is a pattern to test, not a fact about any vendor. Ask the disputes director for the real figure in each row.

| Record type | Where it usually lives | How long it tends to last | What makes it disappear | Who approves keeping it |
|---|---|---|---|---|
| Links from case to order and ticket | Dispute platform database | Only while the platform account is active | Account closure at exit | Disputes director with IT |
| Analyst notes and internal comments | Dispute platform | Same as the account | Account closure; rarely in exports | Disputes director |
| Issuer outcome stored on the case | Dispute platform and payments platform | Payments platform keeps it longer if it was recorded there | Platform closed the case before the decision arrived | Payments operations |
| Submitted response files as files | Dispute platform or payment provider dashboard | Varies by contract; sometimes exportable | Contract end with no data return clause | Disputes director and counsel |
| Order history and shipments | Order management | Years, under the retailer's own policy | The retailer's retention schedule | Operations lead and counsel |

The first two rows are the ones a renewal can erase without anyone noticing, because a bulk export usually carries response files and statuses, not the links and notes.

## An Illustrative renewal timeline

A fictional 380-person outdoor equipment retailer with six years of disputes on one platform. The dates are invented and show what to write down, not what any contract says.

| Date | Event | What it means for the history |
|---|---|---|
| January 15 | Renewal notice deadline in the current contract | Last date to negotiate data return terms |
| March 1 | Decision: switch vendors | Old platform stops receiving new cases |
| March 31 | Contract end | Account becomes read-only, per the contract |
| April 30 | End of the export window | Case links and notes not exported are gone |
| Ongoing | Order history in order management | Unaffected by the switch |

The decision date that matters is January 15, not April 30. After the notice deadline the retailer has less leverage to ask for a fuller export. The graphic shows four of the five rows stopping at April 30 unless someone with authority decides to keep them, while order history carries on in its own system.

## Inventory questions to ask before the notice date

Ask these in the order a disputes director can usually answer them:

1. **Which systems built the response files, by year?** A dedicated dispute platform, the payment provider's dashboard, an alert service, or a mix.
2. **Are submitted response files kept as files?** Or only a status that says "submitted".
3. **Is the outcome stored against the case, won and lost?** With the date, for every year.
4. **Do cases carry the order number and ticket ID?** Or only the payment provider's dispute ID. The [system map](/guides/chargeback-evidence-assembly-records-across-systems) shows which keys matter.
5. **What does the contract say at exit?** Notice date, read-only period, export format, data return clause.
6. **Is anything on legal hold?** If so, counsel decides; [litigation hold versus data destruction](/compare/litigation-hold-vs-data-destruction-wind-down) explains the difference.

Write answers, not records. Do not export, screenshot or sample cases, and do not suggest keeping records beyond what the retailer's policy and counsel authorize. Whether to preserve anything is the retailer's decision.

## Who approves, and what stays unknown

The disputes director can describe each row. Keeping records past a contract end usually needs the CFO or COO, with counsel, because it touches retention policy, customer data and vendor terms. The CEO is the person who can authorize a licensing discussion and sign; the [who-can-say-yes tree](/questions/who-can-license-chargeback-evidence-assembly-records) maps that path.

The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application.

What stays unknown until SourceX reviews it: buyer interest in dispute history, how payment provider, carrier and vendor terms affect rights, the de-identification customer messages need, and whether an offer follows. The [referral brief template](/resources/chargeback-evidence-assembly-referral-brief-template) puts the timeline's dates on one page, and the [accounts receivable dispute resolution page](/data-types/accounts-receivable-dispute-resolution-process) and [chargeback representment records](/data-types/chargeback-representment-records) cover neighboring record types.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a retailer's renewal notice date is close and its case links, notes and outcomes are not in the export plan, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the disputes director.

## Sources

- https://docs.stripe.com/disputes/how-disputes-work
- https://docs.stripe.com/disputes/responding
- https://refer.sourcex.si/terms
