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

• 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

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. The model is covered canonically in Dispute automation; the mechanics of evidence in Representment and evidence.

Work with the API

List disputes, fetch one by id, and enrich cases with your data. See the Disputes API reference.

Real-time events:

Start integrating

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

Automate dispute managementStart here - the two places your integration acts: send a second enrichment, then track the outcome.

Then go deeper as you need it: Enrich a dispute to move win rate, Upload evidence for files, run the Automate a chargeback dispute recipe end-to-end, or Backfill 90 days of history.

Where Automation fits

Automation acts at stage 4 of the transaction lifecycle - after the chargeback is filed. Complaints caught earlier are deflected by Alerts; risky orders are stopped before shipping by Prevent.