Integrations
Connect payment processors to Connect so disputes route in automatically - the smart PSP flow, merchant attribution, reconnecting, and enabling Evidence-as-a-Service.
Connect third-party payment processors so disputes and chargebacks are fully automated. This is the connection that makes everything else work: without it, no dispute reaches the engine.
What you can connect
Connect groups processors into three families:
| Group | Examples |
|---|---|
| Payment processors | Stripe, Checkout.com, PayPal, Adyen, Stripe Connect, Braintree, Commerce Control (Fiserv), and more |
| Subscriptions and BNPL | Klarna, Affirm, Afterpay, Sezzle, Recharge |
| eCommerce platforms | Shopify Payments, WooCommerce, Wix |
One catalog, two groupings
The merchant-facing Chargeflow App groups Klarna, Affirm, Afterpay, and Sezzle under payment processors, while Connect groups them under Subscriptions and BNPL. Same integrations, different shelf. The full merchant-side catalog with per-integration status is in Integrations.
The smart PSP connection flow
Connecting a processor account is not one merchant. The smart flow:
- Detects the merchants present on the processor account.
- Shows you what it found so you can review before importing.
- Imports them automatically once you confirm.
That review step is the point. Importing a processor account blind is how a merchant ends up in your pipeline that should not be there.
Merchant attribution
Map each processor account to the merchant it belongs to, so disputes route to the right merchant the moment they arrive rather than being reconciled later. Get this right at connection time: attribution errors are invisible until someone reads a report or a merchant sees a dispute that is not theirs.
Keeping connections healthy
A processor connection can need attention - credentials rotated, access revoked, permissions changed. Reconnect from this screen when that happens. Watch for integration.access.error, which is the event that tells you a connection has stopped working before the merchant notices missing disputes. See Monitor integration health.
Turning on Evidence-as-a-Service
EaaS is enabled from Integrations. It is the alternative to a PSP connection: your platform loads dispute data over the API and Chargeflow returns evidence, with no processor link required. See the eight-step setup.