Chargeback Export Data

The Chargeback export file contains all chargeback cases associated with each merchant. It captures full dispute details including the card network reason code, case lifecycle stage, financial impact direction, authorization reference, cardholder account (masked), and resolution status. Use this file to manage the chargeback lifecycle, track reversals, and support representment and dispute resolution workflows.

Endpoint

GET /download/YYYYMMDD/Chargeback

Authentication

Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:

Authorization: Basic {base64(username:password)}

When to use

Process this file daily to monitor chargeback activity across your merchant portfolio. Identify new cases requiring action (ItemType: NewCases), track cases resolved in the merchant's favor (ResolutionTo: Merchant), and use FamilyID to link related dispute records across multiple stages of the same transaction dispute. The AcquirerReferenceNumber is the key field for communicating with card networks about a specific case.

Query Parameters

None. The file is identified by the date path segment (YYYYMMDD) and delivered via SFTP.

Response

200 OK — Returns XML content with the following structure:

XML Hierarchy: Merchants > Merchant > Chargebacks > Chargeback

<Merchant> fields:

<Chargeback> fields:

<Merchants>
  <Merchant>
    <MID>9180000000001234</MID>
    <Chargebacks>
      <Chargeback>
        <CaseNumber>2026148001052</CaseNumber>
        <CaseType>FirstChargeback</CaseType>
        <ItemType>NewCases</ItemType>
        <ResolutionTo xsi:nil="true" />
        <DebitCredit>Debit</DebitCredit>
        <TranCode>RetailSale</TranCode>
        <ReasonCode>13.1</ReasonCode>
        <ReasonDesc>Merchandise/Services Not Received</ReasonDesc>
        <CaseAmount>142.50</CaseAmount>
        <CardBrand>Visa</CardBrand>
        <DateResolved />
        <AcquirerReferenceNumber>85207999247900019063197</AcquirerReferenceNumber>
        <AuthCode>412649</AuthCode>
        <DateTransaction>2026-04-15T14:30:00</DateTransaction>
        <DatePosted>2026-04-16T12:00:00</DatePosted>
        <DateLoaded>2026-05-20T12:00:00</DateLoaded>
        <CardholderAccountNumber>414100XXXXXX0555</CardholderAccountNumber>
        <DateSecondRequest />
        <DateWarehouse>2026-05-21T12:00:00</DateWarehouse>
        <TransID>346134553487251</TransID>
        <MerchAmount>0.00</MerchAmount>
        <FamilyID>71452830</FamilyID>
      </Chargeback>
    </Chargebacks>
  </Merchant>
</Merchants>

Error Codes

Common Mistakes

• Treating CaseAmount as equal to the original transaction amount — chargebacks can be partial disputes.
• Ignoring MerchAmount: 0.00 — this indicates no representment has been filed and action may still be required before the deadline.
• Not using FamilyID to group related records — a single transaction may generate multiple chargeback records (initial, representment, pre-arbitration) that must be linked for accurate reporting.
• Misreading ReasonCode without referencing the correct card network — Visa and Mastercard use different reason code taxonomies.
• Assuming DateResolved empty means the case was just opened — cross-reference DateLoaded to determine the age of the case.

Related Endpoints

• GET /download/YYYYMMDD/Transactions — original transaction detail for dispute cross-reference
• GET /download/YYYYMMDD/TransAuth — authorization records used in representment evidence
• GET /download/YYYYMMDD/ACHRejectsCollects — ACH-related failures (separate from card chargebacks)

Example

curl -X GET "https://hq.staging.netevia.dev/download/20260528/Chargeback" \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)"