How to Export and Organize Chargeback Data Before Switching Providers

A chargeback data export preserves cases, payments, evidence, deadlines, and financial events outside the outgoing provider. Build a migration dataset that lets the next owner finish open work and reconcile closed outcomes without losing the relationships between records. It is the data side of switching chargeback providers.

{{cta}}

Define the Export’s Purpose

Obtain the outgoing field list and file formats, then map them to the incoming provider’s documented intake. Resolve unsupported fields before the full transfer.

Inspect the downloaded records for case and payment identifiers, deadlines, evidence access, and submission acknowledgments. A dashboard total does not establish that those records are present.

Build Four Connected Record Sets

Keep the datasets separate where that makes them easier to validate. Use identifiers to connect them instead of repeating every file in a single spreadsheet.

Preserve Account Context

A transaction identifier may be unique inside one account without being a reliable standalone key across your whole business.

Keep legal entity, store, and payment method where those fields affect operational responsibility or reporting. A shared customer email should not replace a transaction key.

If you operate multiple currencies, retain the original amount and currency. Add reporting-currency values only with a documented conversion basis.

Export Open Cases First

Use the processor's live case record to verify actionable status. Avoid applying a generic deadline based on an article or an old file; chargeback time limits vary by network and by party, so the live case record wins.

Plan for Disputes That Arrive After Cutover

Switching providers does not stop disputes on transactions you processed before the switch. Cardholders can file for months after the purchase, so your export has to support responses long after the old contract ends.

Source: Adyen dispute timeframes. Exact windows depend on network rules, reason code and your processor, so treat the live case deadline as authoritative.

Check these windows against your own record-retention policy and legal obligations, then keep the longer of the two.

Organize Evidence as a Manifest

Separate already-submitted evidence from records that could support an unsubmitted response. Preserve the response acknowledgment where available. A chargeback evidence source map helps you list which system holds each record type.

Do not collect entire customer profiles when only specific transaction records are needed. Apply your organization's access and retention controls to the archive.

Never put full card numbers or security codes in the export. PCI DSS prohibits storing sensitive authentication data such as the card security code after authorization, even encrypted, and requires stored card numbers to be unreadable. The card brand and last four digits are enough to match a dispute to its payment.

Open the evidence with the access that will remain after cancellation. If the file depends on the outgoing login, preserve an authorized durable copy or arrange a supported transfer.

Keep 365 Days of Transaction History for Visa CE3.0

A dispute-only export loses that history. If your outgoing provider stored IP, device, login and delivery signals, export them for every transaction from the past 365 days, keyed to the same composite transaction key, so the next provider can build a CE3.0 response from the first fraud dispute after cutover. Read how Visa Compelling Evidence 3.0 works before you decide which fields to keep.

Validate Refunds and Financial Events

A refund can occur before or after a complaint and may be partial. Preserve its identifier, amount, currency, status, and relationship to the original payment.

Keep an attempted refund distinct from a completed refund. Keep a chargeback reversal distinct from a customer refund.

Include refunds the outgoing provider issued through chargeback alerts, and record which system issued each one. A refund your new team cannot see is a refund it may issue a second time.

For closed cases, record final outcome and recovered amount. Add the service charge and settlement reference where available, so finance can keep chargeback accounting consistent across the switch.

An illustrative validation compares 120 exported cases with 120 source cases, then checks their amounts by currency. Matching the count alone does not prove that case ownership or evidence is complete.

Use Processor Exports as a Cross-Check

Stripe's analytics documentation describes downloading chart data as CSV with the selected filters. Record those filters so your team knows the dataset's scope.

Use the analytics CSV to cross-check the migration dataset. Match its filters and field definitions before comparing counts or monetary totals.

Where Each Processor Exposes Dispute Data

For any other processor, use its current documented report or API, and verify historical coverage and pagination before you trust a total. Do not assume its interface matches these four.

On Stripe, dispute evidence fields hold file IDs rather than the files themselves. Per the Stripe file upload guide, a file's contents are downloadable only when its purpose allows it, and an uploaded file can be used in a single API request. Keep your own original evidence files instead of relying on IDs from the old account.

Create a Field-Mapping Sheet

Map outgoing fields to the incoming provider's requirements. Document transformations such as status labels, currency formats, and timestamp conventions.

Preserve unknown values explicitly. An unreported outcome is not a loss, and a missing amount must not become zero during transformation.

Ask the incoming provider to ingest a representative sample before the full transfer. Include an open case, a closed case, a partial refund, and a case with evidence attachments.

Chargeflow's Developer Hub provides integration guidance. Confirm the supported migration and intake route for your specific configuration.

Validate a Sample Joined Record

Run duplicate-key, missing-deadline, broken-file, and currency-total checks on the sample. An unknown status should fail mapping visibly rather than default to lost or closed. Once the sample joins correctly, apply the same validation to the full export.

Run a Final Acceptance Check

Validate Counts Before and After Joining Evidence

A joined export can duplicate a dispute when one case has several evidence files, refunds, or status events. Validate the base case count before calculating recovered value from the combined dataset.

Investigate unmatched records, duplicate event identifiers, and cases with no accessible evidence. This check stops a structurally valid CSV from becoming a financially misleading migration file.

FAQs

What Data Should You Export Before Switching Chargeback Providers?

Export unresolved cases, transaction references, response deadlines, evidence files, submission acknowledgments, refunds, final outcomes, and relevant service charges. Preserve account context and relationships between records. Confirm which fields and files the incoming workflow accepts.

What Happens if a Chargeback Is Disputed?

The merchant’s response and relevant evidence enter the applicable review process, known as representment, and the issuer decides the outcome. For an export, preserve the submitted version, acknowledgment, status history, and final decision separately from a draft packet.

Is a CSV Enough for a Chargeback Migration?

Not usually by itself. A CSV can organize case records, while evidence files and submission acknowledgments may require a separate archive or supported transfer route. Verify that file references remain accessible after the outgoing account is disconnected.

Should You Export Customer Data?

Export only the customer information needed for open cases and ongoing dispute work, under your organization’s access and retention requirements. Leave out full card numbers and security codes: PCI DSS bars storing sensitive authentication data after authorization, and the card brand plus last four digits are enough to match a chargeback to its payment.

What Is the 540-Day Rule for Chargebacks?

The 540-day rule is the outer limit for some Visa and Mastercard disputes. Cardholders generally have 120 days from the transaction date to file, but cases such as pre-orders or travel can extend to 540 days. For a merchant switching chargeback providers, it means order, fulfillment, and refund records for pre-switch transactions should stay accessible for up to 540 days after the last transaction the old provider handled.

What Is the Difference Between a Chargeback and a Retrieval Request?

A retrieval request is an issuer's request for transaction information before a chargeback is filed, while a chargeback reverses the funds. When you switch providers, export open retrieval requests with their response deadlines alongside chargebacks, because an unanswered retrieval request can turn into a chargeback after cutover.

Use Your Export to Move Toward Chargeflow

Use the export to establish a dependable recovery workflow with Chargeflow, our recommended next platform for connected evidence and automation. First reconcile the data and preserve access for the people completing open cases. If you are leaving manual work behind, read the checklist for migrating to automated chargeback management and see how automated chargeback management works. Explore Chargeflow Automation and confirm the supported intake before changing responsibility.