Integrations

You want to know whether Chargeflow works with the stack you already run. This page is the full catalog, grouped the way the connections actually work.

You connect each tool once from the Chargeflow App. After that, disputes arrive on their own, and every ingested dispute carries a source you can read through the Disputes API.

What each category does

Each category plays a different role in recovering a dispute:

• Payment processors route disputes in. This is the connection that makes everything else work: without it, Chargeflow never sees the dispute.
• eCommerce platforms and subscription tools enrich evidence. They supply the order, fulfilment, and billing history that proves the transaction was legitimate.
• Customer communication tools supply the conversation history. This is what wins Item Not Received and Product Not As Described cases, because the thread shows what you told the customer and when.
• Alert networks deflect disputes before they become chargebacks.

Statuses read the same as the sidebar: Available is live today, New shipped recently, Coming soon is not connectable yet.

Payment processors

Connect at least one. Disputes flow in automatically from here.

Klarna, Affirm, AfterPay, and Sezzle are buy-now-pay-later providers. They are listed here because that is how the Chargeflow App groups them; in Chargeflow Connect they appear under Subscriptions and BNPL.

eCommerce platforms

Order and fulfilment data. These strengthen evidence, they do not route disputes in.

Subscriptions

Billing history, plan changes, and cancellation records, for recurring-billing disputes.

Customer communication

The conversation history. Connect one of these if you dispute Item Not Received or Product Not As Described cases, because the thread is often the strongest single piece of evidence.

Alert networks

Received on your behalf, no connection to set up. They deflect a complaint before it becomes a chargeback.

No-code

Stripe

Disputes originate with source: stripe. Each is matched to the underlying transaction and order, and Chargeflow fires the dispute.created webhook so you can react in real time. See Webhooks.

PayPal

Buyer cases and chargebacks arrive with source: paypal, matched to the underlying transaction and order, and announced via the dispute.created webhook.

Shopify

Disputes arrive with source: shopify and pull in the order context already available in Shopify, which strengthens enrichment evidence. See e-commerce enrichment.

WooCommerce

WooCommerce settles through an underlying processor, so the source varies: WooCommerce-handled payments carry wooCommerce, WooPayments carry wooPayments, and some disputes instead carry the underlying processor (for example stripe). Confirm the exact source per dispute through the Disputes API.

Mastercard Ethoca

Ethoca surfaces a cardholder dispute as an alert before it becomes a chargeback, giving you a short window to act. Chargeflow matches each alert to a transaction, resolves it (most commonly by refunding) or hands it to you, and updates the network with the outcome to prevent the chargeback. Alerts arrive through the Alerts API and the alerts.created, alerts.transaction.linked, and alerts.updated webhooks. See the alerts model to choose between automated and merchant-managed handling.

Visa Verifi RDR

RDR resolves eligible Visa disputes automatically at the network level, based on rules you set, typically with a refund. Chargeflow ingests each case as a pre-chargeback alert, matches it to a transaction, and records the outcome so the resolution stays visible in your account. Same Alerts API and webhooks as Ethoca; see the alerts model.

Zapier

Zapier connects Chargeflow to thousands of apps with no code, using the New Dispute trigger and your x-api-key. Pre-built Zap templates let you enrich disputes, sync to a CRM or OMS, and trigger internal workflows. The complete step-by-step setup lives in the guide:

Do not see your tool?

If a processor is missing, you can still load disputes yourself through the Chargeflow API, which needs no processor connection. For anything else, contact support and tell us what you run.

Next step