> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integration-guide/control-center/analytics.md). # Analytics ## Analytics & Insights Where **Operations** shows you individual transactions, **Analytics** shows you the *patterns*: success rates over time, which connectors perform best, why payments fail, and how refunds and disputes trend. This is how you spot problems and prove improvements. Like everything else, analytics respect your current **mode (Test/Live)** and **selected profile**, plus a **date range** you choose at the top. This section covers: * Overview dashboard * Payments analytics * Refunds & disputes analytics * Insights & smart views * Reports & exports *** ### Overview dashboard The analytics **Overview** gives you the health of your payments at a glance. Typical top-level metrics: * **Total payment volume** and **count** * **Success rate** (and how it's trending) * **Failed / declined** breakdown * **Refunds** and **disputes** at a summary level Use the **date range** and **filters** (connector, payment method, currency) to slice any of these. This is the first screen to open each morning. *** ### Payments analytics A deeper view focused entirely on payments. Here you can analyze: * **Success rate over time** — spot dips the moment they happen. * **By connector** — compare processor performance side by side (feeds your routing decisions). * **By payment method** — which methods convert best. * **Failure / error reasons** — grouped decline reasons so you can see *why* payments fail, not just *that* they do. > 💡 The **error-reasons** breakdown is the bridge between Analytics and action: a spike in one decline code often points at a specific connector or a payment-method misconfiguration. *** ### Refunds & disputes analytics Track the money going back out and the challenges you're fighting. * **Refunds analytics** — refund volume, rate, and trends; a rising refund rate is an early warning sign. * **Disputes analytics** — dispute counts, win/loss rate, and reason codes so you can address root causes. * **Authentication analytics** (where enabled) — how 3DS is performing and its effect on conversion. *** ### Insights & smart views The **Insights** area presents richer, pre-built visualizations and drill-downs on top of your raw data. * Curated dashboards that surface trends without you building queries. * **Routing analytics** to see how your routing and Intelligent Routing choices are performing. * **Global search** across your data to jump straight to what you need. Use Insights to answer "how are we doing?" and Payments analytics to answer "why?". *** ### Reports & exports When you need the data outside the dashboard — for finance, reconciliation, or a stakeholder — generate a report. 1. Choose the **data set** (payments, refunds, disputes) and a **date range**. 2. Apply any **filters** you need. 3. **Generate / download** the report (typically CSV) for use in spreadsheets or your data warehouse. > For continuous, automated reconciliation rather than ad-hoc exports, see the **Recon** module in the product suite. *** ### Where to go next * **Workflow** → act on what analytics reveal — adjust routing or 3DS rules. * **Operations** → drill from a trend down to the individual payments behind it. * **Recon** → automated reconciliation for finance teams (product suite). --- # 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.hyperswitch.io/integration-guide/control-center/analytics.md?ask=&goal= ``` `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.