Platforms overview
Chargeflow Connect ("Chargeflow for Platforms") - the four delivery models for ISVs, platforms and PSPs - Evidence-as-a-Service, Co-Branded, White-Label (beta), and Alerts-as-a-Service (Soon).
You are an ISV, platform, or PSP whose merchants get chargebacks, and you need to give them a dispute product without building a dispute team. Connect is that product, delivered as infrastructure you put your own name on.
What Connect is
Connect - "Chargeflow for Platforms" - is the horizontal offering in the Chargeflow product model: the Prevent, Alerts and Automation stack, exposed so your platform can offer it to the merchants it already serves.
It is a B2B2B product - three parties, one relationship:
| Party | Role |
|---|---|
| Chargeflow | Runs the engine. The dispute expertise was built on the merchant side of the market first, across many payment service providers, before the first platform integration. |
| Your platform | Delivers that expertise as a product under its own brand, with no dispute infrastructure to build. |
| The merchant | Is protected inside the product they already use. Never has to become a chargeback expert, and never has to see Chargeflow. |
Connect sells to platforms, not to their merchants. What you buy is the dispute lifecycle, at the level of control you choose.
When to use it
- Your merchants concede disputes they could win, because compiling and uploading evidence takes longer than the dispute is worth to them.
- Your support team fields chargeback questions your product has no answer for, and the first chargeback is the moment a merchant decides whether you are a partner or a payment rail.
- You already run your own submission engine and want bank-ready evidence plus the outcome signal over an API, and nothing more.
- You want to sell dispute protection as your own product, on your own pricing, without an underlying vendor visible to merchants.
Which model fits you
Four delivery models, differing in who owns the brand and who takes the action. Every one runs the same engine.
| You are | Start with | Why |
|---|---|---|
| An ISV with your own submission flow | EaaS | You keep the workflow; you consume evidence and outcomes over the API. |
| A platform or PSP adding disputes to your product | EaaS or Co-Branded | API-first if you have engineers to spend, Co-Branded if you want the shortest path to launch. |
| A merchant of record (MoR) | Co-Branded or White-Label | EaaS does not fit an MoR model; the branded surfaces do. |
| A platform that wants disputes as your own product line | White-Label | Your product name, your UI, your pricing, on the Public API. |
Model availability is set per platform by your Chargeflow account manager. Talk to them before you build - see Support.
Evidence-as-a-Service (EaaS)
Available today. A chargeback lands in your platform, the engine builds the case, the merchant approves it with one click - all inside your UI, with Chargeflow invisible. You supply the dispute data, Chargeflow returns a bank-ready PDF evidence package and the structured data behind it.
ISVs are the sharpest fit: many already run their own submission engine and want only the evidence and the win signal over the API. EaaS is for ISVs, platforms and PSPs - not for merchants of record.
Co-Branded
Available today. The Chargeflow interface with your logo, your colors, and your domain. Merchants see your brand; the engine runs underneath, configured by Chargeflow rather than built by you.
This is the fastest brand-safe launch: no dispute UI to build, no submission flow to own. It fits ISVs and merchants of record that want to be live this month rather than next quarter. Setup is contract-dependent and arranged with your Chargeflow account team - there is no self-serve configuration.
White-Label (beta)
Your own product name, your own UI, and your own pricing, with Chargeflow invisible end to end. Chargeflow connects to your merchants' PSPs and data sources, enriches disputes, builds evidence, and submits it - all under your brand. This is the model platforms ask for most, and it rides on the same Public API the rest of these docs describe.
Alerts-as-a-Service (AaaS)
Soon. Chargeflow sends Ethoca alerts on the merchant's own statement descriptors; your platform issues the refund and stops the chargeback before it is ever filed. Same shape as EaaS - Chargeflow's intelligence, your action, your brand. Enrolling a merchant for Ethoca and RDR will take a single API call at onboarding.
Until AaaS ships, alert-based deflection is available to merchants directly. See Alerts.
Choose your level of autonomy
The on-ramp is not a smaller product. It is the same engine, run at the level of control you pick, per merchant segment:
| Mode | Who decides | Use it when |
|---|---|---|
| Auto-pilot | Chargeflow generates and submits, no human in the loop | Volume is high and per-dispute review is not worth a person's time. |
| Co-pilot | Chargeflow generates, your merchant approves before submission | Your merchants or your risk team require sign-off on what is sent to the bank. |
Acquirers and regulated platforms usually start on co-pilot: an engine deciding everything unsupervised creates its own problems. Segment your merchant base and run both - the Public API exposes the same endpoints either way.
What you'll need
- A Chargeflow Connect account. Your account manager invites your team.
- API keys. Generate them in the Developer Hub in the Connect UI.
- A Chargeflow account per merchant. See Onboard a merchant.
Get started
Whichever model you land on, the first thing to do is prove the engine works against a real dispute. The quickstart takes you from API key to a bank-ready evidence package.
Once it runs, operate it: onboard a merchant, manage accounts, submit platform disputes, monitor integration health, and subscribe to the webhook events. Partner-facing tooling lives in Partner Studio.
Note
All Platforms API endpoints authenticate with your x-api-key header. See the Authentication guide for how to generate keys and optionally enable HMAC signature verification.