> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/api-reference/api/reporting/standard-reporting.md).

# Standard Reporting

The **Standard Reporting API** provides access to various merchant-related data points, including merchant profiles, their transactions, financial activity, funding, disputes, support cases, and batch activity.

### **Standard reports**

Below standard reports provide a structured and predefined view of core merchant activities for reporting and analysis.

<table data-full-width="false"><thead><tr><th>Report Name</th><th>Description</th><th>Key Data Elements</th></tr></thead><tbody><tr><td>Merchant profiles</td><td>Comprehensive merchant profile data</td><td>MID, DBA name, hierarchy info, compliance status, contact details, business info</td></tr><tr><td>Current pricing configuration</td><td>Details pricing plans and fee structures</td><td>Pricing plan types, effective dates, fee descriptions, rates, fee schedule</td></tr><tr><td>Disputes record</td><td>Tracks chargebacks and transaction disputes</td><td>Dispute details, card info, processing dates, reason codes, settlement info</td></tr><tr><td>Case records</td><td>Monitors support cases</td><td>Case numbers, creation/closure dates, categories, descriptions</td></tr><tr><td>Bank deposits</td><td>Tracks funding events</td><td>Deposit amounts, account info, funding types, settlement dates</td></tr><tr><td>Transaction records</td><td>Provides settled transaction history</td><td>Transaction details, terminal info, card data, amounts, interchange fees, qualifications</td></tr><tr><td>Closed batches</td><td>Provides closed batches information</td><td>Batch totals, sales and refund counts, funding dates, deposit amounts, and related merchant batch activity</td></tr><tr><td>Card transactions</td><td>Provides detailed card transactions records</td><td>Transaction status, authorization details, settlement information, batch data, card type, interchange fees, customer details, billing/shipping info</td></tr></tbody></table>

{% hint style="warning" %}
For reports that use date-based filters:

* HNK (partner or portfolio level) queries support a maximum date range limit of **1 day** at the partner or portfolio level.
* MID (merchant level) queries support a maximum date range of **31 days**.

To improve performance and avoid timeouts:

* Include `pageNumber` and `pageSize` in your request.
* The maximum page size is **10,000 records**.
  {% endhint %}

To access merchant portfolio reports, see [Enhanced Reporting](https://docs.xplorpay.com/api-reference/api/reporting/enhanced-reporting).

To view and export reports via reporting UI in the Partner Portal, see [Retrieving Report via Partner Portal](https://docs.xplorpay.com/partner-portal/partner-portal/guides/reporting/retrieving-report-via-partner-portal).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xplorpay.com/api-reference/api/reporting/standard-reporting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.