Product model
The Chargeflow product suite - Prevent, Alerts, Automation, Insights, and Connect - what each one does, when it acts, and which docs section covers it.
You are deciding what to integrate. This page gives you the map: Chargeflow is not one product but a suite, each part acting at a different point in a transaction's life. Everything else in these docs assumes this vocabulary.
The product suite
| Product | Tier | Acts when | In one line |
|---|---|---|---|
| Prevent | 1 | Before you ship | A pre-fulfillment risk score and a recommended action, so risky orders never become disputes. |
| Alerts | 1 | Before the chargeback | Deflects filed complaints via Verifi RDR / CDRN and Ethoca alerts before they post as chargebacks. |
| Automation | 1 | Once a chargeback is filed | Agentic representment: builds, enriches, and submits the evidence response on your behalf. |
| Insights | 1 | Continuously | Performance monitoring across every connected processor, with proactive alerts before a ratio crosses a threshold. |
| Connect | 2 | Horizontal | "Chargeflow for Platforms": deliver the whole stack to your merchants, under your own brand. |
Read the first four as a timeline and the fifth as a delivery model:
| Stage | Post-auth, pre-fulfilment | Pre-chargeback | Post-chargeback | Across all of it |
|---|---|---|---|---|
| Product | Prevent | Alerts | Automation | Insights |
| Job | Friendly-fraud prevention | Chargeback prevention | Chargeback recovery | Performance monitoring |
Prevent API is coming soon
Prevent is live today via the Chargeflow dashboard and the Shopify app. Its public API is not yet available - see Prevent for what you can do now.
Why several products, not one
Each product catches a dispute one stage earlier than the next, and earlier is always cheaper: a blocked risky order costs nothing, a deflected alert costs the refund, a fought chargeback costs time and a fee even when you win. The products compound - what Automation learns from fought disputes sharpens what Alerts deflects and what Prevent flags, and Insights is where you see whether that is working. You can adopt any one alone; they are better together.
See Transaction lifecycle for exactly where each product sits on the timeline.
Connect: the horizontal layer
Connect is Chargeflow for ISVs, platforms and PSPs rather than for individual merchants - a B2B2B product, where you deliver the dispute stack to the merchants you already serve, under your brand. It ships in four delivery models, differing in who owns the brand and who takes the action:
| Model | Status | In one line |
|---|---|---|
| EaaS - Evidence-as-a-Service | Available | You keep the workflow; Chargeflow returns bank-ready evidence on demand. See What is EaaS? |
| Co-Branded | Available | Chargeflow's interface with your logo, colors and domain - the fastest brand-safe launch. See Co-Branded. |
| White-Label | Beta | Your product name, UI and pricing, Chargeflow invisible end to end. See White-Label. |
| AaaS - Alerts-as-a-Service | Soon | Chargeflow sends the alerts, your platform issues the refund. See Platforms overview. |
Each model runs the same engine, and each can run on auto-pilot or co-pilot per merchant segment. See the Platforms overview for which model fits your business.
Where each product lives in these docs
How recovery actually happens
The model above says which product acts when. If what you need is the mechanism - what happens between a chargeback being filed and the money coming back - read How recovery works, then How our AI works for the agent architecture behind it.