# Automation (https://docs.chargeflow.io/docs/merchants/automation)



You have chargebacks being filed and want them fought - without building a disputes team. **Automation** is Chargeflow's representment product: once a dispute is filed, Chargeflow ingests it from your connected PSPs, assembles an evidence package, and submits the response on your behalf. Your integration's job is to make that evidence stronger by sending the data only you have.

## When to use Automation [#when-to-use-automation]

* You want every filed dispute answered, automatically, without per-case manual work.
* You have order, subscription, or customer-communication data that strengthens evidence.
* You want dispute status and outcomes flowing into your own systems via API and webhooks.
* You want to backfill and track historical disputes alongside new ones.

## How it works [#how-it-works]

Chargeflow ingests disputes from your connected payment processors, enriches each case with the signals you provide, generates the evidence response, and submits it within the network deadline. Four parts: data ingestion, data enrichment, evidence creation, submission, with every outcome fed back into the next case.

<Cards>
  <Card title="How recovery works" href="/docs/reference/concepts/how-recovery-works">
    The whole pipeline in one diagram, from filing to outcome.
  </Card>

  <Card title="How our AI works" href="/docs/reference/concepts/how-our-ai-works">
    The agent architecture that writes the case.
  </Card>

  <Card title="Evidence generation" href="/docs/reference/concepts/evidence-generation">
    Why the claim is written from scratch rather than templated.
  </Card>
</Cards>

The API-level model is in [Dispute automation](https://docs.chargeflow.io/docs/reference/concepts/dispute-automation); the mechanics of a representment in [Representment and evidence](https://docs.chargeflow.io/docs/reference/concepts/representment-and-evidence).

## Work with the API [#work-with-the-api]

List disputes, fetch one by id, and enrich cases with your data. See the [Disputes API reference](https://docs.chargeflow.io/docs/api/2025-04-01/merchants/disputes).

Real-time events:

<Cards>
  <Card title="dispute.created" href="/docs/merchants/webhook-events#dispute-created">
    A new dispute was ingested - the trigger for your enrichment flow.
  </Card>
</Cards>

## Start integrating [#start-integrating]

The golden path is one guide - where your integration plugs into the pipeline:

<Card title="Automate dispute management" href="/docs/merchants/automation/automate-dispute-management">
  **Start here** - the two places your integration acts: send a second enrichment, then track the
  outcome.
</Card>

Then go deeper as you need it: [Enrich a dispute](https://docs.chargeflow.io/docs/merchants/automation/enrich-a-dispute) to move win rate, [Upload evidence](https://docs.chargeflow.io/docs/merchants/automation/upload-evidence) for files, run the [Automate a chargeback dispute](https://docs.chargeflow.io/docs/merchants/automation/automate-a-chargeback-dispute) recipe end-to-end, or [Backfill 90 days](https://docs.chargeflow.io/docs/merchants/automation/backfill-90-days) of history.

## Where Automation fits [#where-automation-fits]

Automation acts at stage 4 of the [transaction lifecycle](https://docs.chargeflow.io/docs/reference/start-here/transaction-lifecycle) - after the chargeback is filed. Complaints caught earlier are deflected by [Alerts](https://docs.chargeflow.io/docs/merchants/alerts); risky orders are stopped before shipping by [Prevent](https://docs.chargeflow.io/docs/merchants/prevent).