# Insights (https://docs.chargeflow.io/docs/merchants/insights)



You want to know your chargeback position before your processor tells you. **Insights** is Chargeflow's monitoring product: a single view of payments and chargebacks across every processor you have connected, with proactive notifications when something moves in the wrong direction.

## When to use Insights [#when-to-use-insights]

* You run more than one processor and have no single number for your dispute ratio.
* You want warning that a ratio is approaching a scheme threshold while you can still act, not after a penalty.
* You need dispute performance broken down by processor, reason code, or period for a board or a partner.
* You want fraud patterns surfaced across your payment stack rather than per tool.

## What it gives you [#what-it-gives-you]

| Capability              | What it does                                                                         |
| ----------------------- | ------------------------------------------------------------------------------------ |
| Holistic view           | Payments and chargebacks from every connected processor in one dashboard             |
| Fraud intelligence      | Patterns across your stack, not siloed per processor                                 |
| Customised insights     | Cuts by processor, reason code, and period                                           |
| Real-time notifications | Told when a ratio moves, not at month end                                            |
| Proactive alerts        | A warning when your chargeback ratio approaches a threshold, with the action to take |

Insights reads from the same connections the rest of Chargeflow uses. Connect a processor once and it appears here. See [Integrations](https://docs.chargeflow.io/docs/reference/integrations).

## Why thresholds matter [#why-thresholds-matter]

Card networks monitor dispute ratios, and crossing a threshold moves you into a monitoring program with fees, mandated remediation, and in the worst case loss of processing. The ratio is a lagging number, so the useful moment is while it is climbing. That is the moment Insights is built for: [Alerts](https://docs.chargeflow.io/docs/merchants/alerts) deflects the disputes and [Prevent](https://docs.chargeflow.io/docs/merchants/prevent) stops the risky orders, while Insights tells you which lever the numbers say to pull.

<Callout title="Insights API - coming soon">
  Insights runs today in the Chargeflow dashboard. There is no public API for its metrics yet, so
  nothing on this page is callable. Dispute-level data is available now through the [Disputes
  API](https://docs.chargeflow.io/docs/api/2025-04-01/merchants/disputes) if you want to build your own reporting.
</Callout>

## Where Insights fits [#where-insights-fits]

Prevent, Alerts, and Automation act on individual transactions and disputes. Insights acts on the portfolio: it is the layer that tells you whether the other three are working and where the next problem is forming. See the [product model](https://docs.chargeflow.io/docs/reference/start-here/product-model).

## Next step [#next-step]

<Cards>
  <Card className="cf-card-outline" iconName="card-chip-1" title="Deflect chargebacks with alerts" href="/docs/merchants/alerts/prevent-with-alerts">
    The usual response to a climbing ratio: deflect before the chargeback posts.
  </Card>
</Cards>