Returns daily chargeback case records in XML format, including case type, reason code, card brand, financial impact, and dispute lifecycle dates for each merchant.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Chargeback Export Data
Returns daily chargeback case records in XML format, including case type, reason code, card brand, financial impact, and dispute lifecycle dates for each merchant.
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:
| Field | Type | Description |
|---|---|---|
MID | string | Merchant identifier (unique account number) |
<Chargeback> fields:
| Field | Type | Description |
|---|---|---|
CaseNumber | string | Unique case ID in YYYYJJJ###### format (year + Julian day + 6-digit sequence) |
CaseType | string | Dispute lifecycle type: FirstChargeback, SecondChargeback, CollaborationReversal, Allocation, etc. |
ItemType | string | Case category: NewCases, FulfilledRetrievalRequests, WorkedCaseResolvedtoMerchant, etc. — see Understanding Chargeback Statuses below for the full list and what each one means |
ResolutionTo | string | Resolution party: IssuingBank, Merchant, AcquirersGeneralLedger, Split (null if unresolved) |
DebitCredit | string | Financial impact: Debit = funds pulled from merchant; Credit = funds returned; NonFinancial |
TranCode | string | Original transaction type: RetailSale, Credit, CashAdvance, QuasiCash |
ReasonCode | string | Card network reason code (e.g. 13.1 for Visa, 4853 for Mastercard) |
ReasonDesc | string | Human-readable description of the reason code |
CaseAmount | decimal | Dollar amount of the chargeback |
CardBrand | string | Card network: Visa, Mastercard, Discover, Amex, PayPal |
DateResolved | date | Date the case was resolved (empty if still open) |
AcquirerReferenceNumber | string | 23-digit acquirer reference number for network tracking |
AuthCode | string | Authorization approval code from the original transaction |
DateTransaction | datetime | Date and time of the original disputed transaction |
DatePosted | datetime | Date the chargeback was posted to the merchant account |
DateLoaded | datetime | Date the case was loaded into the dispute management system |
CardholderAccountNumber | string | Masked card PAN of the disputing cardholder (e.g. 000000XXXXXX0000) |
DateSecondRequest | date | Date a second retrieval request was issued (empty if not applicable) |
DateWarehouse | datetime | Date the case was archived to the data warehouse |
TransID | string | Internal transaction identifier linking to the original transaction record |
MerchAmount | decimal | Amount submitted in representment (0.00 if no representment filed) |
FamilyID | string | Groups all related dispute cases for the same transaction together |
<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>Understanding Chargeback Statuses
A single dispute can generate several <Chargeback> records over time — one when it's first loaded, another when it moves to a new stage, another when it's finally resolved. Reading the current state of a case means looking at four fields together; none of them tells the full story on its own:
| Field | What it tells you |
|---|---|
CaseType | Which stage of the dispute lifecycle this record represents |
ItemType | Why this specific record appears in today's file — what happened today |
ResolutionTo | Once a case is closed, which party the case was decided against |
DebitCredit | The direction money actually moved for this specific record |
Always group records by FamilyID first, then look at the most recently loaded record in that group to see where the case currently stands — an earlier record in the same family can look like a loss (Debit) while a later one in the same family shows it was won on appeal (Credit).
ItemType — why the record is in today's file
ItemType — why the record is in today's file| Value | Meaning |
|---|---|
NewCases | A brand-new chargeback or reversal case was loaded today. Nothing decided yet. |
FulfilledRetrievalRequests | A retrieval request (a request for documentation, not a financial chargeback) was fulfilled today. |
WorkedCaseResolvedtoOther | The case closed today with funds staying away from the merchant (bank, GL, or split). |
WorkedCaseResolvedtoMerchant | The case closed today with funds landing on the merchant's side (credit, GL, or split). |
CorrectedCase | Transaction or merchant data on an existing case was corrected — not itself a resolution. |
NewRetrievals | A new retrieval request was loaded today. |
SecondRetrievalRequests | A second retrieval request letter was sent today. |
OutgoingPreArbitration | An outgoing pre-arbitration request was submitted to the issuing bank. |
OutgoingCollection | The chargeback exceeded card-brand time frames; a good-faith request was sent to the issuing bank. |
OutgoingCompliance | A financial loss occurred with no valid dispute rights (or a rule violation); a pre-compliance request was sent to the issuing bank. |
CaseType — what kind of record this is
CaseType — what kind of record this isCase types fall into two families:
- Chargeback / debit-side types —
FirstChargeback,SecondChargeback,DiscoverChargeback,AMEXChargeback,PINDebitChargeback, and theAllocation/Collaborationfamily. These represent money being pulled from the merchant. - Reversal / credit-side types —
FirstReversal,SecondReversal,DiscoverReversal,AMEXReversal,AllocationReversal,CollaborationReversal,PINDebitReversal. These represent a chargeback being reversed — money going back to the merchant.
A won dispute almost always shows up as a reversal-type record sharing the FamilyID of the original chargeback.
ResolutionTo and DebitCredit — who bears the outcome
ResolutionTo and DebitCredit — who bears the outcomeResolutionTois the party the case was decided against:IssuingBankmeans the issuer/cardholder side absorbed the loss (merchant wins);Merchantmeans the merchant absorbed it (merchant loses);Splitmeans it was shared;AcquirersGeneralLedgermeans the acquirer absorbed it internally.DebitCreditis the direction of this record's entry:Debit= money pulled from the merchant,Credit= money returned to the merchant,NonFinancial= no money movement (e.g. a retrieval request).
How to tell if a chargeback was won
Check, in this order:
- Is there a reversal-type
CaseType(FirstReversal,SecondReversal, any*Reversal) for the sameFamilyIDwithDebitCredit = Credit? If yes — the merchant won that stage; funds have been credited back. - What does
ResolutionTosay on the closing record?IssuingBank, or a favorableSplit, confirms a win;Merchantconfirms a loss. - Check
MerchAmount.0.00means no representment has been filed yet — still open, nothing decided. A non-zero value is the amount actually credited or debited when the case closed; compare it toCaseAmountto see if the recovery was full or partial. - No later record under the same
FamilyID, and the response deadline has passed? Treat it as a loss — the chargeback stands as originally posted (Debit). This endpoint doesn't expose a dedicated "final, no recourse" flag, so absence of a reversal record after the deadline is the strongest available signal, not a separate status field.
Example: a full dispute lifecycle
Same FamilyID (71452830), two records loaded on different days.
Day 1 — new chargeback, nothing decided yet:
<Chargeback>
<CaseNumber>2026148001052</CaseNumber>
<CaseType>FirstChargeback</CaseType>
<ItemType>NewCases</ItemType>
<ResolutionTo xsi:nil="true" />
<DebitCredit>Debit</DebitCredit>
<CaseAmount>142.50</CaseAmount>
<MerchAmount>0.00</MerchAmount>
<FamilyID>71452830</FamilyID>
</Chargeback>Reading it: brand-new case, MerchAmount is 0.00 (no representment filed yet), ResolutionTo is empty. Status: pending — the merchant is temporarily out the funds, but nothing has been decided.
Day 2 — representment wins, reversal posts:
<Chargeback>
<CaseNumber>2026156002210</CaseNumber>
<CaseType>FirstReversal</CaseType>
<ItemType>WorkedCaseResolvedtoMerchant</ItemType>
<ResolutionTo>IssuingBank</ResolutionTo>
<DebitCredit>Credit</DebitCredit>
<CaseAmount>142.50</CaseAmount>
<MerchAmount>142.50</MerchAmount>
<FamilyID>71452830</FamilyID>
</Chargeback>Reading it: CaseType is a reversal, ItemType shows the case resolved toward the merchant, ResolutionTo is IssuingBank (the loss went back to the issuer), DebitCredit is Credit, and MerchAmount matches CaseAmount. Status: won — the full $142.50 was credited back.
Example: a final loss
<Chargeback>
<CaseNumber>2026148001052</CaseNumber>
<CaseType>FirstChargeback</CaseType>
<ItemType>WorkedCaseResolvedtoOther</ItemType>
<ResolutionTo>Merchant</ResolutionTo>
<DebitCredit>Debit</DebitCredit>
<CaseAmount>142.50</CaseAmount>
<MerchAmount>142.50</MerchAmount>
<FamilyID>71452830</FamilyID>
</Chargeback>Reading it: CaseType is still the original chargeback (no reversal record exists for this FamilyID), ResolutionTo is Merchant, DebitCredit is Debit, and MerchAmount equals CaseAmount. Status: lost — the $142.50 stays debited and no reversal followed.
Example: a split resolution
<Chargeback>
<CaseNumber>2026160003301</CaseNumber>
<CaseType>SecondReversal</CaseType>
<ItemType>WorkedCaseResolvedtoOther</ItemType>
<ResolutionTo>Split</ResolutionTo>
<DebitCredit>Credit</DebitCredit>
<CaseAmount>200.00</CaseAmount>
<MerchAmount>100.00</MerchAmount>
<FamilyID>71460021</FamilyID>
</Chargeback>Reading it: ResolutionTo is Split and MerchAmount (100.00) is only half of CaseAmount (200.00) — the loss was shared between the merchant and another party. Status: partial win — half the disputed amount was recovered.
Quick reference
| Signal | Meaning |
|---|---|
ItemType = NewCases, MerchAmount = 0.00 | Case just opened, nothing decided yet |
CaseType is a chargeback type, ResolutionTo empty | Still open / awaiting representment |
CaseType is a reversal type, DebitCredit = Credit, ResolutionTo = IssuingBank | Won |
No reversal record under the same FamilyID, ResolutionTo = Merchant, DebitCredit = Debit | Lost |
ResolutionTo = Split | Partial win/loss — compare MerchAmount to CaseAmount for the ratio |
Error Codes
| Code | When it happens |
|---|---|
| 400 | Malformed date format in URL path |
| 401 | Invalid or missing Basic Auth credentials |
| 403 | User does not have permission for this operation |
| 404 | No chargeback file found for the specified date |
| 500 | Internal server error |
Common Mistakes
- Treating
CaseAmountas 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
FamilyIDto group related records — a single transaction may generate multiple chargeback records (initial, representment, pre-arbitration) that must be linked for accurate reporting. - Misreading
ReasonCodewithout referencing the correct card network — Visa and Mastercard use different reason code taxonomies. - Assuming
DateResolvedempty means the case was just opened — cross-referenceDateLoadedto determine the age of the case. - Treating any closed case as a loss by default — check for a reversal-type
CaseTyperecord under the sameFamilyIDbefore concluding the merchant lost. - Concluding a case is a final loss just because it's been open a long time with no reversal —
itemTypehas no explicit "final, no recourse" value, so absence of a reversal after the response deadline is the best available signal, not a status field you can key off directly.
Related Endpoints
GET /download/YYYYMMDD/Transactions— original transaction detail for dispute cross-referenceGET /download/YYYYMMDD/TransAuth— authorization records used in representment evidenceGET /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)"OpenAPI definition
{
"openapi": "3.0.0",
"info": {
"version": "download",
"title": "Netevia HQ | Export Data Documentation",
"description": "Netevia HQ | Export Data Documentation"
},
"paths": {
"/download/YYYYMMDD/Chargeback": {
"get": {
"tags": [
"ExportData"
],
"operationId": "ExportData_Chargeback",
"responses": {
"200": {
"description": "OK",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/MerchantChargebacksData"
}
},
"text/json": {
"schema": {
"$ref": "#/components/schemas/MerchantChargebacksData"
}
},
"application/xml": {
"schema": {
"$ref": "#/components/schemas/MerchantChargebacksData"
}
},
"text/xml": {
"schema": {
"$ref": "#/components/schemas/MerchantChargebacksData"
}
},
"mid": {
"examples": {
"response": {
"value": "9180000000004242"
}
}
},
"chargebacks": {
"examples": {
"response": {
"value": [
{
"caseNumber": "2019252031169",
"caseType": 3,
"resolutionTo": 1,
"debitCredit": 1,
"tranCode": 5,
"reasonCode": "4837",
"reasonDesc": "No Cardholder Authorization",
"caseAmount": 44.95,
"cardBrand": 2,
"dateResolved": "2019-10-02T12:00:00",
"acquirerReferenceNumber": "85207999247900019063196",
"authCode": "225086",
"dateTransaction": "2019-09-01T12:00:00",
"datePosted": "2019-09-03T12:00:00",
"dateLoaded": "2019-10-02T12:00:00",
"cardholderAccountNumber": "123456XXXXXX1234",
"dateSecondRequest": "2019-10-02T12:00:00",
"transID": "MCWFQU1PO0803",
"merchAmount": 82.04,
"familyID": "23819352"
}
]
}
}
}
}
}
},
"summary": "Chargeback Export Data",
"description": "Returns daily chargeback case records in XML format, including case type, reason code, card brand, financial impact, and dispute lifecycle dates for each merchant."
}
}
},
"security": [
{
"Basic": []
}
],
"servers": [
{
"url": "https://hq.staging.netevia.dev"
}
],
"components": {
"securitySchemes": {
"Basic": {
"type": "http",
"description": "Basic HTTP Authentication",
"scheme": "basic"
}
},
"schemas": {
"MerchantChargebacksData": {
"type": "object",
"properties": {
"mid": {
"description": "Merchant ID",
"type": "string"
},
"chargebacks": {
"type": "array",
"items": {
"$ref": "#/components/schemas/MerchantChargebackData"
}
}
}
},
"MerchantChargebackData": {
"type": "object",
"properties": {
"caseNumber": {
"description": "The unique number assigned by the system to every case.\r\n\r\nThe format is YYYYJJJ######, where YYYY is the year, JJJ is the 3-character Julian day, and ###### is the 6-character case number.",
"type": "string"
},
"caseType": {
"description": "\"The type of case involved. Possible values:\r\n* FirstChargeback\r\n* SecondChargeback\r\n* FirstReversal\r\n* SecondReversal\r\n* AmericanExpressChargeback\r\n* Allocation\r\n* Collaboration\r\n* CollaborationReversal\"",
"enum": [
"Retrieval",
"FirstChargeback",
"SecondChargeback",
"FirstReversal",
"SecondReversal",
"IncomingCollection",
"OutgoingCollection",
"IncomingCompliance",
"OutgoingCompliance",
"IncomingPreArbitration",
"DiscoverRetrieval",
"DiscoverChargeback",
"DiscoverReversal",
"DiscoverPreArbitration",
"DiscoverIncomingDisputeArb",
"DiscoverPreArbArbDebit",
"AMEXInquiry",
"AMEXChargeback",
"AMEXReversal",
"Allocation",
"Collaboration",
"AllocationReversal",
"CollaborationReversal",
"CollaborationPreArbitration",
"MasterCardPreArbitration",
"MasterCardArbitration",
"CollaborationArbitration",
"OutgoingAllocationPreArbitration",
"OutgoingAllocationArbitration",
"OutgoingAllocationReversalPreArbitration",
"OutgoingAllocationReversalArbitration",
"PINDebitAllocation",
"PINDebitCollaboration",
"PINDebitAllocationReversal",
"PINDebitCollaborationReversal",
"PINDebitCollaborationPreArbitration",
"PINDebitCollaborationArbitration",
"PINDebitOutgoingAllocationPreArbitration",
"PINDebitOutgoingAllocationArbitration",
"PINDebitOutgoingAllocationReversalPreArbitration",
"PINDebitOutgoingAllocationReversalArbitration",
"PINDebitChargeback",
"PINDebitReversal"
],
"type": "string"
},
"itemType": {
"description": "The type of item involved. See 'Understanding Chargeback Statuses' above for what each value means and how to use it to determine whether a case was won.",
"enum": [
"NewCases",
"FulfilledRetrievalRequests",
"WorkedCaseResolvedtoOther",
"WorkedCaseResolvedtoMerchant",
"CorrectedCase",
"NewRetrievals",
"SecondRetrievalRequests",
"OutgoingPreArbitration",
"OutgoingCollection",
"OutgoingCompliance"
],
"type": "string"
},
"resolutionTo": {
"description": "The institution against which this case was resolved.\r\nPossible values:\r\n* IssuingBank\r\n* Merchant\r\n* AcquirersGeneralLedger\r\n* Split\r\n* Credit\r\nNote: This value is \"\"IssuingBank\"\" when a retrieval request is successfully fulfilled.\r\nThis value is \"\"Merchant\"\" when a retrieval request is closed due to time frame exceeded.",
"enum": [
"IssuingBank",
"Merchant",
"AcquirersGeneralLedger",
"Split"
],
"type": "string"
},
"debitCredit": {
"description": "Indicates whether the transaction is a debit or a credit. Possible values:\r\n* Debit\r\n* Credit\r\n* NonFinancial",
"enum": [
"Debit",
"Credit",
"NonFinancial"
],
"type": "string"
},
"tranCode": {
"description": "Indicates the type of transaction. Possible values:\r\n* RetailSale\r\n* Credit\r\n* CashAdvance\r\n* QuasiCash(often used with insurance payments)\r\nNote: The most common are RetailSale and Credit.",
"enum": [
"RetailSale",
"Credit",
"CashAdvance",
"QuasiCash"
],
"type": "string"
},
"reasonCode": {
"description": "This is the reason code for chargebacks from the card association.",
"type": "string"
},
"reasonDesc": {
"description": "The explanation of the Reason Code.",
"type": "string"
},
"caseAmount": {
"format": "double",
"description": "The amount of the chargeback. This is not always equal to the amount of the transaction.",
"type": "number"
},
"cardBrand": {
"description": "\"The type of card used in the transaction. Possible values:\r\n* Visa\r\n* MasterCard\r\n* Discover\r\n* American Express\r\n* PayPal\"",
"enum": [
"Visa",
"Mastercard",
"Discover",
"Amex",
"PayPal"
],
"type": "string"
},
"dateResolved": {
"description": "The date the that the chargeback case was resolved.",
"type": "string"
},
"acquirerReferenceNumber": {
"description": "A 23-digit identification number for a credit card transaction assigned by the acquirer.",
"type": "string"
},
"authCode": {
"description": "The authorization code passed with the settlement record.",
"type": "string"
},
"dateTransaction": {
"description": "The transaction date as reported by the issuer.",
"type": "string"
},
"datePosted": {
"description": "The post date as reported by the issuer.",
"type": "string"
},
"dateLoaded": {
"description": "The date the chargeback was loaded into the TSYS chargeback system.",
"type": "string"
},
"cardholderAccountNumber": {
"description": "Identifies the cardholder account number.",
"type": "string"
},
"dateSecondRequest": {
"description": "The date the second retrieval request was printed to be sent or faxed to the merchant.",
"type": "string"
},
"dateWarehouse": {
"description": "The date the file was sent to the data warehouse.",
"type": "string"
},
"transID": {
"description": "The unique card association identifier per transaction.",
"type": "string"
},
"merchAmount": {
"format": "double",
"description": "The amount debited or credited to the merchant if the case is resolved to the merchant. This will typically be the same as the Case Amount but may differ if the case resolution is split.",
"type": "number"
},
"familyID": {
"description": "A value assigned to link associated cases together. Cases that contain the same Acquirers Reference Number, Card Number, and Case Amount are assigned the same Family ID.",
"type": "string"
}
}
}
}
}
}