> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/reporting/reporting/order-search-chargeback-info-export.md).

# Order search chargeback info export

Use **Order search** data portability capabilities to generate and export a chargeback dispute report.

## Create a custom template for the chargeback report in Order Search <a href="#create-a-custom-template-for-the-chargeback-report-in-order-search" id="create-a-custom-template-for-the-chargeback-report-in-order-search"></a>

Before generating a chargeback report, you need to create its corresponding order search export template. Follow these steps:

1. Go to **Orders & customers** > [Order search](https://secure.avangate.com/cpanel/reports.php).
2. Run a search. Optional: You can filter results, but this is not necessary.
3. Click **Export**.
4. Click [Edit templates ](https://secure.avangate.com/cpanel/export_templates.php?IdReport=1)in the pop-up.
5. Click **Add new template** on the [Export Templates settings](https://secure.avangate.com/cpanel/export_templates.php?IdReport=1) page.
6. Enter a unique name for this order search export template. For example: **Custom Chargebacks Report**.
7. Select the information that will be included in this report. For example:
   * Under **Order**:
     * Reference no
     * Order date
     * Chargeback status
     * Chargeback reason
   * Under **Product**:
     * Product ID
     * Product
   * Under **Price**:
     * Currency
     * General total
   * Under **Customer and End User information**:
     * Client
   * This enables you to choose the column headers of the order search report, which can be exported as a CSV (comma-separated values) or an XLS (Excel) file, or the XML elements when the export is an XML file.
8. Once you selected the type of details to be included in the report, click the arrow button between the **Additional Column headers** and the **Template Column headers** fields.
9. The desired details will be added to the **Template Column headers**. Click **Save** to add the new template to the list of existing items.

{% hint style="info" %}
You can include additional info in the report, based on your account's specific setup.
{% endhint %}

For complete guidance on order search export templates, read: [Custom order search export templates - XML, CSV, XLS](/reporting/reporting/custom-order-search-export-fields-and-templates-xml-csv-xls.md).

## Export a custom chargeback report using Order Search <a href="#export-a-custom-chargeback-report-using-order-search" id="export-a-custom-chargeback-report-using-order-search"></a>

1. Navigate to [Order search](https://secure.avangate.com/cpanel/reports.php) under **Orders & customers**.
2. Under order status, select **Finished**. Chargebacks can only be opened for finished orders.
3. Select the desired order search interval.
4. Run a search.
5. Click the **Export** button.
6. In the pop-up, select the desired download format, for example, CSV.
7. Open the menu under **Export Templates** and select the custom chargeback export template you created. Click **Export**.
8. Save the exported chargebacks report locally on your machine, and open it with your preferred CSV editor (you can use Office Excel, for example).

The report will include all orders returned to the search you performed, but you can filter content based on the **Chargeback reason** and **Chargeback status** column headers.

| Field name        | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Data type | Length      |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ----------- |
| Chargeback Status | <p>The status of the chargeback dispute from the moment the report is generated.</p><p>Possible values:</p><p><strong>OPEN</strong> = a chargeback was opened by a customer and the dispute continues to be unresolved.</p><p><strong>WON</strong> = the dispute was won by you and no money were paid back to the customer.</p><p><strong>LOST</strong> = the dispute was lost and the entire value of the order was reimbursed to the customer.</p><p><strong>NONE</strong> = if a chargeback wasn't requested.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | string    | VARCHAR(20) |
| Chargeback Reason | <p>The reason why the chargeback was initiated. Possible values:</p><p> </p><p><strong>1. Order not fulfilled/not delivered:</strong> Customers claim that they did now receive the product they purchased or that they cannot access the service acquired.</p><p><strong>2. Product(s) not as described/unfunctional:</strong>Customers claim that the product/subscription/service purchased does not work or functions differently than you advertised it would.</p><p><strong>3. Duplicate order:</strong> Customers claim that they were charged twice when purchasing the same product.</p><p><strong>4. Fraud/Order not recognized:</strong>Customers claim that they don't recognize the charge.</p><p><strong>5. Agreed refund not processed:</strong> Customers have opened a chargeback dispute because the refund they agreed on with you failed to process.</p><p><strong>6. New/renewal order not recognized:</strong> Customers have opened a chargeback dispute because the refund they agreed on with you failed to process.</p><p><strong>7. Authorization problem:</strong>Customers claim that the payment authorization failed and are surprised to see that the charge went through.</p><p><strong>8. Information request:</strong> The customer's bank requested details about a charge. This is a temporary status, which can be closed once customers recognize the charge, or result in a chargeback for one of the reasons listed above.</p> | string    | VARCHAR(80) |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.2checkout.com/reporting/reporting/order-search-chargeback-info-export.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
